This is wrong. According to the documentation it is not vim underneath. It specifically says enabling neovim support will only utilize neovim for ex-commands, NOT for direct editing. You got my hopes up - but this does not solve any of the big issues I have with vim support in vscode.
meh - It's not really vim underneath. This is very misleading from /u/quavan. I set it up and tested it and it still has most of the weaknesses vim extensions had in vscode. In no particular order:
In normal vim, if I type something such as '5873 j', it will immediately jump me to the bottom of the file. This is incredibly slow in vscodevim with neovim.
Undoing large operations in vim is instant, in vscodevim with neovim it is sluggish and laggy.
If it is truly just running neovim in the background, why can't it read my .nvimrc config file? I lose so much power with the weak vscode configuration options.
Why does pressing backspace when I start a command in vscodevim not exit the command? (nitpick but it drives me nuts)
0
u/[deleted] Feb 07 '19
[deleted]