| 1 |
On śro, 2017-05-31 at 23:54 +0100, 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 |
...and then vimthreesome for things that work with three vim |
| 34 |
implementations? |
| 35 |
|
| 36 |
-- |
| 37 |
Best regards, |
| 38 |
Michał Górny |
Archives