Add option for recursive select bindings #1
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
When using recursive key bindings in select mode, some chars (like 'n') will trigger an appropriate change operation instead of entering the char itself (for 'n' it would be "change up to the next search result"). A special <Plug> mapping was introduced to mitigate these issues.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
First of all thank you for this plugin ❤️
It makes the usage of (Neo)Vim a lot easier and predictable for me
One issue that always got me was that during snippet expansion (which usually uses select mode) the initial key press would not trigger any "autopair" style plugin (to automatically insert closing parentheses or matching quotation marks). I saw that this issue could easily be resolved by making the select bindings nested/recursive.
To not mess around wit the defaults I have implemented this as an opt-in feature.
If you think this is outside the scope for this plugin and you like to keep this minimal I would understand, but I thought maybe this is a use case which others could relate to 🙂