* regression: zsh completion stopped working after upgrading zsh 5.2=>5.3 @ 2016-12-27 18:10 Timothee Cour 2016-12-27 18:53 ` Bart Schaefer 0 siblings, 1 reply; 4+ messages in thread From: Timothee Cour @ 2016-12-27 18:10 UTC (permalink / raw) To: zsh-users [-- Attachment #1: Type: text/plain, Size: 72 bytes --] See https://github.com/zsh-users/zsh-completions/issues/480 for details ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: regression: zsh completion stopped working after upgrading zsh 5.2=>5.3 2016-12-27 18:10 regression: zsh completion stopped working after upgrading zsh 5.2=>5.3 Timothee Cour @ 2016-12-27 18:53 ` Bart Schaefer 2016-12-28 2:20 ` Timothee Cour [not found] ` <CANri+EyJXxR81pK0unLt9ywUbSFpbSD24ffb1_xrtmU8vVQ6_w__49789.5799264826$1482898175$gmane$org@mail.gmail.com> 0 siblings, 2 replies; 4+ messages in thread From: Bart Schaefer @ 2016-12-27 18:53 UTC (permalink / raw) To: Timothee Cour, zsh-users 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. (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.) ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: regression: zsh completion stopped working after upgrading zsh 5.2=>5.3 2016-12-27 18:53 ` Bart Schaefer @ 2016-12-28 2:20 ` Timothee Cour [not found] ` <CANri+EyJXxR81pK0unLt9ywUbSFpbSD24ffb1_xrtmU8vVQ6_w__49789.5799264826$1482898175$gmane$org@mail.gmail.com> 1 sibling, 0 replies; 4+ messages in thread From: Timothee Cour @ 2016-12-28 2:20 UTC (permalink / raw) To: Bart Schaefer, zsh-users [-- 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
[parent not found: <CANri+EyJXxR81pK0unLt9ywUbSFpbSD24ffb1_xrtmU8vVQ6_w__49789.5799264826$1482898175$gmane$org@mail.gmail.com>]
* Re: regression: zsh completion stopped working after upgrading zsh 5.2=>5.3 [not found] ` <CANri+EyJXxR81pK0unLt9ywUbSFpbSD24ffb1_xrtmU8vVQ6_w__49789.5799264826$1482898175$gmane$org@mail.gmail.com> @ 2016-12-28 4:37 ` Daniel Shahaf 0 siblings, 0 replies; 4+ messages in thread From: Daniel Shahaf @ 2016-12-28 4:37 UTC (permalink / raw) To: Timothee Cour; +Cc: zsh-users Timothee Cour wrote on Tue, Dec 27, 2016 at 21:20:38 -0500: > Not intending to start a sterile flame war here, just my opinion: If you want the zsh project to start using a bug tracker, it'd be a lot more productive to ask the developers what their requirements are than to start advocating github/gitlab. For one, I assume we won't consider a bug tracker that doesn't have bidirectional email integration with this mailing list. (to minimise workflow disruption) Cheers, Daniel > * 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-12-28 4:40 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2016-12-27 18:10 regression: zsh completion stopped working after upgrading zsh 5.2=>5.3 Timothee Cour 2016-12-27 18:53 ` Bart Schaefer 2016-12-28 2:20 ` Timothee Cour [not found] ` <CANri+EyJXxR81pK0unLt9ywUbSFpbSD24ffb1_xrtmU8vVQ6_w__49789.5799264826$1482898175$gmane$org@mail.gmail.com> 2016-12-28 4:37 ` Daniel Shahaf
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).