-
Notifications
You must be signed in to change notification settings - Fork 7
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
Integration with nvim-mapper
#2
Comments
I actually thought about the same thing, but with which-key, which also has a more complicated custom format to define mappings but is really good at showing mappings. I will put it on the list for integrations - there might be several interesting optional integrations :-) |
nvim-mapper
Thanks for mentioning it! Actually I already use folke/which-key.nvim and thought it didn't work for non-leader keybindings. Now I see it does, so (I think?) I don't need to use nvim-mapper for those features. I also see the which-key mapping format looks very similar to nest.vim - if you do add a which-key integration, it would be helpful to have some examples of why use nest.nvim's format :) |
|
nvim-mapper provides a way to find and remember key mappings, but it requires re-writing your mappings in its special format. The special format provides no benefits except for informing the plugin about the available maps. On the other hand, nest.nvim provides a nice way of formatting mappings in ways that group similar keybindings together, a clear benefit that makes sense to adopt. An integration with nvim-mapper would make it much easier to get the benefits of both plugins with minimal changes to the nest.nvim format.
The text was updated successfully, but these errors were encountered: