Vscode-neovim: Support current Neovim release

[pedrominicz]

Support the latest _release_ of Neovim. Not even Archlinux is on 0.5.0. I don't see what big change could make it worth while to inconvenience users to manually install a nightly build.

An okay compromise would be instructing users how to downgrade the extension to work with current Neovim.

[asvetliakov]

An okay compromise would be instructing users how to downgrade the extension to work with current Neovim.

0.0.52 is the latest version which works with neovim 0.4

I can't support neovim 0.4 anymore because cursor positioning worked through clunky workaround previously - it was using set number to render line numbers in neovim do determine current real cursor position in a buffer based on string in the gutter. Yeah, funny, and error prone. Thankfully, neovim devs implemented correct ui event but it's available in 0.5 nightly only.

You don't need to have neovim 0.5 installed system wide. You can drop off the tarball into some directory and just use it for vscode, while continue using 0.4 from your package manager for your daily non-vscode needs.

[AprilArcus]

You should have waited to ship improved cursor positioning until 0.5 was released.

[asvetliakov]

The previous method was the big headache, so i'd say working cursor instead of improved. I don't see a big problem dropping a tarball of neovim nightly or running brew install neovim --HEAD. But i see a big headache of trying to keep old way.

Anyway, this is free OSS software, so if you would like to work on PR which will restore old cursor behavior for 0.4 (either under configuration flag or by neovim version checking) - i'd be happy to review and accept it.

[pedrominicz]

From a developer point of view I 100% understand you. Reading about the cursor problem made me empathize with your decision. However, from the user point of view the plugin just randomly started warning about an update then broke. Installing from a tarball isn't hard, but isn't ideal for user satisfaction (I guess most people find it pretty annoying).

A few suggestions I have:

• Add documentation about installing an older version to the README
• Add a warning to the newest version like "you can install a newer Neovim _or_ downgrade the plugin"
• Make sure people who have downgraded get some sort of notification when Neovim 0.5 gets pushed to, say, Ubuntu's repos (I guess when Ubuntu have it most other distros will)

[JoeSchr]

I love it! Now I finally can work with 2 panes next to another and also editing in diff view works! Keep pushing the envelope!

[hholst80]

I'm using vscode-nightly on 4 different machines so I have to do this four times. But the end result is worth it. Keep up the great work!

[exapsy]

I believe it's still not great idea from a user's experience standpoint to use it on the stable version of the plugin.

I know I'm overanalyzing, but this is what happens from a user's standpoint (by which, I mean mine :P )

1. User installs VSCode neovim plugin (yay! Happy)
2. User sees he can't use the plugin with his neovim's version
3. User now tries to update neovim, because he thinks 0.5+ are stable versions
4. User sees that they cant do that, so maybe the package manager is not updated yet? They have to search for that
5. Oh, apparently, it's not yet stable version. So now they search for this in vscode-neovim's git issues (gets here)
6. Finds out he can use a previous version which didn't use neovim 0.5+

Like, a lot of friction is created because of this. This could have been made as a beta version or something.

Or, at least provide the required information, like a link that leads here or anything that helps in the error dialog, to reduce the friction.

Nonetheless, let's not skip that you guys have done amazing work anyways.

[catofnineswords]

This would be great, but the nightly builds of neovim started failing as of a few weeks ago. (See their travis build issue thread)
This is the problem that gets passed on to users when an application depends on non-released and unstable upstreams.