desync between neovim and vscode
See original GitHub issueI’m running into a problem where the cursor desyncs and I find it difficult to provide a reproducible case for the issue. @asvetliakov is there a group of files one can provide so you can get an idea of what could be going wrong in neovim or vscode itself when an issue appears?
eg. some kind of neovim input log or vscode log file?
Anyways, here’s the issue
As you can see, the cursor doesn’t want to select text that is actually there. But then, also when I do ‘dd’, it deletes the line below (}
) instead of the this.$router.push
line
vscode-neovim 0.0.45 nvim 0.4.3 with empty init.vim and no plugins vscode 1.41.1 ubuntu 19.04
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (11 by maintainers)
Top Results From Across the Web
desync between neovim and vscode · Issue #125 - GitHub
I'm running into a problem where the cursor desyncs and I find it difficult to provide a reproducible case for the issue.
Read more >Why I chose vscode-neovim over VSCodeVim | In the Middle
A comparison between the two VSCode Vim extensions.
Read more >VSCode Neovim - Visual Studio Marketplace
Neovim is a fork of VIM to allow greater extensibility and integration. This extension uses a fully embedded Neovim instance, no more half- ......
Read more >Integrating VSCode With Neovim | Barbarian Meets Coding
Copy the content of your file inside Neovim. Execute the command in Neovim. Sync the results back to Visual Studio Code. This means...
Read more >Rant: Neovim is less productive than VS Code - Reddit
Not that we can't setup the neovim configuration, we DON'T WANT TO. I feel this issue shouldn't be yet another person's issue in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yep line number is not related, I just happened to add the working case at the bottom.
a",
could’ve been in the middle. I’ll keep looking regarding 116, recently it started happening after changing editor groups but I couldn’t repro twice.assuming it’s some kind of #116 then. If you can provide full repro steps it’d help very much.