News for hackers. Stuff that matters.
Re:Python in Visual Studio Code by rraval on Thursday September 06, 2018 @09:54AM (#17926260)
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 [2] https://github.com/onivim/oni

Re:Python in Visual Studio Code by chillee on Thursday September 06, 2018 @11:17AM (#17926874)
Ooohhh, 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.

Re:Python in Visual Studio Code by lingz on Thursday September 06, 2018 @10:36AM (#17926602)
Yeah 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?
Re:Python in Visual Studio Code by jamesgeck0 on Thursday September 06, 2018 @11:03AM (#17926773)
The maintainer of vscodevim has done a lot of work on a plugin that uses such a bridge. :-)
Re:Python in Visual Studio Code by ericmccarthy7 on Thursday September 06, 2018 @11:53AM (#17927125)
sounds like https://www.onivim.io/ to me