From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22290 invoked by alias); 16 Oct 2017 15:12:09 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 41909 Received: (qmail 6609 invoked by uid 1010); 16 Oct 2017 15:12:09 -0000 X-Qmail-Scanner-Diagnostics: from mailout1.w1.samsung.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(210.118.77.11):SA:0(-6.9/5.0):. Processed in 6.169272 secs); 16 Oct 2017 15:12:09 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: p.stephenson@samsung.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | X-AuditID: cbfec7ef-f79ee6d000003120-b9-59e4cc3b8b0c Date: Mon, 16 Oct 2017 16:11:51 +0100 From: Peter Stephenson To: Mailing-list zsh-workers Subject: Re: GH:zsh-users/zsh-completions. Message-id: <20171016161151.6981579c@pwslap01u.europe.root.pri> In-reply-to: <6529.1508164192@thecus.kiddle.eu> Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPIsWRmVeSWpSXmKPExsWy7djP87rWZ55EGpxZomRxsPkhkwOjx6qD H5gCGKO4bFJSczLLUov07RK4Mqb3tzIX7OGtOPCmja2B8QtXFyMnh4SAicSXY7MZIWwxiQv3 1rN1MXJxCAksY5TY3niUFcLpZZL4f28rE0zH/J4dLHBVqz/3M0I405gk3m2YygzhnGGUWDBh JROEc5ZRonf9HrB+FgFViR2LusA2sgkYSkzdBLFdRMBIYt3u/UA1HBzCAloSF38WgoR5Bewl PhxcANbKKaAv8XT1J3YQmx/Ivvr3E9RJ9hIzr5xhhKgXlPgx+R4LiM0soCOxbdtjdghbXmLz mrdgx0kILGCT+PJ+PStEs4vEsg3H2CBsYYlXx7ewQ9gyEp0dB6EW9DNKPOn2hWiewShx+swO qAZrib7bFxkhNvBJTNo2nRnkAQkBXomONiGIEg+Jt2tmQM1xlJgy+wU07N4xSkx7MolxAqPC LCSHz0Jy+Cwkhy9gZF7FKJJaWpybnlpsqFecmFtcmpeul5yfu4kRmAxO/zv+fgfj0+aQQ4wC HIxKPLwZh55ECrEmlhVX5h5ilOBgVhLhtdwNFOJNSaysSi3Kjy8qzUktPsQozcGiJM5rG9UW KSSQnliSmp2aWpBaBJNl4uCUamBsf5fC53f+1pV/0Wwpljfrd87jVM52L1W1U2vvd9gYJNig c/dQVwevQspO3UW7pY0ynqpvXTnZSD2nZKPT/Y06e6/NUWFwDlb4tymXxfTM2YYTO/wTv58u 1++sX3XSyG7aPB+/yj7bbzw3zRhMf5fpKuzJqT3ne4enLDSV6a6aT7X53iXiC5RYijMSDbWY i4oTARBHlF0CAwAA X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrPLMWRmVeSWpSXmKPExsVy+t/xa7rWZ55EGhzntjjY/JDJgdFj1cEP TAGMUVw2Kak5mWWpRfp2CVwZ0/tbmQv28FYceNPG1sD4hauLkZNDQsBEYn7PDhYIW0ziwr31 bF2MXBxCAksYJRqWz2aHcGYwSfy6v4IFwjnHKHFzVjszhHOWUeLy7t9sIP0sAqoSOxZ1MYLY bAKGElM3zQazRQSMJNbt3s/UxcjBISygJXHxZyFImFfAXuLDwQVMIDangL7E09WfoLa9Y5TY PeUIO0iCHyhx9e8nJoj77CVmXjnDCNEsKPFj8j2wu5mBZm7e1sQKYctLbF7zlhnEFhJQl7hx dzf7BEbhWUhaZiFpmYWkZQEj8ypGkdTS4tz03GJDveLE3OLSvHS95PzcTYzAYN527OfmHYyX NgYfYhTgYFTi4c049CRSiDWxrLgy9xCjBAezkgiv5W6gEG9KYmVValF+fFFpTmrxIUZpDhYl cd7ePasjhQTSE0tSs1NTC1KLYLJMHJxSDYzJ1XcfqV4T3hO+ZNUK61mKex9pf+y6uuqgrX3i kvOnPVqThPo7m8J6Fico3wrPaGc4sE5Y9oCr7l0r5+PrW6bvs181efv9LawdT870O6nMPn6W IfrOpS/Pjs82t3SYs7P59Kelk6Us1nHfuPdwL+/ks9n+MYH3GFgexThUPOewebW6nXuHT02v EktxRqKhFnNRcSIAnBbrXWICAAA= X-CMS-MailID: 20171016151155eucas1p247f398c9c24b0484dc22acc250603123 X-Msg-Generator: CA X-Sender-IP: 182.198.249.179 X-Local-Sender: =?UTF-8?B?UGV0ZXIgU3RlcGhlbnNvbhtTQ1NDLURhdGEgUGxhbmUb?= =?UTF-8?B?7IK87ISx7KCE7J6QG1ByaW5jaXBhbCBFbmdpbmVlciwgU29mdHdhcmU=?= X-Global-Sender: =?UTF-8?B?UGV0ZXIgU3RlcGhlbnNvbhtTQ1NDLURhdGEgUGxhbmUbU2Ft?= =?UTF-8?B?c3VuZyBFbGVjdHJvbmljcxtQcmluY2lwYWwgRW5naW5lZXIsIFNvZnR3YXJl?= X-Sender-Code: =?UTF-8?B?QzEwG0VIURtDMTBDRDA1Q0QwNTAwNTg=?= CMS-TYPE: 201P X-CMS-RootMailID: 20171016144130epcas1p2c1fa53d06d36c27f8ac8af3237b97721 X-RootMTR: 20171016144130epcas1p2c1fa53d06d36c27f8ac8af3237b97721 References: <7240.1507973844@thecus.kiddle.eu> <6529.1508164192@thecus.kiddle.eu> On Mon, 16 Oct 2017 16:29:52 +0200 Oliver Kiddle wrote: > Does anyone else have views on allowing a github model for completion > functions? Most of my arguments against github usage don't really apply > if we're only talking about completions for commands. It's already allowed --- anyone can set this up, and they already have. Anyone can use any set of shell functions they like. The next question is more about how it interacts with the source distribution. If it overrides it --- which is easy to set up, too --- there's no actual clash. The question then becomes more one of bundling and installation. If it completely replaces it, that's probably not a problem since developers can easily get the completions from elsewhere, and again it becomes a bundling problem for distribution. It's not clear to me how helpful that is in practice. If you have a stable branch in the original repository, it's going to have to be maintained as an update from the development branch for each completion separately --- which isn't much different from just copying it over to the source distribution, where the update also gets a bit more visibility from people not necessarily interested in a rapidly changing completion repository. > And is there a simple way to provide this without separating the repository? That seems to me the wrong way to go. There's no absolute need for completions to be in the same place as the source. Either keep them separate and updated and installed separately (but potentially bundled with a source release for convenience) or keep them (or an stabilised version, as above) with the source, with the restrictions that implies. pws