Questions about the new keymap spec #734
-
While I understand the appeal and the reasoning to use a closer spec to the internal nvim api, I personally prefer the old way of specifying keymaps for which-key. I see the v3 still supports the old version with a deprecation warning. When will effectively remove the support for the old version? Do you have this planned? I'm trying to find time to migrate them all. All my which-key keymaps would fit the internal nvim api (except the parent group ones). Would there be any tradeoff between defining them with which-key api in comparison to nvim api? Is it possible to define the group parents with the nvim api? Would it be possible to create a tree of maps? For example:
And lastly. I can't express how grateful I am for your hard work in creating such a rich ecosystem of plugins. Great work. Thank you very much. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
The old way will be removed at some point and I'm not going to bring nested mappings back. To define groups with the Neovim API, add an |
Beta Was this translation helpful? Give feedback.
-
If you don't mind, @folke, could you please give a rationale for the deprecation of nested mappings? It seemed quite an elegant design to me, and I don't understand why they are going away. I have looked for a rationale in the docs and the git history but haven't found one. |
Beta Was this translation helpful? Give feedback.
The old way will be removed at some point and I'm not going to bring nested mappings back.
To define groups with the Neovim API, add an
rhs
of""
or"<nop>"