Hi, Neovim is a valid alternate to vim and eclass should be updated allow neovim as a valid alternate. Reproducible: Always Steps to Reproduce: 1. Install neovim, emerge -C app-editors/vim app-editors/vim-core 2. emerge -pv gentoo-syntax (or any other vim-plugin) Actual Results: app-editors/vim and app-editors/vim-core are pulled in as dependency Expected Results: app-editors/vim should be optional if app-editors/neovim is installed
Assigned to radhermit; Eclass doesn't list maintainers.
I don't think neovim is fully compatible with all vim plugins so I'm not sure this is a good idea right now.
After year, Neovim community seems to still growing, maybe it's time right now?
> I don't think neovim is fully compatible with all vim plugins so I'm not sure this is a good idea right now. I am yet to see modern ViM plugin not compatible with NeoVim. However, if we adopt multiple VIM_TARGETS (see bug 612644, for example), then this will not be a problem: just exclude neovim from list of supported implementations and that's it.
Probably just something like virtual/vim (referring to vim, gvim and neovim packages) might be enough. If a maintainer of some package considers it to be incompatible with nvim, the explicit dependencies may be kept. Same way e.g. virtual/jdk is referring to different JDK implementations, while certain packages can still set explicit dependency on Oracle JDK.
One difficulty is that neovim uses /usr/share/nvim/runtime instead of /usr/share/vim/vimfiles, so the vim-plugin eclass would need some modification at a minimum. Parameterizing it would be straight forward, but we'd still probably require something like python to ensure that a plugin built for both vim and nvim, so the solution suggested in bug 612644 is probably still the right direction to go...
