Closed prdanelli closed 1 month ago
I guess this can be done with the triggers
option in the config now
wk should never bind triggers to builtin keymaps. I already added protection for this for lower-case keys, but forgot to do the same for uppercase. Will do so now.
Added. Turns out that only Z
is a safe upper-case letter.
All the others are builtin keymaps.
Thank you so much.
On Thu, 18 Jul 2024 at 15:28, Folke Lemaitre @.***> wrote:
Added. Turns out that only Z is a safe upper-case letter. All the others are builtin keymaps.
— Reply to this email directly, view it on GitHub https://github.com/folke/which-key.nvim/issues/756#issuecomment-2236701192, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJE62KWCKKAWDYV7WMJPGTZM7GKRAVCNFSM6AAAAABLCTVE22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZWG4YDCMJZGI . You are receiving this because you authored the thread.Message ID: @.***>
Did you check the docs?
Is your feature request related to a problem? Please describe.
I've been reading the docs and can't find anything related to how I can bypass which-key for certain keymaps - similar to the "blacklist" feature in v2.x.
I have a series of custom keymaps for things like
oo
, which inserts a line below and returns to normal mode, andOO
which adds a line above and returns to the normal mode.Since updating to v3, using
O
, to jump into insert mode on the line above, now presents the which-key panel with a single option forO
.I did have this disabled by using the
disable
method:However that seems to have been removed now.
Describe the solution you'd like
Similar to "blacklist", i'd like to be able to define a table to characters that would be ignored by which-key completely.
Describe alternatives you've considered
.
Additional context
.