Justin M. Keyes
Justin M. Keyes
Oh because Windows.
This could be done by using `(nvim.foo)` for mappings with a common prefix. E.g. the `gr` prefix could be `(nvim.gr)`. But `:help gr-default` already shows a "structured" way to disable...
and why isn't `:mapclear` a solution? the fact that one person wants some mappings but not others, is kind of a random preference. in the case of lsp, it *already*...
A way forward is to decide which mappings are non-controversial, and make them builtins. Adding a new "mapping family" concept just sounds like another thing that won't satisfy everyone. When...
And your suggestion is to... create some groupings, which some people will like, and others will open new issues saying they want different groupings? That is not something we are...
Feel free to keep the PR in "Draft" if you want to keep hacking at it. PRs in Draft do not bother anyone.
The magnitude of the problem is not clear. How many highlights does this affect and why is it important enough to justify all the code in https://github.com/neovim/neovim/pull/36717 ?
The default from https://github.com/neovim/neovim/pull/19672 should be preserved, I don't see a reason to change the default. The main point of the recent exit_timeout enhancements is to provide a mechanism for...
I'm in favor of renaming a lot of these, but `bufnr` is also prevalent so we're kind of stuck. But it's probably at least feasible to get rid of `buffer`...