WhichKey conflicting keymaps for mini.comment

[JacquesCherbuin]

In the mini.comment plugin there are 3 mappings:

-- Toggle comment (like `gcip` - comment inner paragraph) for both
-- Normal and Visual modes
comment = 'gc',

-- Toggle comment on current line
comment_line = 'gcc',

-- Define 'comment' textobject (like `dgc` - delete whole comment block)
textobject = 'gc',

'gc' conflicts with 'gcc' and :checkhealth and shows this warning:

When I tried to override the mappings in key lua/plugins/ , :checkhealth still shows the conflict.

I want to map comment_line to 'gl'.

Anyone know how to fix this conflict?

[jyuan0]

For me, :checkhealth doesn't show a 'gc' conflict if comment_line is changed to gl:

  {
    "echasnovski/mini.comment",
    opts = {
      mappings = {
        comment = "gc",
        comment_line = "gl",
        textobject = "gc",
      },
    },
  },

[JacquesCherbuin]

Oh I didn't realise that it can be changed in opts, I was trying to change in keys. Now it works. Thank you

[dpetka2001]

In keys you usually change keys that are not mapped internally by a plugin. If a plugin comes with internal mappings then it's often in the opts section under a mappings or something else that the plugin has configured in its default config. Reading the docs for the default config of the plugin in question helps you understand how nested you should go in opts to change the configuration.

[JacquesCherbuin]

Ok that makes sense. Thanks

[ssh352]

still shows conflict with this config.

WhichKey: checking conflicting keymaps
- WARNING conflicting keymap exists for mode **"n"**, lhs: **"gc"**
- rhs: `

[pkazmier]

Out of curiosity, should an out-of-the-box installation of LazyVim show any conflicting keymap warnings? I just noticed this same warning on a new install. Should we post a bug report?

[folke]

It's a warning, don't worry about it