diff options
author | Damjan 9000 <damjan.9000@gmail.com> | 2024-03-03 09:54:58 +0100 |
---|---|---|
committer | Damjan 9000 <damjan.9000@gmail.com> | 2024-03-03 09:54:58 +0100 |
commit | de8986f7a8a6688fee64b381ec3ef4a9c347518e (patch) | |
tree | dcacc4cc7c23c9fa26faa45d339f0f1eb7b5ae4b /lua/kickstart/plugins/which-key.lua | |
parent | df166c3b8b075a3444dd88215320aa7fbaa55ed5 (diff) | |
parent | e6710a461ab08513af80c213929ff64e75b5e456 (diff) |
Merge 'upstream/master' VimEnter, win install, custom/plugins note
fix: add note in readme for custom plugins
README.md: updated windows install instructions (#674)
feat: use VimEnter event instead of VeryLazy (#673)
Diffstat (limited to 'lua/kickstart/plugins/which-key.lua')
-rw-r--r-- | lua/kickstart/plugins/which-key.lua | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/lua/kickstart/plugins/which-key.lua b/lua/kickstart/plugins/which-key.lua index 776a052..b73b17b 100644 --- a/lua/kickstart/plugins/which-key.lua +++ b/lua/kickstart/plugins/which-key.lua @@ -4,9 +4,9 @@ -- lazy loading plugins that don't need to be loaded immediately at startup. -- -- For example, in the following configuration, we use: --- event = 'VeryLazy' +-- event = 'VimEnter' -- --- which loads which-key after all the UI elements are loaded. Events can be +-- which loads which-key before all the UI elements are loaded. Events can be -- normal autocommands events (`:help autocmd-events`). -- -- Then, because we use the `config` key, the configuration only runs @@ -16,7 +16,7 @@ return { { -- Useful plugin to show you pending keybinds. 'folke/which-key.nvim', - event = 'VeryLazy', -- Sets the loading event to 'VeryLazy' + event = 'VimEnter', -- Sets the loading event to 'VimEnter' config = function() -- This is the function that runs, AFTER loading require('which-key').setup() |