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
Is your feature request related to a problem? Please describe.
When creating mappings in keybindings.json, it's possible to create a collision with a Vim chord.
So for example, you have a shift+k in your keybindings.json and [ "ctrl+w", "K" ] (or [ "ctrl+w", "shift+k" ], it doesn't matter) in your vim.normalModeKeyBindings. shift+k will take priority here, making [ "ctrl+w", "K" ] impossible to trigger.
Describe the solution you'd like
A way to detect if there's a currently active chord. The condition can then be put into when, to ensure that it doesn't shadow the chord.
Describe alternatives you've considered
You can map the keybind in your vim.normalModeKeyBindings, but some commands don't behave properly as a Vim binding for some reason. For example, editor.action.showHover (gh) doesn't behave properly when mapped as a Vim binding: #3740 (comment)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When creating mappings in
keybindings.json
, it's possible to create a collision with a Vim chord.So for example, you have a
shift+k
in yourkeybindings.json
and[ "ctrl+w", "K" ]
(or[ "ctrl+w", "shift+k" ]
, it doesn't matter) in yourvim.normalModeKeyBindings
.shift+k
will take priority here, making[ "ctrl+w", "K" ]
impossible to trigger.Describe the solution you'd like
A way to detect if there's a currently active chord. The condition can then be put into
when
, to ensure that it doesn't shadow the chord.Describe alternatives you've considered
You can map the keybind in your
vim.normalModeKeyBindings
, but some commands don't behave properly as a Vim binding for some reason. For example,editor.action.showHover
(gh
) doesn't behave properly when mapped as a Vim binding: #3740 (comment)The text was updated successfully, but these errors were encountered: