4 ms·
> vim plugin in VSCode. How is that these days? I used it a couple of years ago but it had issues at the time, namely some performance problems and getting stu
by deergomoo 6y ago
> vim plugin in VSCode.
How is that these days? I used it a couple of years ago but it had issues at the time, namely some performance problems and getting stuck in a particular mode.
I ended up abandoning vim bindings because the JetBrains plugin was also buggy, and I straight up had no feasible way to get those bindings in Xcode, but I hold out hope for a glorious LSP-based future where I can just use vim and get all the benefits of my other editors.
- artemave 6y agoIf you haven't already, you might want to check out coc.nvim https://github.com/neoclide/coc.nvim https://github.com/neoclide/coc.nvim
- leppr 6y agoCoc.nvim is awesome. Instead of trying to bring the UI of vim to another editor, coc.nvim brings the "backend" of the other editor to vim. I tried using VSCode with the Vim plugin for a while but the latency and inconsistencies eventually got me back to proper (neo)vim. UIs are almost always more complex and subtle than people intuit, have a large surface area, and make lag and inconsistencies most noticeable.
- MFogleman 6y agoThere are a few. I am using VSCodeVim[1] with the default settings (besides the typical `jj` command) I love it, and using anything else feels weird. I remember having some problems with it before as well, but I haven't bothered looking at the settings or anything for months. I had to go back just now to see if I had any weird configs set up, (I don't) [1]https://github.com/VSCodeVim/Vim.git https://github.com/VSCodeVim/Vim.git