disabled problematic which-key features

This commit is contained in:
BirdeeHub 2024-04-15 00:05:53 -07:00
parent 23773900d9
commit 7d2ab40f2f
1 changed files with 13 additions and 1 deletions

View File

@ -277,7 +277,19 @@ require('lazy').setup({
'folke/which-key.nvim', 'folke/which-key.nvim',
event = 'VimEnter', -- Sets the loading event to 'VimEnter' event = 'VimEnter', -- Sets the loading event to 'VimEnter'
config = function() -- This is the function that runs, AFTER loading config = function() -- This is the function that runs, AFTER loading
require('which-key').setup() require('which-key').setup({
-- some features of which key prevent normal functioning of the key
-- this is a bug, so we will disable the problematic features.
-- which-key is very useful for those new to vim motions, so it is still included.
plugins = {
-- this will currently prevent the " keybind from working in normal mode.
registers = false, -- shows your registers on " in NORMAL or <C-r> in INSERT mode
presets = {
-- this will currently prevent the <C-w> keybinds from working in normal mode.
windows = false, -- default bindings on <c-w>
},
},
})
-- Document existing key chains -- Document existing key chains
require('which-key').register { require('which-key').register {