From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25607 invoked by alias); 8 Dec 2014 16:41:46 -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: 33935 Received: (qmail 9525 invoked from network); 8 Dec 2014 16:41:33 -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=399Rl8SIxmcm-etDinAA:9 a=CjuIK1q_8ugA:10 From: Bart Schaefer Message-id: <141208084138.ZM25388@torch.brasslantern.com> Date: Mon, 08 Dec 2014 08:41:38 -0800 In-reply-to: <20141208130334.4ea54996@pwslap01u.europe.root.pri> Comments: In reply to Peter Stephenson "Re: Interrupting globs (Re: Something rotten in tar completion)" (Dec 8, 1:03pm) 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> <141206211828.ZM15934@torch.brasslantern.com> <20141207170713.1a71fe0d@pws-pc.ntlworld.com> <20141207171920.0913aae9@pws-pc.ntlworld.com> <20141208111806.5cd1ced5@pwslap01u.europe.root.pri> <20141208130334.4ea54996@pwslap01u.europe.root.pri> 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 8, 1:03pm, Peter Stephenson wrote: } } I think we should clear it before and after precmd to be safe. } } It's not really clear to me why this worked before; one of the various } other errflag-clearings must have come in before we reached the } top-level loop. I'm not sure if that was intentional or accidental, but } presumably somewhere high up in loop() with toplevel == 1 is right. I } can't work out if it should be even higher, before the history mechanism } starts. I suspect it should be cleared before the history starts but as long as it is cleared before anything is actually *read* the chances for it to go wrong are probably very small.