On Thu, 01 Jun 2017 02:32:24 +0700 "Vadim A. Misbakh-Soloviov" <gen...@mva.name> wrote: > - implementing "nvim-syntax" (and `app-nvim/*`?) and duplicate all > the installed files > > - patching NeoVim source to include Vim's runtimedirs (incl. "after" > dir), // NeoVim upstream highly disagree with such way, if any > > - patching VIMRUNTIME environment variable, > > - making a wrapper, > > - rewrite all the existing ebuilds to take nvim into account and > force all newcomers to also take it, > > - symlinking a directory, > // mostly bad way, since opposite plugin compatibility is not > garanteed and users can install nvim-only plugins in the future > > - making postinst hook to regenerate content of NeoVim's > site-directory (maybe, by symlinking installed vim modules there) > > or even: > > - making eselect module for user to rule that.
- Have a separate anyvimishthing directory, and make both vim and neovim look there, and only make plugins that have been tested to work with both install to that directory. -- Ciaran McCreesh
