Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Parse error (lack thereof) on incomplete loops
- X-seq: zsh-workers 43604
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
- Subject: Re: Parse error (lack thereof) on incomplete loops
- Date: Thu, 4 Oct 2018 13:34:53 -0700
- Cc: "zsh-workers@xxxxxxx" <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=TJan9fhpiu0En0XHRxCS2vZ7DEWxlFGtc5JUwwH0eGU=; b=S+F6TZuKAic1regmyI5UIqcxJrhHn6ORv8BlXkaeDUZsOafQyoziHfMX7+XqhhIIvd oHys3HtLY/mgTOspeRASOH4Ffgb9F1mzvXwlzC4xcQPXL9/oskFic2JgkyyMkecBftrK R+wPv+6i83M24+ohr0VURRnS6/NhtS5yLSwip7PiYCxUzpdo2dSgPxnKcohQPfImI485 XIDKAxZnPlm4rdl7eV98/Q1d0d8zAkHjgGZefg4mNWZUQecU+mIbOrMqdL9wqNeDef2c WNe3tDoxOqDHVLJyWDYDeq2NhzC1lix/eohtfJrRwBFnUxbrK2Y2debk6D5aSpj2Oklz l1Zg==
- In-reply-to: <20181004163158eucas1p234a045be013b5463d8db44314ed217dc~adN28lJmq0822408224eucas1p2F@eucas1p2.samsung.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- List-unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CGME20181004154947epcas4p2441e109a2c4e060bf39f0f6925e98241@epcas4p2.samsung.com> <CAH+w=7awbwDuX2RXcB7pK6Hhbi8fjs=NvwkTAEGmY7gvNpLCqA@mail.gmail.com> <20181004163158eucas1p234a045be013b5463d8db44314ed217dc~adN28lJmq0822408224eucas1p2F@eucas1p2.samsung.com>
On Thu, Oct 4, 2018 at 9:32 AM Peter Stephenson
<p.stephenson@xxxxxxxxxxx> wrote:
>
> On Thu, 2018-10-04 at 08:49 -0700, Bart Schaefer wrote:
>
> > % { while false
> > cursh while> }
> > %
> >
> > This indicates a parsing problem in 5.6
>
> It affects for, repeat, until and if, too, and isn't hard to turn back
> into a parse error.
How did it stop being a parse error in the first place?
> However, I'm very far from convinced this is actually a bug. If you
> turn off SHORT_LOOPS you'll find you get the error back
My problem with it is that it's not consistent.
set -x
{ while false
while false
}
The shell is now in an infinite loop executing "false". Can this
really be intentional?
Messages sorted by:
Reverse Date,
Date,
Thread,
Author