Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Normal mode latency #140

alexozer opened this issue Jan 7, 2020 · 2 comments

Normal mode latency #140

alexozer opened this issue Jan 7, 2020 · 2 comments


Copy link

@alexozer alexozer commented Jan 7, 2020

I find that there is a notable bump in input latency while navigating in normal mode as compared to that of the vscodevim extension. Is there any plan to address this?


This comment has been minimized.

Copy link

@asvetliakov asvetliakov commented Jan 7, 2020

Check readme section and #129

This issue is caused by some 3rd party vscode extension which renders decorators very often (like indent guides, bracket HL extension, etc...)
Also may be caused if you're trying to use remote neovim (from WSL for example) by explicitly overriding extensionKind to workspace


This comment has been minimized.

Copy link

@alexozer alexozer commented Jan 8, 2020

So I made a minimal vim config just for vscode-neovim with none of my normal vim plugins or other settings like so...

if exists('g:vscode')
  " Leader
  let mapleader = ","
  let maplocalleader = "\\"

  " Make Y behave like D and C, instead of like yy
  nnoremap Y y$

  " Much better use of H and L
  noremap H ^
  noremap L $

  " Allow using ; to access command mode in normal and visual mode
  noremap ; :
  noremap : ;

" ...

And now vscode-neovim seems to have comparable, if not better latency than vscodevim! So that was probably the issue. Thanks!

I would probably mention somewhere in the README under the performance section that Vim plugins/settings may cause latency specifically, rather than just "performance problems (likely cursor jitter)".

@alexozer alexozer closed this Jan 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.