search

folke / which-key.nvim

💥 Create key bindings that stick. WhichKey helps you remember your Neovim keymaps, by showing available keybindings in a popup as you type.
Apache License 2.0
5.4k stars 176 forks source link

This plugin is adding useless mappings to > #39

Closed jordisantamaria closed 3 years ago

jordisantamaria commented 3 years ago

What are those mappings, It's conflicting with my setup... and I don't see It's doing anything useful, is there any way to disable It? スクリーンショット 2021-05-01 18 50 58

folke commented 3 years ago

You can disable them by setting the plugins.presets.operators to false If you don;t want help for motions and text objects, then set those also to false The <nop> ones are to make sure whichkey triggers always repsect timeoutlen.

Apart from this, would be great if you could tell me what conflicts with your setup?

folke commented 3 years ago

also, if you want to specify your own triggers, then set triggers = {"<leader>"} for example

jordisantamaria commented 3 years ago

I wanted to setup a map of < to << and > to >> for tabbing text, It's a bit annoying to wait timeoutlen time because some extra mappings I didn't defined.

folke commented 3 years ago

That wouldn't wait for timeoutlen and should work as expected

folke commented 3 years ago

<< and >> are native commands. No need to setup anything for that?

folke commented 3 years ago

Ah never mind, you want to remap < to <<? Got it

folke commented 3 years ago

See also https://github.com/folke/which-key.nvim#-operators-motions-and-text-objects

Especially the collapsed example on disabling v

jordisantamaria commented 3 years ago

anyway, It's fixed by doing plugins.presets.operators to false so all fine, thanks you, It's awesome you respond so fast lol.