Closed IndianBoy42 closed 3 months ago
This sounds like a reasonable request for which-key
. Unfortunately I don't think lazy.nvim
could follow it (see this comment).
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.
Did you check the docs?
Is your feature request related to a problem? Please describe.
vim.keymap.set
wisely made the slight change on the defaults fornvim_set_keymap
to make "replace_keycodes" defaultstotrue
if "expr" istrue
, as users would want most of the time.Describe the solution you'd like
Replicate this behaviour to make which-key mapping as close to vim.keymap.set mapping. I also just noticed that lazy.nvim could do with this change as well
Describe alternatives you've considered
This is just simplifying common cases/bringing parity with
vim.keymap.set
rather than a new feature. The alternatives are just remembering to set the options manuallyAdditional context
No response