From: Timothee Cour <timothee.cour2@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>, zsh-users@zsh.org
Subject: Re: regression: zsh completion stopped working after upgrading zsh 5.2=>5.3
Date: Tue, 27 Dec 2016 21:20:38 -0500 [thread overview]
Message-ID: <CANri+EyJXxR81pK0unLt9ywUbSFpbSD24ffb1_xrtmU8vVQ6_w@mail.gmail.com> (raw)
In-Reply-To: <161227105342.ZM1085@torch.brasslantern.com>
[-- Attachment #1: Type: text/plain, Size: 2096 bytes --]
On Tue, Dec 27, 2016 at 1:53 PM, Bart Schaefer <schaefer@brasslantern.com>
wrote:
> On Dec 27, 1:10pm, Timothee Cour wrote:
> }
> } See https://github.com/zsh-users/zsh-completions/issues/480 for details
>
> Thanks for the report.
>
> Essentially, it was a bug that having ERR_RETURN set *ever* worked.
> There are a whole lot of commands in the completion system, mostly
> "zstyle" where the success or failure isn't consequential, that are
> run in contexts where they might return nonzero and trigger ERR_EXIT.
>
> The bug, fixed October 15 of 2016, was that ERR_RETURN was ignored in
> some cases where ERR_EXIT was not.
>
> You can fix this easily in your .zshrc by adding
>
> _comp_options+=(NO_err_return)
>
> after you run compinit.
>
Thanks, this workaround worked! It solves my issues.
Having ERR_RETURN set is helpful to catch bugs.
> where the success or failure isn't consequential
Isn't that a bug in those commands though?
>
> (Also, just to reply to your comment about going back to the 80s: No,
> we don't require you to sign up for the mailing list in order to send
> us bug reports here. But I would have to sign up for github to reply
> to your comment there, so ...)
>
> (Volunteers willing to spend time watching and updating a bug tracker
> are welcome to apply for the position.)
>
OK, I thought signup was required in order to post, as is the case in some
mailing lists.
Not intending to start a sterile flame war here, just my opinion:
* github/gitlab are widely used so no particular signup would be needed
* using github.gitlab, ppl can click on Watch to follow/unfollow individual
issues or all of zsh issues to choose how much email from github they
receive
* it would lower the barrier of entry to enter bugs, ie get bugs fixed
faster
* all benefits of bug tracker as opposed to mailling list [tracking bugs,
cross references, search etc]
* avoids revealing your email address
* this has been adoped by https://github.com/zsh-users [Zsh community
projects (not directly affiliated with the zsh project)] probably for a
combination of the above reasons
next prev parent reply other threads:[~2016-12-28 4:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-27 18:10 Timothee Cour
2016-12-27 18:53 ` Bart Schaefer
2016-12-28 2:20 ` Timothee Cour [this message]
[not found] ` <CANri+EyJXxR81pK0unLt9ywUbSFpbSD24ffb1_xrtmU8vVQ6_w__49789.5799264826$1482898175$gmane$org@mail.gmail.com>
2016-12-28 4:37 ` Daniel Shahaf
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=CANri+EyJXxR81pK0unLt9ywUbSFpbSD24ffb1_xrtmU8vVQ6_w@mail.gmail.com \
--to=timothee.cour2@gmail.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@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).