Why does `opleader` create mapping in both normal and visual mode?

[mawkler]

Why does opleader create a mapping in both normal and visual mode? I noticed that the mapping I set for operator-pending mode appears as an xmap as well. Is there a specific reason for why it is set in visual mode as well? Is it even possible to perform an operator-pending command from visual mode?

From the README:

---LHS of operator-pending mappings in NORMAL + VISUAL mode
---@type table
opleader = {
    ---Line-comment keymap
    line = 'gc',
    ---Block-comment keymap
    block = 'gb',
},

[numToStr]

This was already discussed in #104

This is just how vim works. If you have a operator pending mapping then the LHS of that keymap should work in NORMAL and VISUAL mode like d10j or V10jd (here you can say that d is an opleader)

[numToStr]

Is there a specific reason for why it is set in visual mode as well?

Because then in visual mode you will be able to do something like V10jgc to comment 10 lines in visual mode.

[mawkler]

Ok I think see your point.

It sorta clashed with my setup because I wanted try using as cm as a trigger in normal mode and <leader>c in visual mode, but this caused cm to become an operator in visual mode as well which I didn't want.

I'll just use #98 to set up my mappings instead as you suggested in #104.