From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 0A349139694 for ; Wed, 31 May 2017 20:09:54 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8159BE0F67; Wed, 31 May 2017 20:09:34 +0000 (UTC) Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 043BFE0F5D for ; Wed, 31 May 2017 20:09:29 +0000 (UTC) Received: by mail-lf0-x22f.google.com with SMTP id c184so10779765lfe.2 for ; Wed, 31 May 2017 13:09:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+uRem6C9sJByqIxdDpyjqyjN+5pZGjNiG+9qR8azNLk=; b=BIMt8cI6H6d8GxOry0JBNmeVw21CFSzaJaXHjrSyHBKN08U6cYMzCgqCReH0zu//EE Mk/Z60ZxIunv7dmm6WjICrnKiL28+zFCXkPH7/D/SK9bm90QUg5qaZiA4vuFbc7s9FYm S8qF6mRfJwGn/hey0VKCRiKcBu3IvqIkJSEyGh6FPsY+Oqyd/hkQJzruicRJuhyjXjJz 5V/t2l25qWWKJMMwTvY/j8gVWXSHu5fShv6P8N9I16V8qcbVX4A7zK4Q8kWZnqpYLBnx G35TrBQyt1MhgySQX0wl/nvcRRb0GE2rjgB0WNzkp6WossWMppMg9/fLbF1k0ZjYZa7u qj7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+uRem6C9sJByqIxdDpyjqyjN+5pZGjNiG+9qR8azNLk=; b=sr9amw3teIVLyN32R7+uClwuZx0zhJ/TckLTm0yVa30kmjeoEh/ybk3f/gXnYId+lZ yYIZpvtzl9I3AVXZOOToH3bQVEJCpecxKTyfFBJIJApS5f3L6g+L7MeymA0SJD7soBzK GpWQYYdwFVOS9BLUvgdCxs2hakHaoFCfm3bNfiHGZi3/PZ5PxybpGm5PO1Ntox9GePD0 7uxkVypb4q90HLweDRmZ9GcGvecmgQk5g9sBpJwJnDR10Jtuc2VDt0j3LO2P+Djdsh/r bOz2xK4cL/YPELS6IL3y8wODt5t7scQr+ieggeULCsc4URu0VDP61BwbePyB9YiYZ8GI Nq2Q== X-Gm-Message-State: AODbwcC58apdexhwObOG5BZ1lqmR1FwVJgidnDSKCfRijgL6CbljHnns 7YTKHzFtSh+RFNuTgM4IpDijskkw/w== X-Received: by 10.25.152.79 with SMTP id a76mr7603071lfe.165.1496261367361; Wed, 31 May 2017 13:09:27 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Received: by 10.25.165.4 with HTTP; Wed, 31 May 2017 13:09:06 -0700 (PDT) In-Reply-To: <15162118.1WtZIBpG5a@note> References: <15162118.1WtZIBpG5a@note> From: Peter Volkov Date: Wed, 31 May 2017 23:09:06 +0300 Message-ID: Subject: Re: [gentoo-dev] [RFC] NeoVim and vim-syntax To: gentoo-dev@lists.gentoo.org Cc: vim@gentoo.org Content-Type: multipart/alternative; boundary="001a11401bc44af6b50550d77fb9" X-Archives-Salt: e0fbbb7a-2e40-407e-a26d-30c53bb74ca8 X-Archives-Hash: e9536a20e3190ca0b2bacd87023c8f7a --001a11401bc44af6b50550d77fb9 Content-Type: text/plain; charset="UTF-8" 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't find any evidence of the opposite), so it is possible to fix that > situation by many of "kludge" ways, including: > > - patching NeoVim source to include Vim's runtimedirs (incl. "after" dir), > // NeoVim upstream highly disagree with such way, if any But what is the reasoning for upstream from this way? If NeoVim supports vim plugins but not vice versa this looks as a very logical step. -- Peter. --001a11401bc44af6b50550d77fb9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi.

On Wed, May 31, 2017 at 10:32 PM, Vadim A. Misb= akh-Soloviov <gentoo@mva.name>= 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&= #39;s plugins/scripts very well (although I
> didn't find any evi= dence of the opposite), so it is possible to fix that
> situation by = many of "kludge" ways, including:
>
> - patching NeoV= im source to include Vim's runtimedirs (incl. "after" dir),> // NeoVim upstream highly disagree with such way, if any

But = what is the reasoning for upstream from this way? If NeoVim supports vim pl= ugins but not vice versa this looks as a very logical step.

<= div>--
Peter.
--001a11401bc44af6b50550d77fb9--