From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10311 invoked by alias); 7 Dec 2014 05:04:21 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 33898 Received: (qmail 9797 invoked from network); 7 Dec 2014 05:04:08 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 X-CMAE-Score: 0 X-CMAE-Analysis: v=2.1 cv=AKpDk7pY c=1 sm=1 tr=0 a=FT8er97JFeGWzr5TCOCO5w==:117 a=kj9zAlcOel0A:10 a=q2GGsy2AAAAA:8 a=oR5dmqMzAAAA:8 a=-9mUelKeXuEA:10 a=A92cGCtB03wA:10 a=J_GDWTzTb2u5tEbpK7gA:9 a=CjuIK1q_8ugA:10 From: Bart Schaefer Message-id: <141206210413.ZM15558@torch.brasslantern.com> Date: Sat, 06 Dec 2014 21:04:13 -0800 In-reply-to: <141206204503.ZM15491@torch.brasslantern.com> Comments: In reply to Bart Schaefer "Re: Interrupting globs (Re: Something rotten in tar completion)" (Dec 6, 8:45pm) References: <20141202155452.647182b4@pwslap01u.europe.root.pri> <141202084858.ZM31517@torch.brasslantern.com> <20141202172654.30e7d380@pwslap01u.europe.root.pri> <141204085606.ZM9146@torch.brasslantern.com> <20141204171226.301e9d2c@pwslap01u.europe.root.pri> <141205002023.ZM19736@torch.brasslantern.com> <20141205145054.655a2f70@pwslap01u.europe.root.pri> <141205100632.ZM508@torch.brasslantern.com> <20141205181330.2b458b46@pwslap01u.europe.root.pri> <20141205203417.2bc66b7b@pws-pc.ntlworld.com> <20141205220717.2f86bdd2@pws-pc.ntlworld.com> <141206094849.ZM1787@torch.brasslantern.com> <141206204503.ZM15491@torch.brasslantern.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: "Zsh Hackers' List" Subject: Re: Interrupting globs (Re: Something rotten in tar completion) MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Dec 6, 8:45pm, Bart Schaefer wrote: } } } - /* Commenting this out makes ^C-ing a job started by a function } } - stop the whole function again. But I guess it will stop } } - something else from working properly, we have to find out } } - what this might be. --oberon } } - } } - errflag = 0; */ } } + errflag &= ~ERRFLAG_ERROR; } } } } And commenting that line back out fixes my chpwd() hook ctrl-c thing. } } (or changing it to errflag &= ~ERRFLAG_INT; but I have no idea if that } } makes any sense). } } Both things fit with Oberon's comment, actually. Based on the comment, } what we do NOT want to do there is clear ERRFLAG_INT. Wait ... I think I have something backward there. errflag &= ~ERRFLAG_ERROR should leave ERRFLAG_INT unaffected, which is what seems to be wanted. So if ~ERRFLAG_INT (or no change at all) works, then the important value of errflag there *is* ERRFLAG_ERR. Which means something changed errflag from ERRFLAG_INT to ERRFLAG_ERR ? But that doesn't make sense, looking at the patch. OK, now I'm just confused. Sorry.