From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Vadim A. Misbakh-Soloviov" <gentoo@mva.name>, vim@gentoo.org
Subject: Re: [gentoo-dev] Re: [RFC] NeoVim and vim-syntax
Date: Sun, 23 Jul 2017 16:39:47 -0500 [thread overview]
Message-ID: <20170723213947.GA1399@linux1.home> (raw)
In-Reply-To: <20170723141710.GA8732@patriceclement.me>
[-- Attachment #1: Type: text/plain, Size: 1367 bytes --]
On Sun, Jul 23, 2017 at 04:17:10PM +0200, Patrice Clement wrote:
> Hi Vadim and thank for your email.
>
> Sorry for taking so long to respond, been busy with work, life, etc.
>
> Thursday 01 Jun 2017 02:32:24, Vadim A. Misbakh-Soloviov wrote :
> > 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).
> Vim8 is here to stay and has served us well until now. Calling him "old" is
> unfair. :)
>
> To be honest, I haven't given NeoVim a try yet (should I?).
> >
> > Unfortunately, both of them have different runtimedirs: XDG ones for NeoVim
> > and the ones you know for Vim8, while NeoVim is fully compatible with Vim's
> > plugins, and epecially with vimscripts (like syntax definitions and ftdetect
> > scripts).
> ACK. I have one question though: will this retrocompatibility last forever?
If we aren't sure that compatibility will go both ways forever, e.g.
neovim will always support vim8 files and vim8 will always support
neovim files, I do not recommend making them both use the same runtime
directory. I imagine upstream neovim set a different runtime directory
so that if they diverge things won't break, and I wouldn't try to merge
the runtime directories.
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2017-07-23 21:40 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
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 [this message]
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=20170723213947.GA1399@linux1.home \
--to=williamh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo@mva.name \
--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