Fix which-key delay settings (#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.
8ab96b38a2/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.
			
			
This commit is contained in:
		
							parent
							
								
									7ddaab3ffd
								
							
						
					
					
						commit
						a8f539562a
					
				
							
								
								
									
										4
									
								
								init.lua
								
								
								
								
							
							
						
						
									
										4
									
								
								init.lua
								
								
								
								
							|  | @ -135,7 +135,6 @@ vim.opt.signcolumn = 'yes' | |||
| vim.opt.updatetime = 250 | ||||
| 
 | ||||
| -- Decrease mapped sequence wait time | ||||
| -- Displays which-key popup sooner | ||||
| vim.opt.timeoutlen = 300 | ||||
| 
 | ||||
| -- Configure how new splits should be opened | ||||
|  | @ -274,6 +273,9 @@ require('lazy').setup({ | |||
|     'folke/which-key.nvim', | ||||
|     event = 'VimEnter', -- Sets the loading event to 'VimEnter' | ||||
|     opts = { | ||||
|       -- delay between pressing a key and opening which-key (milliseconds) | ||||
|       -- this setting is independent of vim.opt.timeoutlen | ||||
|       delay = 0, | ||||
|       icons = { | ||||
|         -- set icon mappings to true if you have a Nerd Font | ||||
|         mappings = vim.g.have_nerd_font, | ||||
|  |  | |||
		Loading…
	
		Reference in New Issue
	
	 Ryan Jensen
						Ryan Jensen