public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Vadim A. Misbakh-Soloviov" <gentoo@mva.name>
To: gentoo-dev@lists.gentoo.org
Cc: vim@gentoo.org
Subject: Re: [gentoo-dev] [RFC] NeoVim and vim-syntax
Date: Fri, 02 Jun 2017 04:56:36 +0700	[thread overview]
Message-ID: <2441749.gsc6QkMBCV@note> (raw)
In-Reply-To: <15162118.1WtZIBpG5a@note>

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) from Ciaran's suggestion of making a directory common 
for all vims, patch all the vims, and force *developers* to check modules and 
put them there only after check modules under both (currently) vims (as side 
effect leave neovim users without modules until developers finaly finish that 
work).

And what point they (participants) really supports?

3) Again, dear Vim Team, please come here, and take a part in the discussion.


  parent reply	other threads:[~2017-06-01 21:56 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
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 [this message]
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=2441749.gsc6QkMBCV@note \
    --to=gentoo@mva.name \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=vim@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