On Fri, 2 Jun 2017 15:34:19 -0400
"Walter Dnes" wrote:
> On Fri, Jun 02, 2017 at 01:14:31PM +1200, Kent Fredric wrote
> > On Thu, 1 Jun 2017 09:38:01 -0400
> > "Walter Dnes" wrote:
> >
> > > As mentioned elsewhere, what happens when two or three other
> > > people do their own forks? Plugin
On Fri, Jun 02, 2017 at 01:14:31PM +1200, Kent Fredric wrote
> On Thu, 1 Jun 2017 09:38:01 -0400
> "Walter Dnes" wrote:
>
> > As mentioned elsewhere, what happens when two or three other
> > people do their own forks? Plugin 1 works with vim A and B but
> > not C or D. Plugin 2 works with vim
> strongly against eselect modules (and any user code) that
> writes into /usr (except for /usr/local)
Well, NeoVim, at least, have support for site-dir in /usr/local out of the
box. I guess, Vim8 will need a bit of patching for that.
Although, I'm, in opposite, dislike (very little, tho) /usr/l
On pią, 2017-06-02 at 04:56 +0700, Vadim A. Misbakh-Soloviov wrote:
> 1) Dear Vim Team, can we hear your opinions?
>
> 2) I'd like to know if discussion participants really differs my eselect-php-
> like suggestion (where all scripts goes to another directory, controlled by
> neither of vims, and
On Thu, 1 Jun 2017 09:38:01 -0400
"Walter Dnes" wrote:
> As mentioned elsewhere, what happens when two or three other people
> do their own forks? Plugin 1 works with vim A and B but not C or D.
> Plugin 2 works with vim A and C and D but not B. The number of
> directories could potentially b
1) Dear Vim Team, can we hear your opinions?
2) I'd like to know if discussion participants really differs my eselect-php-
like suggestion (where all scripts goes to another directory, controlled by
neither of vims, and then users should/can manually dis-/enable modules for
each of vim they want
On Thu, 1 Jun 2017 09:38:01 -0400
"Walter Dnes" wrote:
> On Wed, May 31, 2017 at 11:54:59PM +0100, Ciaran McCreesh wrote
> > - 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 di
On Wed, May 31, 2017 at 11:54:59PM +0100, Ciaran McCreesh wrote
> - 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.
As mentioned elsewhere, what happens when two or th
> - 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.
Actually it is almost the thing I described as "second" eselect variant.
Although, you suggest for gentoo devs to chec
On Thu, 01 Jun 2017 07:00:30 +0200
Michał Górny wrote:
> > - 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.
>
> ...and then vimthreesome for things that work with t
On śro, 2017-05-31 at 23:54 +0100, Ciaran McCreesh wrote:
> On Thu, 01 Jun 2017 02:32:24 +0700
> "Vadim A. Misbakh-Soloviov" wrote:
> > - implementing "nvim-syntax" (and `app-nvim/*`?) and duplicate all
> > the installed files
> >
> > - patching NeoVim source to include Vim's runtimedirs (incl. "
On 05/31/2017 03:54 PM, Ciaran McCreesh wrote:
> On Thu, 01 Jun 2017 02:32:24 +0700
> "Vadim A. Misbakh-Soloviov" wrote:
>> - implementing "nvim-syntax" (and `app-nvim/*`?) and duplicate all
>> the installed files
>>
>> - patching NeoVim source to include Vim's runtimedirs (incl. "after"
>> dir),
On Wed, 31 May 2017 23:54:59 +0100
Ciaran McCreesh wrote:
> - 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
pgpmXJgzQwGtk.pgp
Description: OpenPGP digital signa
On Thu, 01 Jun 2017 02:32:24 +0700
"Vadim A. Misbakh-Soloviov" 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 an
Hi.
On Wed, May 31, 2017 at 10:32 PM, Vadim A. Misbakh-Soloviov
wrote:
> Currently, we have a situation, that there are two Vim's: "old" one
(vim8) and
> NeoVim... Unfortunately, both of them have different runtimedirs...
>
> ... NeoVim supports Vim's plugins/scripts very well (although I
> didn'
Currently, we have a situation, that there are two Vim's: "old" one (vim8) and
NeoVim (for those who do not know: a fork of Vim with much and much more clean
code, many neat features and so on).
Unfortunately, both of them have different runtimedirs: XDG ones for NeoVim
and the ones you know fo
16 matches
Mail list logo
