#102 <ctrl><shift>n used in two places in default shortcuts

Fixed
closed
nobody
None
1
2015-01-08
2014-03-21
Anonymous
No

Amazing that nobody noticed this until now, but in the Default keyboard shortcuts file, Ctrl+Shift+n is used twice--once for New Window, once for Find Next:

ƛ cat Config/Shortcuts/Default

[roxterm shortcuts scheme]
File/New Window=<Shift><Control>n
File/New Tab=<Shift><Control>t
File/Close Window=<Shift><Control>q
File/Close Tab=<Shift><Control>w
Tabs/Previous Tab=<Control>Page_Up
Tabs/Next Tab=<Control>Page_Down
Edit/Copy=<Shift><Control>c
Edit/Paste=<Shift><Control>v
View/Zoom In=<Control>plus
View/Zoom Out=<Control>minus
View/Normal Size=<Control>0
View/Full Screen=F11
View/Scroll Up One Line=<Shift>Up
View/Scroll Down One Line=<Shift>Down
Help/Help=F1
Edit/Copy & Paste=<Shift><Control>y
Search/Find...=<Shift><Control>f
Search/Find Next=<Shift><Control>n
Search/Find Previous=<Shift><Control>p

Besides that, maybe I should open another bug, since editing this file, and even creating a custom set of shortcuts didn't change the actual shortcuts... maybe it's not looking in ~/.config/roxterm.sourceforge.net/Shortcuts/ for the shortcut files?

Discussion

  • Tony Houghton

    Tony Houghton - 2014-04-25

    Thanks for pointing out the clash. I think the most appropriate amendment would be to use shift+control+i for Find Next. Not ideal, but I think New Window should take priority for 'n', while 'i' could be remembered as 'incremental search', besides being the second letter of 'find'.

    I can't work out what went wrong for you when you tried to correct it though. AFAICT it is picking up changes to either file, but you have to restart roxterm (close all its windows) to make it reread the file. If the one in ~/.config is present it will use that and ignore the one in /usr/share/roxterm/Config/Shortcuts, otherwise it uses the latter (assuming a standard installation with a package manager). Also, if you edit the one in .config while roxterm is running it's likely to overwrite it before it exits.
    Now I need to think about a way to deal with localisation in Shortcuts (see #103) and find out why shortcut editing isn't working in GTK3.

     
  • Tony Houghton

    Tony Houghton - 2015-01-08
    • status: open --> closed
    • Group: Next_release --> Fixed
     


Anonymous

Cancel  Add attachments