which-key.nvim
which-key.nvim copied to clipboard
Conflicting with other keymaps
WhichKey: checking conflicting keymaps
- WARNING: conflicting keymap exists for mode "n", lhs: "g
" - INFO: rhs:
<Cmd>lua require("Comment.api").call("uncomment_linewise_op")<CR>g@ - WARNING: conflicting keymap exists for mode "n", lhs: "gc"
- INFO: rhs:
<Plug>(comment_toggle_linewise) - WARNING: conflicting keymap exists for mode "n", lhs: "gb"
- INFO: rhs:
<Plug>(comment_toggle_blockwise) - WARNING: conflicting keymap exists for mode "n", lhs: "g>"
- INFO: rhs:
<Cmd>lua require("Comment.api").call("comment_linewise_op")<CR>g@ - WARNING: conflicting keymap exists for mode "n", lhs: "ys"
- INFO: rhs:
<Plug>Ysurround - WARNING: conflicting keymap exists for mode "n", lhs: "yS"
- INFO: rhs:
<Plug>YSurround - WARNING: buffer-local keymap overriding global for mode "n", buf: 0, lhs: "
" - INFO: old rhs:
:TmuxNavigateRight<cr> - INFO: new rhs:
<cmd>TmuxNavigateRight<cr> - WARNING: buffer-local keymap overriding global for mode "n", buf: 0, lhs: "
" - INFO: old rhs:
:TmuxNavigateDown<cr> - INFO: new rhs:
<cmd>TmuxNavigateDown<cr> - WARNING: buffer-local keymap overriding global for mode "n", buf: 0, lhs: "<c-\>"
- INFO: old rhs:
:TmuxNavigatePrevious<cr> - INFO: new rhs:
<cmd>vsp<cr> - WARNING: buffer-local keymap overriding global for mode "n", buf: 0, lhs: "
" - INFO: old rhs:
:TmuxNavigateUp<cr> - INFO: new rhs:
<cmd>TmuxNavigateUp<cr> - WARNING: buffer-local keymap overriding global for mode "n", buf: 0, lhs: "
" - INFO: old rhs:
:TmuxNavigateLeft<cr> - INFO: new rhs:
<cmd>TmuxNavigateLeft<cr>
Possibly related to #218
Hi, any news on this?
I have this:
WhichKey: checking conflicting keymaps ~
- WARNING conflicting keymap exists for mode **"n"**, lhs: **"gb"**
- rhs: `<Plug>(comment_toggle_blockwise)
- WhichKey: checking conflicting keymaps ~
- WARNING conflicting keymap exists for mode **"n"**, lhs: **"gb"**
- rhs: `<Plug>(comment_toggle_blockwise)
Seem like you just ignore them. https://github.com/folke/which-key.nvim/issues/79