3 ms·
My setup is neovim + VSCode + VSCode Neovim + clangd with which I am extremely happy. I am otherwise a vanilla vim user.
by CalChris 5y ago
My setup is neovim + VSCode + VSCode Neovim + clangd with which I am extremely happy. I am otherwise a vanilla vim user.
- city41 5y agoThat's also my setup. I find VSCode Neovim can get out of sync at times. The fix seems to be to close the document and re-open it. Not knocking the plugin, it has to be quite the task to get the integration working perfectly. But yeah, overall it's an excellent combo.
- dharmaturtle 5y agoI have this out-of-sync issue as well. I was previously blaming it on a Clojure plugin (Calva), but I'm guessing you don't have that. Wish I could reliably recreate - it happens once or twice a day.
- kristiandupont 5y agoI tried out vscode-neovim at one point but switched back to vscodevim. I don't actually remember what the problems were but I do remember thinking that vscodevim was the lesser evil. It's pretty hard when coming from regular vim, but I live with it. But maybe things have changed?
- CalChris 5y agoPost 0.5 neovim, vscode-neovim is great, well for me it is. But there were three problems. Command mode sucked but it's much better now. If I could close the results window with an escape character, that'd be just great. If you navigate right with the space bar, it screws up the line. Right arrow works fine. However, I think this is a VSC problem. :e! fixes the problem. If you do any editing immediately after opening, it just inserts your keystrokes at the beginning. It would be better to buffer or ignore them. I also think this is a VSC problem. :e! fixes the problem. I only added clangd very recently. It obviates You Complete Me, ctags and much of clang-tidy. It refactors. It's an awesome code navigator. https://clangd.llvm.org/features https://clangd.llvm.org/features I still use neovim from the command line occasionally. But since they've fixed command mode, that's less and less.
- kristiandupont 5y agoThank you. Maybe I should give it a try again. I am also frequently considering creating a vscode extension that just opens a file in a terminal-based vim instance, sitting in a tab. I think that would be possible and it would be a nice fall-back..