From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1057 invoked by alias); 28 Dec 2016 04:07:57 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 22298 Received: (qmail 6969 invoked from network); 28 Dec 2016 04:07:57 -0000 X-Qmail-Scanner-Diagnostics: from mail-qt0-f173.google.com 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(209.85.216.173):SA:0(-0.7/5.0):. Processed in 0.885023 secs); 28 Dec 2016 04:07:57 -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=-0.7 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_PASS,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: timothee.cour@gmail.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.216.173 as permitted sender) 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== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=ovFikg1YiyIm/QppOCiqaFlZrgIe9wuexuYgaSDKpHs=; b=CZQ6bCS9orBFCWhLbb+/yzV/f0JCtSFJ3MF6BUAUzKfIL0okLyyGGWWo91lHOfg4dW ErOudG0FLCL1sLlG0gCe7JVbJwkeAdZJYP1zQesSwVWJsdOneRaskVOkwyJmTvzW/fSO XBLNFxmmuG4MjJDpUUDi/XUFjuWrTJE0RkbbqVnHZtZrYK3czpXJ5fPkva5rFSRSHZ+5 NP+J2jp4FmehmUKqaKWGaGEjvgEr2sTGkmGEje738FYmeN90Dx7Cj326yBUQ8IrVAay2 xgI1GW+SWnxY0gjjLVeJqm4a5P+yvvNve4fAP5MZoP/UonW/QSkP1aNySdEGKWO7TSaa aoSQ== X-Gm-Message-State: AIkVDXK001qieXdoNfcVEc+ucDcQ4M2vzfIHflviwbdBtbuGtaRFvuk/RqIyjeHoCaxYVNTp6CPYbizLRH7qLA== X-Received: by 10.200.38.168 with SMTP id 37mr32063107qto.160.1482891669142; Tue, 27 Dec 2016 18:21:09 -0800 (PST) MIME-Version: 1.0 Sender: timothee.cour@gmail.com In-Reply-To: <161227105342.ZM1085@torch.brasslantern.com> References: <161227105342.ZM1085@torch.brasslantern.com> From: Timothee Cour Date: Tue, 27 Dec 2016 21:20:38 -0500 X-Google-Sender-Auth: PcoZYoJRIJw1Ey8Uzy5aNxZnmkw Message-ID: Subject: Re: regression: zsh completion stopped working after upgrading zsh 5.2=>5.3 To: Bart Schaefer , zsh-users@zsh.org Content-Type: multipart/alternative; boundary=001a114060762e07740544ae9f9e --001a114060762e07740544ae9f9e Content-Type: text/plain; charset=UTF-8 On Tue, Dec 27, 2016 at 1:53 PM, Bart Schaefer 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 --001a114060762e07740544ae9f9e--