I was just looking at the vim-go milestones and I noticed the following note for the upcoming switch to version 2.0 of vim-go:
I was wondering why that decision was taken, how it will impact NeoVim users, like myself, and if there are other vim-go users that are using nvim and might be affected?
preslavmihaylov
All 3 comments
There are absolutely other NeoVim users this would affect, if support is possibly dropped.
mnarrell
on 2 Oct 2019
It's something we've talked about. There is no timeline for vim-go 2.0, and nothing is written in stone yet.
Neovim is not Vim. It's a Vim clone in the same way that Vim is a Vi clone, and it continues to diverge. The effort it takes to deal with the divergence is often quite frustrating, so dropping support for Neovim is something that Fatih and I discussed last year as a possibility for vim-go 2.0 if it ever happens.
bhcleek
on 2 Oct 2019
I should point out that most of the problems with Neovim within vim-go are solved, but Neovim's bifurcation of the API is causing the same problems for plugins that Neovim sought to solve with regard to Vim's support for lots of old and archaic operating systems. e.g. branching to support different apis to do the same thing in two different systems.
bhcleek
on 2 Oct 2019
Related issues
danielmanesku
路
4Comments
smontazeran
路
4Comments
korjavin
路
4Comments
svanharmelen
路
3Comments
jongillham
路
3Comments
Most helpful comment
It's something we've talked about. There is no timeline for vim-go 2.0, and nothing is written in stone yet.
Neovim is not Vim. It's a Vim clone in the same way that Vim is a Vi clone, and it continues to diverge. The effort it takes to deal with the divergence is often quite frustrating, so dropping support for Neovim is something that Fatih and I discussed last year as a possibility for vim-go 2.0 if it ever happens.