4 ms·
I would really love to ditch more of my nvim setup for vscode, but this bug [1] from 3 months ago absolutely wrecks my productivity. I rely on splits as the pri
by rraval 8y ago
I would really love to ditch more of my nvim setup for vscode, but this bug [1] from 3 months ago absolutely wrecks my productivity. I rely on splits as the primary means to navigate the codebase and having a single cursor position per file is maddening!
The vim bindings aren't perfect and are sometimes slow (you can see a macro insert things character by character) but about on-par with IdeaVim for the IntelliJ side feature wise.
Maybe oni [2] will catch up before vscode fixes their issues but I eagerly await a decent language server modal editing setup.
[1] https://github.com/VSCodeVim/Vim/issues/2688 https://github.com/VSCodeVim/Vim/issues/2688
[2] https://github.com/onivim/oni https://github.com/onivim/oni
- lingz 8y agoYeah VSCode for Vim feels like they are slowly trying to implement a subset for VSCode. This kind of iterative approach doesn't strike me as a way to build something that will finally "feel right", and overcome these limitations. Perhaps some remote vim running actual nvim code with a minimal API bridge into VSCode is more appropriate?
- jamesgeck0 8y agoThe maintainer of vscodevim has done a lot of work on a plugin that uses such a bridge. :-)
- ericmccarthy7 8y agosounds like https://www.onivim.io/ https://www.onivim.io/ to me
- chillee 8y agoOoohhh, this is something that I've been meaning to get back to... There was an atrociously bad "undoing work" issue that I popped out of hiatus to fix, and that bug was the cost of the fix. I meant to add proper support for that, but me not using splits that much (especially for the same file) as well as other commitments have prevented that.