[desireco42]

How is Neovim working out for you? I remember using it at one point and it was really smooth experience.

[micku]

I'm using it every day for a couple of months now, never crashed and loads faster than Vim 7.

Anyway, the things I appreciate more are the fast evolution and the community, no more than one year ago I tried it but was too lazy to compile, wait, configure...

This time I ran homebrew, linked my .vimrc in ~/.config/nvim/init.vim, and forgot I was using Neovim instead of Vim, except for the async compiling/linting.

[fatbird]

I switched more than a year ago and have never had stability problems; it's been only performance and feature enhancements for me. The most obvious was that saving my files no longer locked up the interface for a couple seconds while linters ran (thank you async). More subtly, I had to go on a plugin diet initially that slimmed my features down to what I actually used regularly; since then, I judge the quality of plugins to be improved because they're either new plugins by authors excited to code for neovim, or they're current plugins that got a decent overhaul to work with both.

From what I understand, the plugin community is generally pretty happy with neovim and find it preferable.

[shazow]

Not the parent but FWIW I've been using neovim for +6 months now and it's fantastic. I'm super impressed at the pace of progress and responsiveness of the team.

I've since switched all my plugins to use async versions and it's sooo fast, didn't think vim could be faster but here we are.

[colordrops]

Could you mention which plugins you switched to? Is there a list somewhere that details the alternatives that work better in neovim?

[shazow]

Off the top of my head:

- vim-plug for a plugin manager (very good regardless of concurrency)

- neomake for building

- vim-go added async job support using neovim a while ago for most of its functionality, which I use for writing Go

My full inventory is here: https://github.com/shazow/dotfiles/blob/master/.vim/plugins....

[kzrdude]

Do most vim plugins work without changes in neovim? I'm mostly using vim-airline and tagbar to be honest, wouldn't be sad if the other ones stopped working.

[hsitz]

VimScript is not deprecated in NeoVim, and maintaining backward compatibility is major focus. So must Vim plugins will work in Neovim. vim-airline is listed among the plugins that has some special neovim-specific features added: https://github.com/neovim/neovim/wiki/Related-projects

[kzrdude]

Cool, thanks.

[cyphar]

I've been using neovim for almost a year now, and have contributed some (small) code fixes and also donate to the project. It works great for me, and I completely forget that I'm using neovim (until I use :terminal). Also, from what I hear, contributing to Vim is much harder than NeoVim so I'm more inclined to contribute to a project which has a healthy community of contributors.

[nobleach]

I am stuck at 0.1.3 as I am unable to brew install any of the newer versions. (It craps out on some LuaJIT stuff and I haven't really had time to fight with it) Aside from having to mess with it to get CTRL-h working, it's been pretty smooth. I LOVED vimplug (the package manager) with its async installs. I have high hopes for NeoVim's future... even if that future turns out to be just giving Vim a kick in the pants to move forward.

[Spiritus]

Try cleaning your Homebrew cache for neovim.

    rm -rf /Library/Caches/Homebrew/neovim--git
    brew reinstall --HEAD neovim

[nobleach]

nope, sadly:

    ==> make VERBOSE=1
    Last 15 lines from /Users/jimwharton/Library/Logs/Homebrew/neovim/02.make:
  "__Unwind_GetCFA", referenced from:
      _lj_err_unwind_dwarf in libluajit.a(lj_err.o)
  "__Unwind_RaiseException", referenced from:
      _lj_err_throw in libluajit.a(lj_err.o)
  "__Unwind_SetGR", referenced from:
      _lj_err_unwind_dwarf in libluajit.a(lj_err.o)
  "__Unwind_SetIP", referenced from:
      _lj_err_unwind_dwarf in libluajit.a(lj_err.o)
    ld: symbol(s) not found for architecture x86_64
    clang: error: linker command failed with exit code 1 (use -v to see invocation)
    make[4]: *** [luajit] Error 1
    make[3]: *** [src/luajit] Error 2
    make[2]: *** [build/src/luajit-stamp/luajit-install] Error 2
    make[1]: *** [CMakeFiles/luajit.dir/all] Error 2
    make: *** [all] Error 2

I know I just need to jump into figuring out how to get the ONE version of LuaJIT that works (as I've read, there is only one) and pop that in there.

[m0shen]

Try:

    unset LUA_CPATH LUA_PATH
    brew reinstall --HEAD neovim

[thedz]

Really great! It was honestly a relatively painless transition for me.