Repository navigation
Change default binds from <leader> to <localleader> - #34
Merged
Merged
Conversation
voodoos
approved these changes
Jul 16, 2026
voodoos
left a comment
Member
There was a problem hiding this comment.
Thank you @NatKarmios that feels like the right thing to do, yes.
Could you add a changelog entry for it (I can do it myself if you prefer)
Contributor
Author
|
Sure, I've done that now, thank you. |
Member
|
Thanks ! |
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.
Thank you guys for maintaining this plugin :)
This may be down to personal taste, but as I understand it, the local leader is the best place to put filetype-specific bindings.
I found that the default bindings provided here clash with my global binds; it wouldn't surprise me if this were the case for others too.
Might it be worth switching the default from
<leader>to<localleader>?