Zsh Mailing List Archive
Messages sorted by:
Re: regression: zsh completion stopped working after upgrading zsh 5.2=>5.3
- X-seq: zsh-users 22298
- From: Timothee Cour <timothee.cour2@xxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>, zsh-users@xxxxxxx
- Subject: Re: regression: zsh completion stopped working after upgrading zsh 5.2=>5.3
- Date: Tue, 27 Dec 2016 21:20:38 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=ovFikg1YiyIm/QppOCiqaFlZrgIe9wuexuYgaSDKpHs=; b=cK7Eks02pd5++IEKXCyYNcXHs2bmy9WIgKZixNC7ogX+zLlc1Snepk2/K9Q5zoIaIk L/voZCgYIcwWVSGhjH0qS1Y9SV2UKg6b1CQ5DH1RZ3YWh4xfIVBNp86mSHjA/UPlF9r2 AZIh3FcRqaDg/o51HaVV54mdqO9ZgCbh0rSRLQ3spjLiyMrv/vNdXyMWGoG3Cm8jrTLv kjh1L90XVi6Yv/aH+a+qL9dEdSisVvp6oaUAogwedgtGnM3OHlbDUeNaDB21jE+T2L+R /xMsu8SwSyllJUBdtPiKl6rlMpAh1LIraTyF8/0oe4tq++pf3XDH7dihCDFu998jZXmt n5vA==
- In-reply-to: <161227105342.ZM1085@torch.brasslantern.com>
- List-help: <mailto:firstname.lastname@example.org>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:email@example.com>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
- References: <CAM4j=kOb-W_Oj5K5MoMS78Wn4pN=C2kbcPwzXaKv+cZcpwBR=A@mail.gmail.com> <161227105342.ZM1085@torch.brasslantern.com>
- Sender: timothee.cour@xxxxxxxxx
On Tue, Dec 27, 2016 at 1:53 PM, Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
> 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
> 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
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
* it would lower the barrier of entry to enter bugs, ie get bugs fixed
* 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
Messages sorted by: