On 05/31/2017 03:54 PM, Ciaran McCreesh wrote: > 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. >
+1, though it's still important to keep nvim- and vim-specific dirs. A third, common dir cuts down on the work that other solutions would need. It would also give users a way to check which plugins will work with 'the other one' too and can use that to decide whether they want to make the switch. This information can probably be gleaned on their own with some detective work on the Web, but choosing this path gives the accidental feature for free. ~zlg -- Daniel Campbell - Gentoo Developer OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6
signature.asc
Description: OpenPGP digital signature