| 1 |
On Wed, May 31, 2017 at 11:54:59PM +0100, Ciaran McCreesh wrote |
| 2 |
|
| 3 |
> - Have a separate anyvimishthing directory, and make both vim and |
| 4 |
> neovim look there, and only make plugins that have been tested to work |
| 5 |
> with both install to that directory. |
| 6 |
|
| 7 |
As mentioned elsewhere, what happens when two or three other people |
| 8 |
do their own forks? Plugin 1 works with vim A and B but not C or D. |
| 9 |
Plugin 2 works with vim A and C and D but not B. The number of |
| 10 |
directories could potentially be 2^N where N is the number of forks. |
| 11 |
And who's going to do the necessary testing across multiple versions? |
| 12 |
And remember that each minor version bump of any of the forks could |
| 13 |
render another fork's plugin incompatable. This is a classic "moving |
| 14 |
target". The only way that works is to have each fork look after their |
| 15 |
own copies of plugins. |
| 16 |
|
| 17 |
This reminds me of Firefox and Pale Moon, except that browser plugins |
| 18 |
are user-installed. After the initial fork from Firefox, plugins were |
| 19 |
mostly compatable amongst the two browsers. Over time, as the code |
| 20 |
diverged, fewer plugins remained compatable (not talking about Firefox's |
| 21 |
upcoming deprecation of XUL). E.g. Pale Moon now has a forked version of |
| 22 |
Ad Block Plus to ensure that it works on Pale Moon.. |
| 23 |
|
| 24 |
-- |
| 25 |
Walter Dnes <waltdnes@××××××××.org> |
| 26 |
I don't run "desktop environments"; I run useful applications |
Archives