From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5793 invoked by alias); 14 Oct 2017 17:02:53 -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: 41895 Received: (qmail 24205 invoked by uid 1010); 14 Oct 2017 17:02:53 -0000 X-Qmail-Scanner-Diagnostics: from mout.gmx.net 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(212.227.17.21):SA:0(-2.6/5.0):. Processed in 2.70657 secs); 14 Oct 2017 17:02:53 -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=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM, RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: llua@gmx.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Subject: Re: GH:zsh-users/zsh-completions. To: zsh-workers@zsh.org References: <7240.1507973844@thecus.kiddle.eu> From: Eric Cook Message-ID: Date: Sat, 14 Oct 2017 12:49:48 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:RvHTNtkjU3Jxa+keahDhILwqOwD+GwnqGTCj1B+0sXutBBffn24 UDWCBDZYWWx85KoQySDHKwsMFIssKu4EWcjZmR3fcc7LIpCj9rZbl8FCbF0Vxx+gD7vUWxU yV+9DMV1aVXcFPADZnqU4i45E1Eyi0EXheEDcOCm0zVEJ+WKxN78UN4Lkt/EThMHQqh453w j0VqD3v6D3Kdo4Q+FfslA== X-UI-Out-Filterresults: notjunk:1;V01:K0:dWjuI0FXFvg=:v+a3c8Wh64DP/cks+EmRTI Bv3onOa0hk4TKfw0uOPXjHzg5ShTBbS6kPxegFSTPZ6dmFO2lfRghKrTb3okdnrbHXEE1RgUf hXQxSyVNujed9o/ipq5OU1MgYr1SziBrNcQy094NFHO9K2d1Lbd4Zt35+s/m0Tf10w0BarZD/ MfaEd6C3QN9EYFRmAX/LqHTBF+OzY9gEnJuIlcw+KG1ZqlEr1I8Z/K2pBWD5w6ZdBCHRUrB6j +DbxD0SDA/ZpRJtSi9QIOXlPMsDY3V3HfmQStw6fG3U3J1jiC5dTG/kdhNOOVV2rsBXRbKhQe 68DLPGKoce7dogmSUAPz2txMMIhqhPpAefHYRoqNU/SevEDcNaYDygw/3IbPjExLT1+/roJkt fyfglsONnYe7vcrDiZ78k/ZKsv9sVi7f3eQslnBm0HL5lndJBfASlEK6A60lkQyKu1cQAKFdZ c4LRMkmJrkYlTjkjsd/HAdHCYKevK6Jy8ONbM+nbpZ+ZrZxNNyjcbNpIqOOHrbmQeaIq4PR/L uSTmvXUBHSy8x3uDBCaRpPkoOvYKJrUhhnfVs1A0arYEqE1whGqJrtyWeRM7xQku4vBuUnlKI ETGW/BqmLSHu/S7PYgo/DR1hqyZ8QUpF18flvEZzUwF7nClSrKtjqShia1TyoF9WMuchStHeK hig74scf/mxFS6hcJ8EoJuQ2aH0Jh8m3XIfdLeCkCwTWCtga8RSMhYBYZnmOU3DBnQbfgvwNF gggosV5JJ9PweUof+o0hbGKg8GVfcHScsuRPN4KeIr9qa/EzzfhODnGJUwFucLQuWyCY8NjsH zvBejnOWmRliyztVmoHGkNSsgv6SG55+NMOwgATdVH3vE46dnU= On 10/14/2017 10:44 AM, Julien Nicoulaud wrote: > - I believe the release rythm of zsh (~once a year) is a bit too slow > for completions. We do ~monthly releases, and I think most users importing > it via a "plugin manager" actually directly use the master branch, which is > fine IMHO for completions. By the time a compdef lands in a zsh release, it > can be already obsolete or need bugfixes. I think this is the biggest point > for having compdefs in a separate repo than the shell itself. The release frequency cuts both ways, if the command in question changes frequently, with the completer keeping in sync and an user continues to use an older version of the command. they would be presented options that doesn't exist yet. That would be my biggest point for trying to push those completers into their project's source tree. While it would awesome if the developers attempt to keep it up to date there isn't an reason why the original contributor of the completer couldn't help with that effort too. But once an release of project foo happens and appears on your os, you have an snapshot of the options supported by that release. bug fixes to the completer would work like any other bug fix to packages on an os.