17

I am stuck on windows 10 and would like to give Neovim a shot. Is it ready, or should I just set up my vim configuration for the moment? I haven't really seen any videos or articles on Neovim under windows, but when googling, I found a few that lead me to believe there may have been issues that have not yet been adequately resolved.

  • One comment I have is that the only working binary I've found is from build 658 – DJMcMayhem Jun 18 '16 at 5:53
10

As stated on neovim wiki:

Windows support is (currently) experimental. To try it out, you need nvim.exe and a front-end such as Neovim-Qt.

However there isn't a list of all features that are missing or unstable. The best way to discover is actually installing and trying.

  • I got nowhere with it. Hangs, small windows etc. They've not updated the pre-built one for months. I've given up on it; I'll try again when they reach v1. (I use it every day on various linux boxes without issue). – user859 Oct 5 '17 at 12:08
  • 1
    @DrEval Please see my answer. – Sardathrion - Reinstate Monica Oct 9 '17 at 9:14
  • @Sardathrion I tried and that version has the same problem. White background I cannot shift no matter what i've tried. – user859 Oct 19 '17 at 14:43
  • @DrEval That happens from time to time when neovim-qt loses contact with neovim… But it should not happen often. – Sardathrion - Reinstate Monica Oct 19 '17 at 14:54
  • @Sardathrion It happens every single time and I have no way of configuring neovim-qt. – user859 Oct 19 '17 at 14:57
4

Using chocolatey, you can install neovim like thus:

choco install neovim

Add --pre if you want the latest pre-release. It will install nvim-qt as well.

All in all, consider it beta software. However, it works well enough for my needs.

3

One way to run NeoVim on Windows 10 is through "bash on windows". After setting up ubuntu on bash on windows, you can just install NeoVim the same way you would on a Ubuntu machine (add the PPA, etc.).

You will need at least Windows Insider Preview Build 14366 and NeoVim 0.1.5-dev (prior to this build it would crash).

You might wish to wait until the proper release of the Windows 10 anniversary update, though.

https://github.com/neovim/neovim/issues/4507

https://wpdev.uservoice.com/forums/266908-command-prompt-console-bash-on-ubuntu-on-windo/suggestions/13390779-neovim-crashes-on-bash-on-windows

  • 1
    As of 2017-02-24, this is working well for me. I had problems using terminal ConEmu (getting 256 colors working is a hassle, and doing so seemed to break cursor keys etc - they would in Bash but not in nvim. So I switched to wsl-terminal (github.com/goreliu/wsl-terminal) which is less fully featured, but all the above just works out of the box. – Jonathan Hartley Feb 24 '17 at 21:45
  • 1
    Actually, one problem I still have with this set up is that it's easy to paste INTO Neovim, but I haven't yet figured out how to cut/copy text out of it. I have xsel installed, but neovim CheckHealth says "no clipboard tool found". I'm resorting to catting the file in a terminal and selecting it there to copy. Dreading the day when my Windows-oriented colleagues see me doing it. :-) – Jonathan Hartley Feb 24 '17 at 22:02
  • @JonathanHartley at my day job I'm now on a Mac, but this looks relevant: github.com/neovim/neovim/issues/3147 best of luck, I know what it's like stuck on windows :( – aikeru Feb 27 '17 at 21:48
  • Thanks. I read that clipboard between Windows and WSL can be fixed by getting XMing running (A Windows port of X-Windows, I think, which is much easier to get running than you'd expect) and then clipboard management programs like xsel or xclip work just fine. github.com/Microsoft/BashOnWindows/issues/… – Jonathan Hartley Feb 27 '17 at 22:33

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.