feat(keymap): allow direct bindings for leader commands - #326
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Commands available only in the leader menu cannot currently be assigned a direct key. Allow main leader commands in
action_keyswithin app scopes, soquery_normal.edit_query_in_editor: "ctrl+g"opens the editor while the existing leader shortcut remains available.The bindings retain command guards, explicit state restrictions, and existing conflict detection. Direct editor shortcuts are dispatched before the text widget consumes them, with autocomplete precedence resolved by the existing key router. Aliases and independent unbinding are supported. Vim submenu motions and dialog scopes remain outside this command-promotion feature.
Closes #321.
Validation:
keymap_manager.pyalso reproduce onmain.