Skip to content

Commit f2761df

Browse files
jensenr30zenvignesh
authored andcommitted
Fix which-key delay settings (nvim-lua#1276)
The which-key plugin used to rely on vim.opt.timeoutlen, but it was updated a few months ago to use its own opt.delay instead. https://github.com/folke/which-key.nvim/blob/8ab96b38a2530eacba5be717f52e04601eb59326/NEWS.md?plain=1#L10 I set which-key's delay to 0 ms because it makes it feel snappy and responsive! That way, we give new users a good first impression.
1 parent a040855 commit f2761df

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

init.lua

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -135,7 +135,6 @@ vim.opt.signcolumn = 'yes'
135135
vim.opt.updatetime = 250
136136

137137
-- Decrease mapped sequence wait time
138-
-- Displays which-key popup sooner
139138
vim.opt.timeoutlen = 300
140139

141140
-- Configure how new splits should be opened
@@ -286,6 +285,9 @@ require('lazy').setup({
286285
'folke/which-key.nvim',
287286
event = 'VimEnter', -- Sets the loading event to 'VimEnter'
288287
opts = {
288+
-- delay between pressing a key and opening which-key (milliseconds)
289+
-- this setting is independent of vim.opt.timeoutlen
290+
delay = 0,
289291
icons = {
290292
-- set icon mappings to true if you have a Nerd Font
291293
mappings = vim.g.have_nerd_font,

0 commit comments

Comments
 (0)