You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages
Description
I can't decide if this is a resolver issue or a core keybindings issue really. There are a number of keys that are bound to Ctrl-Shift-[special character]. When these keys are being seen by keybinding-resolver, they no longer have the Shift in them, so often don't show a resolved mapping.
I noticed this on Ctrl-Shift-\ -- which in reality is actually ctrl-| and that's how keybinding-resolver is seeing it, so it doesn't show a mapping.
Now one fix for this, is to just put ctrl-| in keymaps instead, which now resolves properly, but at the same time atom IS responding to keymap defined as ctrl-shift-\. Which is a little odd.
I haven't dug to see if there is a way to get the key pressed vs "resulting key", but this is clearly happening different in the core key lookups.
Ctrl-Shift-8 is another example, Ctrl-* is what results.
From a usability standpoint, I guess I understand why like Ctrl-Shift-8 and Ctrl-Shift-9 are easier for a user to remember, but it really is ctrl-* and ctrl-( ;)
Capitalized letters do show up with the Shift Ctrl-Shift-P for example. Ctrl-+ and Ctrl- -are interesting in that they are defined without listing shift, but also have matching bindings for the non-shifted keys.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Prerequisites
Description
I can't decide if this is a resolver issue or a core keybindings issue really. There are a number of keys that are bound to
Ctrl-Shift-[special character]
. When these keys are being seen by keybinding-resolver, they no longer have the Shift in them, so often don't show a resolved mapping.I noticed this on
Ctrl-Shift-\
-- which in reality is actuallyctrl-|
and that's how keybinding-resolver is seeing it, so it doesn't show a mapping.Now one fix for this, is to just put
ctrl-|
in keymaps instead, which now resolves properly, but at the same time atom IS responding to keymap defined asctrl-shift-\
. Which is a little odd.I haven't dug to see if there is a way to get the key pressed vs "resulting key", but this is clearly happening different in the core key lookups.
Ctrl-Shift-8
is another example,Ctrl-*
is what results.From a usability standpoint, I guess I understand why like Ctrl-Shift-8 and Ctrl-Shift-9 are easier for a user to remember, but it really is ctrl-* and ctrl-( ;)
Capitalized letters do show up with the Shift
Ctrl-Shift-P
for example.Ctrl-+
andCtrl- -
are interesting in that they are defined without listing shift, but also have matching bindings for the non-shifted keys.The text was updated successfully, but these errors were encountered: