1 |
On 05/31/2017 03:54 PM, Ciaran McCreesh wrote: |
2 |
> On Thu, 01 Jun 2017 02:32:24 +0700 |
3 |
> "Vadim A. Misbakh-Soloviov" <gentoo@×××.name> wrote: |
4 |
>> - implementing "nvim-syntax" (and `app-nvim/*`?) and duplicate all |
5 |
>> the installed files |
6 |
>> |
7 |
>> - patching NeoVim source to include Vim's runtimedirs (incl. "after" |
8 |
>> dir), // NeoVim upstream highly disagree with such way, if any |
9 |
>> |
10 |
>> - patching VIMRUNTIME environment variable, |
11 |
>> |
12 |
>> - making a wrapper, |
13 |
>> |
14 |
>> - rewrite all the existing ebuilds to take nvim into account and |
15 |
>> force all newcomers to also take it, |
16 |
>> |
17 |
>> - symlinking a directory, |
18 |
>> // mostly bad way, since opposite plugin compatibility is not |
19 |
>> garanteed and users can install nvim-only plugins in the future |
20 |
>> |
21 |
>> - making postinst hook to regenerate content of NeoVim's |
22 |
>> site-directory (maybe, by symlinking installed vim modules there) |
23 |
>> |
24 |
>> or even: |
25 |
>> |
26 |
>> - making eselect module for user to rule that. |
27 |
> |
28 |
> - Have a separate anyvimishthing directory, and make both vim and |
29 |
> neovim look there, and only make plugins that have been tested to work |
30 |
> with both install to that directory. |
31 |
> |
32 |
|
33 |
+1, though it's still important to keep nvim- and vim-specific dirs. |
34 |
|
35 |
A third, common dir cuts down on the work that other solutions would |
36 |
need. It would also give users a way to check which plugins will work |
37 |
with 'the other one' too and can use that to decide whether they want to |
38 |
make the switch. This information can probably be gleaned on their own |
39 |
with some detective work on the Web, but choosing this path gives the |
40 |
accidental feature for free. |
41 |
|
42 |
~zlg |
43 |
|
44 |
-- |
45 |
Daniel Campbell - Gentoo Developer |
46 |
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net |
47 |
fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 |