Archived Read Only Forums > SlickEdit 2016 v21 Beta Discussion

Goto line does not work any more

(1/4) > >>

wvdb:
The Ctrl+G (Goto line) does not work any more in RC3 and RC4.
Slickedit shows a popup with "Command gui-goto not found"
The menu item Search --> Goto line ...  does work, but this one refers to the command gui-goto-line

SlickEdit Pro 2016 (v21.0.0.9 64-bit)

Serial number: FE10423_BETA
License type: Beta License
License expiration: 2016-10-31 01:00:00
License file: C:\ProgramData\slickedit\21\slickedit.lic

Build Date: September 22, 2016
Emulation: Visual C++ 6

OS: Windows 7 x64
OS Version: 6.01.7601  Service Pack 1
Memory: 39% Load, 9690MB/24515MB Physical, 9353MB/24513MB Page File, 578MB/8388607MB Virtual
Shell Information: C:\Windows\system32\cmd.exe /q
Screen Size: 1920 x 1080

Project Type: Cpp
Language: .cpp (C/C++)
Encoding: Automatic

Installation Directory: C:\Program Files\SlickEdit Pro 21.0.0\ (non-removable drive,NTFS,39543MB free)
Configuration Directory: C:\Users\boogaardw\Documents\My SlickEdit Config\21.0.0\ (non-removable drive,NTFS,39543MB free)
Migrated from: C:\Users\boogaardw\Documents\My SlickEdit Config\20.0.1\
Spill File: C:\Users\boogaardw\AppData\Local\Temp\$slk.7340 (non-removable drive,NTFS,39543MB free)

Clark:
Maybe your 20.0.1 config didn't get migrated quite right.

Please zip up your 20.0.1 config without the subdirectories and upload it.

Go to Url: http://support.slickedit.com

Enter 14053 for the case (this topic id).

Post here to let us know it has been uploaded

Thanks

jporkkahtc:
FWIW, I think I had the same problem when upgrading to RC3 --
everything else seemed OK, but Ctrl+G no longer worked.
That keybinding was lost.

Clark:

--- Quote from: jporkkahtc on September 26, 2016, 05:27:32 pm ---FWIW, I think I had the same problem when upgrading to RC3 --
everything else seemed OK, but Ctrl+G no longer worked.
That keybinding was lost.

--- End quote ---

I've got your 20.0.2 config. I tried upgrading it to RC 3 and Ctrl+G worked after the upgrade. I also tried some other migration tests and couldn't reproduce this.

I can only guess there is some additional odd condition happening.

I'd like to figure this out.

jporkkahtc:
You should have a more recent config of mine as well.


Anyways, I restored my config from before I installed RC3, but I could not repro the problem.
I may have seen this on my computer at home - I'll take a look tonight.

Navigation

[0] Message Index

[#] Next page

Go to full version