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
Allow all default keybindings to be set to no-op with a config option. While I'm very happy with Helix's design of giving commands and bindings descriptive names instead of using arcane keyboard keys (unlike vim and it's derivatives), it's currently both cumbersome and error prone to manually set every unused binding to no-op when remapping keys. If a precedent is needed, Zellij has a keybindings: unbind: <bool> config that does exactly this.
To be more specific, I propose the following configuration: unbind-defaults: <bool> which defaults to false. When set to true all default keybindings are not added to the keybinding trie (or set to no-op, whatever's easier) and only the bindings listed in the user's config file will be used.
The text was updated successfully, but these errors were encountered:
When we switch to scheme config we want to make it possible to completely overwrite the default keymap which will solve this (see the keymap portion of #10441). So I will close this in favor of #10389
Describe your feature request
Allow all default keybindings to be set to
no-op
with a config option. While I'm very happy with Helix's design of giving commands and bindings descriptive names instead of using arcane keyboard keys (unlike vim and it's derivatives), it's currently both cumbersome and error prone to manually set every unused binding tono-op
when remapping keys. If a precedent is needed, Zellij has akeybindings: unbind: <bool>
config that does exactly this.To be more specific, I propose the following configuration:
unbind-defaults: <bool>
which defaults tofalse
. When set totrue
all default keybindings are not added to the keybinding trie (or set tono-op
, whatever's easier) and only the bindings listed in the user's config file will be used.The text was updated successfully, but these errors were encountered: