From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-34564-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 4878 invoked by alias); 17 Feb 2015 12:57:34 -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: 34564
Received: (qmail 13411 invoked from network); 17 Feb 2015 12:57:31 -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=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI,
	SPF_HELO_PASS autolearn=ham version=3.3.2
X-AuditID: cbfec7f5-b7fc86d0000066b7-c6-54e33a21ff67
Date: Tue, 17 Feb 2015 12:57:16 +0000
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: PATCH:  Crash bug on garbage input (previously reported to Debian)
Message-id: <20150217125716.2f485dcf@pwslap01u.europe.root.pri>
In-reply-to: <150216113923.ZM5698@torch.brasslantern.com>
References: <150214102534.ZM4368@torch.brasslantern.com>
 <20150214214209.6d2f5e7e@ntlworld.com>
 <150215112622.ZM11584@torch.brasslantern.com>
 <20150216125749.7a26822c@pwslap01u.europe.root.pri>
 <20150216170413.054623af@pwslap01u.europe.root.pri>
 <150216113923.ZM5698@torch.brasslantern.com>
Organization: Samsung Cambridge Solution Centre
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu)
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Brightmail-Tracker:
 H4sIAAAAAAAAA+NgFlrKLMWRmVeSWpSXmKPExsVy+t/xK7qKVo9DDF5+0bU42PyQyYHRY9XB
	D0wBjFFcNimpOZllqUX6dglcGftWihc8YavofL6NvYFxA2sXIyeHhICJxLJ1d9ggbDGJC/fW
	A9lcHEICSxklfs5/ygzhLGGSWLr0LBOEs41R4sDZ14wgLSwCqhK3Pk9lAbHZBAwlpm6aDRYX
	ERCXOLv2PFhcWMBf4sfVbvYuRg4OXgF7ie4uB5Awp4ClxOdNs1khZq5hkvjxYAHYSfwC+hJX
	/35igjjJXmLmlTNgM3kFBCV+TL4HNpNZQEti87YmVghbXmLzmrfMILaQgLrEjbu72ScwCs1C
	0jILScssJC0LGJlXMYqmliYXFCel5xrpFSfmFpfmpesl5+duYoQE7dcdjEuPWR1iFOBgVOLh
	XbjgUYgQa2JZcWXuIUYJDmYlEV4fqcchQrwpiZVVqUX58UWlOanFhxiZODilGhgFG5Ve+Ldr
	LFpbxPL/9RsBh8wPuqFXm+d6qEVLLuh73LeC6+p6vdX5b1b1WVUryP87L/h/1bECz+KjFam3
	ZhnbfZCwP5Pg+7tn/7VlSyeo9iXzNAZ92rmSt6O1f272z36jHcJ+r5e8/H9Ue0Nrzq6HRmev
	zV7K6BG0b+fxYJkpmz8aXpWT8shRYinOSDTUYi4qTgQA5v7Q8DgCAAA=

On Mon, 16 Feb 2015 11:39:23 -0800
Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Feb 16,  5:04pm, Peter Stephenson wrote:
> }
> } I've add the "parse test from hell" where the first line looks like an
> } arithmetic substitution but it actually turns out to be a case statement
> } with unbalanced parentheses that needs the new parsing behaviour.
>
> There's an interesting bit of this which I don't think is actually a
> change in behavior but which might be worth noting.
>
> Interactive shell:
>
> torch% print $((case foo in
> mathsubst>
>
> If you send-break (ctrl+c) at this point, the input is entirely discarded
> and can't be recalled with up-line-or-history.

I'm not getting this now.  If I abort here, I can recall the line above,
though anything I type on that second line gets discarded (which I think
is standard).

pws