Disable visual mappings

[folke]

Disable visual mappings

[folke]

The correct way to disable this would be to not load the operators preset and configure operators manually:

{
  plugins = {
    -- ...
    presets = {
      operators = false
      -- ..
    },
  },
  -- add operators that will trigger motion and text object completion
  -- to enable all native operators, set the preset / operators plugin above
  operators = {
    d = "Delete",
    c = "Change",
    y = "Yank (copy)",
    ["g~"] = "Toggle case",
    ["gu"] = "Lowercase",
    ["gU"] = "Uppercase",
    [">"] = "Indent right",
    ["<lt>"] = "Indent left",
    ["zf"] = "Create fold",
    ["!"] = "Filter though external program",
    -- ["v"] = "Visual Character Mode",
    gc = "Comments"
 },
}

Although, this seems a bit verbose to just disable one operator. I'll see if I can come up with an easier way to do this.

[folke]

I think I'll just add some proper documentation on how to set up operators, motions and text objects and how the preset works in regards to that. You can leave it open for now :)

[klooj]

you need to specify a mode. i think that should fix it.

so wk.register({['v'] = 'which_key_ignore'}, {mode = 'n'}) and wk.register({['v'] = 'which_key_ignore'}, {mode = 'v'})

[klooj]

nevermind. i'm getting this error after timeoutlen if i just press v once in normal mode:

[NTBBloodbath]

Strange, I just placed it and it didn't give errors, however instead of showing +Visual Character Mode, it shows +which_key_ignore 🤔

Maybe it's not possible to disable triggering WhichKey in visual mode (for now), although it's not something that is very annoying

[NTBBloodbath]

Thank you very much, it works great 😃

Should I close the issue or will it be closed when making changes?

[NTBBloodbath]

Understood, thank you very much again 🙂