-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: does not work with cutlass.nvim #513
Comments
Related to this, for me cutlass doesn't work at all if the |
I think I found a workaround by setting the 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 😓 |
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
gbprod/cutlass.nvim#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
The text was updated successfully, but these errors were encountered: