From: Eric Cook <llua@gmx.com>
To: zsh-workers@zsh.org
Subject: Re: GH:zsh-users/zsh-completions.
Date: Sat, 14 Oct 2017 12:49:48 -0400 [thread overview]
Message-ID: <f9fd90d6-e057-f99c-c860-9258cefa1e5d@gmx.com> (raw)
In-Reply-To: <CA+mcLN6ZuZ_AoKvfbceupZVg9+1btDg7NG=bGRUMDxwzLs5bcg@mail.gmail.com>
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.
next prev parent reply other threads:[~2017-10-14 17:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7240.1507973844@thecus.kiddle.eu>
2017-10-14 14:44 ` GH:zsh-users/zsh-completions Julien Nicoulaud
2017-10-14 16:49 ` Eric Cook [this message]
2017-10-16 14:29 ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-10-16 15:11 ` GH:zsh-users/zsh-completions Peter Stephenson
2017-10-16 15:24 ` GH:zsh-users/zsh-completions Bart Schaefer
2017-10-16 15:42 ` GH:zsh-users/zsh-completions Peter Stephenson
2017-10-16 17:49 ` GH:zsh-users/zsh-completions gi1242+zsh
2017-10-17 21:09 ` GH:zsh-users/zsh-completions Joey Pabalinas
2017-10-18 16:23 ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-10-19 1:09 ` GH:zsh-users/zsh-completions Bart Schaefer
2017-10-19 4:03 ` GH:zsh-users/zsh-completions Aaron Schrab
2017-10-19 5:24 ` GH:zsh-users/zsh-completions Bart Schaefer
2017-11-01 23:33 ` ChangeLogs (Re: GH:zsh-users/zsh-completions.) Oliver Kiddle
2017-11-01 23:46 ` Bart Schaefer
2017-11-02 20:09 ` Oliver Kiddle
2017-10-19 1:31 ` GH:zsh-users/zsh-completions Joey Pabalinas
2017-10-19 14:37 ` GH:zsh-users/zsh-completions Daniel Shahaf
2017-10-30 23:38 ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-11-01 16:35 ` GH:zsh-users/zsh-completions Daniel Shahaf
2017-11-01 22:58 ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-10-16 23:00 ` GH:zsh-users/zsh-completions Bart Schaefer
2017-10-16 20:04 ` GH:zsh-users/zsh-completions Daniel Shahaf
2017-10-17 7:53 ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-10-17 8:41 ` GH:zsh-users/zsh-completions Peter Stephenson
2017-10-16 15:26 ` GH:zsh-users/zsh-completions gi1242+zsh
2017-10-17 9:35 ` GH:zsh-users/zsh-completions Oliver Kiddle
2017-10-19 18:25 ` GH:zsh-users/zsh-completions Daniel Tameling
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=f9fd90d6-e057-f99c-c860-9258cefa1e5d@gmx.com \
--to=llua@gmx.com \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).