Open kevintraver opened 10 months ago
Related to this, for me cutlass doesn't work at all if the which-key
plugin is also enabled. The pop-ups of which-key show up, but the d
and s
bindings are just not set by cutlass. Seems like an ordering issue to me.
I think I found a workaround by setting the triggers_blacklist
option of which-key
to something like
triggers_blacklist = {
-- list of mode / prefixes that should never be hooked by WhichKey
-- this is mostly relevant for keymaps that start with a native binding
i = { "j", "k", "d", "D", "s", "S" },
v = { "j", "k", "d", "D", "s", "S", " ", "g" },
n = { "d", "D", "s", "S", "m" },
}
I've tried many things to fix this but nothing works :sweat:
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 docs and existing issues?
Neovim version (nvim -v)
NVIM v0.9.1
Operating system/version
MacOS 13
Describe the bug
Does not work with cutlass.nvim
https://github.com/gbprod/cutlass.nvim/issues/20
Steps To Reproduce
Install which-key.
Then pressing any pending operator mode keys should bring up which-key:
c
,C
,s
,S
,d
,D
,x
,X
,y
Expected Behavior
The which-key panel does not show up.
Repro