My cursor is on speed, often leaves VS Code behind.

As you may have noticed in some of my recordings, my cursor is 🏇 🏇 🏇 🏇 🏇 🛒.

I some times move too fast, and VS Code rendering will not be up to date. Or sometimes, VS Code’s cursor will have moved further than mine. Maybe this happens once it has been slammed with all the previous movement, and then VS Code handles the input instead of neovim? I think that may be the case, because sometimes in insert mode I’ll type some stuff, then ctrl+c and start moving with j, but instead I’ll see jjjjjj inputted into the text.

I think this is also more likely to happen when other things are taking up CPU, so that it slows both VS Code and Neovim down.

I noticed the Vim plugin also has the same issue.

[trusktr]

What I experience happens most often when there’s lots of system load and VS Code is operating slowly (I only have 8GB RAM, so working at full mem usage and swap space swapping is usually when it happens). The slowness seems to cause races or something, and then text editing gets out of sync, but it always catches up. When VS Code is slow and I’m trying to edit fast, then sometimes the edits don’t happen where I expected they would (like I would expect with vim on a slow network). Similar to the movement, the edits happen at the erroneous cursor positions before the cursor lands at the correct spots and I’ve already inputted the vim commands before things settle.

[vlwkaos]

I experienced similar issue. on 0.7x versions. Most noticeable for me is when I type ‘o’ to open line in normal mode, it enters insert mode further down the next line. Also I have seen what @trustkr is experiencing too sometimes.