Bug description
I reported the latency bug in the neovim-vscode repo: vscode-neovim/vscode-neovim#2538
To Reproduce
- Look at the repo issue for lua config file
- Setup a
<leader> binding using the config in that issue
Expected behavior
Pressing <leader> should show which key pretty quickly.
Additional context
I'm using Lazyvim and Neovim VSCode plugin and Lazyvim has this nice feature where all the plugins are off by default when using the Neovim VSCode plugin except for plugins where vscode = true. This way I can write a lua config file that binds keybinds using which-key.nvim plugin and set vscode = true so that these keybinds are for vscode. In this way, I can run vscode.action (apart of Neovim VSCode plugin) to run the "whichkey.show" vscode command. But, that's running poorly (latency is too high).
System information
macOS 15.6 (24G84)
NVIM v0.11.1
Bug description
I reported the latency bug in the neovim-vscode repo: vscode-neovim/vscode-neovim#2538
To Reproduce
<leader>binding using the config in that issueExpected behavior
Pressing
<leader>should show which key pretty quickly.Additional context
I'm using Lazyvim and Neovim VSCode plugin and Lazyvim has this nice feature where all the plugins are off by default when using the Neovim VSCode plugin except for plugins where
vscode = true. This way I can write a lua config file that binds keybinds usingwhich-key.nvimplugin and setvscode = trueso that these keybinds are for vscode. In this way, I can runvscode.action(apart of Neovim VSCode plugin) to run the"whichkey.show"vscode command. But, that's running poorly (latency is too high).System information
macOS 15.6 (24G84)
NVIM v0.11.1