Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unbind all default keybindings config option #2720

Closed
Lindenk opened this issue Jun 8, 2022 · 1 comment
Closed

Unbind all default keybindings config option #2720

Lindenk opened this issue Jun 8, 2022 · 1 comment
Labels
A-helix-term Area: Helix term improvements C-enhancement Category: Improvements

Comments

@Lindenk
Copy link

Lindenk commented Jun 8, 2022

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 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.

@Lindenk Lindenk added the C-enhancement Category: Improvements label Jun 8, 2022
@the-mikedavis the-mikedavis added the A-helix-term Area: Helix term improvements label Jun 8, 2022
omentic added a commit to omentic/helix-ext that referenced this issue Nov 1, 2023
@the-mikedavis
Copy link
Member

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

@the-mikedavis the-mikedavis closed this as not planned Won't fix, can't repro, duplicate, stale Apr 19, 2024
omentic pushed a commit to omentic/helix-ext that referenced this issue May 1, 2024
omentic pushed a commit to omentic/helix-ext that referenced this issue May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-helix-term Area: Helix term improvements C-enhancement Category: Improvements
Projects
None yet
2 participants