Closed garcialn closed 3 months ago
your setup is wrong
look at the readme
the "<leader>c"
should be inside the table
also idk what you intend to do with the _ =" which_key_ignore"
there is no such field
Indeed, you were correct... I was using the standard which-key
config from kickstart.nvim, and since it was working before, i didn't even think to look into it. Today i refactored it according to which-key
docs and everything is working fine. Thank you for the heads up 😉
Did you check docs and existing issues?
Neovim version (nvim -v)
0.10.0
Operating system/version
Pop!_OS 22.04-LTS
Describe the bug
Since the new release, every time i open nvim, i get an error message linked to" keymaps (but only those added with
which-key
, when i proceed with:checkhealth which-key
i noticed that theERRORS
are related to "require("which-key").add{}
) orWARNINGS
to keymaps that have similar bindings, but not repeated (overlapping). My problem is actually about the startup message (which i believe is only connected to the<leader>
keymaps errors), not really about the:checkhealth
output...Steps To Reproduce
<leader>
binding:checkhealth which-key
Expected Behavior
No errors with
<leader>
binding, which would lead to no error message on startup...Health
Log
Repro