public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] NeoVim and vim-syntax
Date: Thu, 1 Jun 2017 15:54:05 +0100	[thread overview]
Message-ID: <20170601155405.438d42f6@snowblower> (raw)
In-Reply-To: <20170601133801.GA15513@waltdnes.org>

On Thu, 1 Jun 2017 09:38:01 -0400
"Walter Dnes" <waltdnes@waltdnes.org> 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 directory.  
> 
>   As mentioned elsewhere, what happens when two or three other people
> do their own forks?

Nothing, unless those forks obtain large user bases, and then the issue
gets revisited. This is unlikely to happen.

-- 
Ciaran McCreesh


  reply	other threads:[~2017-06-01 14:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-31 19:32 [gentoo-dev] [RFC] NeoVim and vim-syntax Vadim A. Misbakh-Soloviov
2017-05-31 20:09 ` Peter Volkov
2017-05-31 22:54 ` Ciaran McCreesh
2017-06-01  1:21   ` Kent Fredric
2017-06-01  1:38   ` Daniel Campbell
2017-06-01  5:00   ` Michał Górny
2017-06-01  5:49     ` Ciaran McCreesh
2017-06-01  8:42   ` Vadim A. Misbakh-Soloviov
2017-06-01 13:38   ` Walter Dnes
2017-06-01 14:54     ` Ciaran McCreesh [this message]
2017-06-02  1:14     ` Kent Fredric
2017-06-02 19:34       ` Walter Dnes
2017-06-02 19:39         ` Ciaran McCreesh
2017-06-01 21:56 ` Vadim A. Misbakh-Soloviov
2017-06-02  4:59   ` Michał Górny
2017-06-02  7:13     ` Vadim A. Misbakh-Soloviov
2017-07-23 14:17 ` [gentoo-dev] " Patrice Clement
2017-07-23 21:39   ` William Hubbs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170601155405.438d42f6@snowblower \
    --to=ciaran.mccreesh@googlemail.com \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox