Skip to content
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

Not all maping are defined with which-key #2

Open
xoac opened this issue Dec 15, 2021 · 1 comment
Open

Not all maping are defined with which-key #2

xoac opened this issue Dec 15, 2021 · 1 comment

Comments

@xoac
Copy link
Owner

xoac commented Dec 15, 2021

Here is an example of not described shortcuts but there are more. There should be a way to display all not described shortcuts.

image

additional there are some conflicts:

which_key: health#which_key#check
========================================================================
## WhichKey: checking conflicting keymaps
  - WARNING: conflicting keymap exists for mode **"n"**, lhs: **"g<lt>"**
  - INFO: rhs: `<Cmd>lua require("Comment.api").call("glt")<CR>g@`
  - WARNING: conflicting keymap exists for mode **"n"**, lhs: **"gc"**
  - INFO: rhs: `<Cmd>lua require("Comment.api").call("gc")<CR>g@`
  - WARNING: conflicting keymap exists for mode **"n"**, lhs: **"gb"**
  - INFO: rhs: `<Cmd>lua require("Comment.api").call("gb")<CR>g@`
  - WARNING: conflicting keymap exists for mode **"n"**, lhs: **"g>"**
  - INFO: rhs: `<Cmd>lua require("Comment.api").call("ggt")<CR>g@`
@LudoPinelli
Copy link

For the conflicts, I think it has to do with the way nvim-comment default keybindings are defined : it seems to me that gc creates a conflicts with gcc and gb creates a conflict with gbc.
I didn't try it yet but changing the kybindings of gc and gb to - for example - gx and gy may solve the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants