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 5E4BC139694 for ; Fri, 2 Jun 2017 19:34:53 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 222B2E0D6F; Fri, 2 Jun 2017 19:34:43 +0000 (UTC) Received: from ironport2-out.teksavvy.com (ironport2-out.teksavvy.com [206.248.154.181]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E2435E0D0B for ; Fri, 2 Jun 2017 19:34:42 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0DbBgCivDFZ/zaHSC1dHQEFAQsBg1gjP4ENiH+FDHORBysBlVCCDyyCQoMwBAICgntAGAECAQEBAQEBAWsohRkBBTocMwsYCRMSDwUlN4oqELFWixUBAQgCJoVuc4RLNIU2gnWCMQWeLwGCE4UNi32CaIghGYZllFwfOIEKgQEIRochJDaJcwEBAQ X-IPAS-Result: A0DbBgCivDFZ/zaHSC1dHQEFAQsBg1gjP4ENiH+FDHORBysBlVCCDyyCQoMwBAICgntAGAECAQEBAQEBAWsohRkBBTocMwsYCRMSDwUlN4oqELFWixUBAQgCJoVuc4RLNIU2gnWCMQWeLwGCE4UNi32CaIghGYZllFwfOIEKgQEIRochJDaJcwEBAQ X-IronPort-AV: E=Sophos;i="5.39,286,1493697600"; d="scan'208";a="314314072" Received: from 45-72-135-54.cpe.teksavvy.com (HELO waltdnes.org) ([45.72.135.54]) by smtp.teksavvy.com with SMTP; 02 Jun 2017 15:34:40 -0400 Received: by waltdnes.org (sSMTP sendmail emulation); Fri, 02 Jun 2017 15:34:19 -0400 From: "Walter Dnes" Date: Fri, 2 Jun 2017 15:34:19 -0400 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [RFC] NeoVim and vim-syntax Message-ID: <20170602193419.GA23270@waltdnes.org> References: <15162118.1WtZIBpG5a@note> <20170531235459.605dd783@snowblower> <20170601133801.GA15513@waltdnes.org> <20170602131431.3af64873@katipo2.lan> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170602131431.3af64873@katipo2.lan> User-Agent: Mutt/1.5.24 (2015-08-30) X-Archives-Salt: c56455db-07f3-4179-997b-0986b35b0bbc X-Archives-Hash: e72d11a74f5edad88adde4d4539a2c7d 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 A and C and D but not B. The > > number of directories could potentially be 2^N where N is the number > > of forks. And who's going to do the necessary testing across > > multiple versions? And remember that each minor version bump of any > > of the forks could render another fork's plugin incompatable. This > > is a classic "moving target". The only way that works is to have > > each fork look after their own copies of plugins. > > If and when that happens: It already has happened. Compare /usr/portage/app-editors against http://texteditors.org/cgi-bin/wiki.pl?ViFamily Portage has... * elvis * levee * nvi * vi * vim * vis ...not to mention neovim, which doesn't show up on texteditors.org. > "4" could alternatively be implemented by creating a meta-file that > enumerates a list of source files to symlink, and the list of vim > implementations that are known to be supported by it, and then a > tool can fix up the difference in pkg_postinst or on-demand. This would require a multi-dimensional array of approx 7 packages (today) versus however many ebuilds are currently in Portage for each editor. Do I see any volunteers for compatibility testing for all current and future VI-family editors and plugins on all current and future ebuilds on all arches (small and large endian) and various USE flags? And what happens when 2 or more editors make different plugins with the same file names? This is not a "software ecosystem", and the various upstreams are not obligated to co-operate with each other. Indeed, the reason for a fork may be bad blood between developers in the first place. A lot of complexity to save a few kbytes on a multi-terabyte hard drive (even a 128 gig SSD) does not make sense. And it may actually use more space in the long run. If I have only vim, do I really want everybody else's plugins installed? No. But if I do switch over to another VI-family editor, or install one simultaneously, how does a separate "plugins package" know which plugins to install? And if I uninstall one editor, how does the "plugins package" know which plugins to uninstall? -- Walter Dnes I don't run "desktop environments"; I run useful applications