From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-33917-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 17196 invoked by alias); 7 Dec 2014 20:03:09 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 33917
Received: (qmail 23608 invoked from network); 7 Dec 2014 20:03:07 -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-Originating-IP: [86.6.25.230]
X-Spam: 0
X-Authority: v=2.1 cv=S8BXwecP c=1 sm=1 tr=0 a=c0CwWhpM9oUd/BnC3z6Gzg==:117
 a=c0CwWhpM9oUd/BnC3z6Gzg==:17 a=NLZqzBF-AAAA:8 a=kj9zAlcOel0A:10
 a=q2GGsy2AAAAA:8 a=6eOJrZsStTyLZaSF7oAA:9 a=CjuIK1q_8ugA:10
Date: Sun, 7 Dec 2014 20:03:01 +0000
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: Interrupting globs (Re: Something rotten in tar completion)
Message-ID: <20141207200301.45421caf@pws-pc.ntlworld.com>
In-Reply-To: <141206211828.ZM15934@torch.brasslantern.com>
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>
X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.7; x86_64-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Sat, 06 Dec 2014 21:18:28 -0800
Bart Schaefer <schaefer@brasslantern.com> wrote:
> } Correspondingly, most of the time only the ERRFLAG_ERROR bit gets
> } reset.  ERRFLAG_INT gets reset [...]
> } 
> } - at the start of zleread, so we can read the next thing to do whatever
> } just happened.  I'm not sure this is particularly useful
> 
> But the situation before this patch is the same, is it not?

Didn't reply to this bit in my attempted summary.

Yes, as I've only reduced the places where it gets reset it shouldn't
cause any new problems.  Theoretically...

pws