search

folke / which-key.nvim

💥 Create key bindings that stick. WhichKey helps you remember your Neovim keymaps, by showing available keybindings in a popup as you type.
Apache License 2.0
5.42k stars 177 forks source link

question(healthcheck): how to mark overwrites as intended and not accidental conflicting #151

Closed matu3ba closed 4 months ago

matu3ba commented 3 years ago

The following warnings are given upon running :checkhealth on a fresh install. This is kinda odd, since which-key should work without keybindings. So somewhere checkhealth broke.

health#which_key#check
========================================================================
## WhichKey: checking conflicting keymaps
  - WARNING: buffer-local keymap overriding global for mode **"n"**, buf: 0, lhs: **" "**
  - INFO: old rhs: ``
  - INFO: new rhs: `<cmd>lua require("which-key").show(" ", {mode = "n", auto = true})<cr>`
  - WARNING: buffer-local keymap overriding global for mode **"x"**, buf: 0, lhs: **" "**
  - INFO: old rhs: ``
  - INFO: new rhs: `<cmd>lua require("which-key").show(" ", {mode = "v", auto = true})<cr>`
matu3ba commented 3 years ago

This comes from

vim.api.nvim_set_keymap("n", " ", "", { noremap = true })
vim.api.nvim_set_keymap("x", " ", "", { noremap = true })

and alike mappings.

Is there a plan or are there any plans to indicate that a mapping is intended to overwrite stuff (ideally also what existing stuff, but that might be too noisy) ?

wren commented 3 years ago

Or in absence of this, maybe a way to disable the health check?

github-actions[bot] commented 4 months ago

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.