WhichKey shows conflicts with default keybindings

[matu3ba]

WhichKey: checking conflicting keymaps

• WARNING: conflicting keymap exists for mode "n", lhs: "gb"
• INFO: rhs: <Plug>(comment_toggle_blockwise)
• WARNING: conflicting keymap exists for mode "n", lhs: "gc"
• INFO: rhs: <Plug>(comment_toggle_linewise)

Would be nice to add a hint how to disable this with note on the default keybindings.

see also https:/linty-org/key-menu.nvim/pull/8 for the great effort.

[numToStr]

Would be nice to add a hint how to disable this with note on the default keybindings.

I am not sure, what to disable here(?). As I don't use whichkey so I have no idea what to do here. But if you want, you can disable all the mappings by adding mappings = false to setup config

[sonu405]

I have copied comment.lua from your config but still the mappings are not working!! What do I do? The plugin is not giving any errors? The path in the Packer config is also correct.
Code from comment.lua --> require('Comment').setup({
pre_hook = function(ctx)
return require('Comment.jsx').calculate(ctx)
end,
})

[numToStr]

@Jetandarkumar What mappings are not? Are you talking about whichkey? If not please have a look #115

[numToStr]

I am closing this as this is not really a issue with the plugin.

[sonu405]

@Jetandarkumar What mappings are not? Are you talking about whichkey? If not please have a look #115

Found the answer in #115, Thanks a lot!! I also copied chris@machine config and the problem was with it.

[zippeurfou]

@numToStr I think he is referring to the :checkhealth command where which-key tells you if any of your mapping has conflict and in this case this plugin seems to display a conflict.

So it is not really about changing your keymap but somehow something create a conflict there.
There is an issue about it here as well folke/which-key.nvim#218
I am not sure there is a fix thought.