From: Bart Schaefer <schaefer@brasslantern.com>
To: Peter Stephenson <p.stephenson@samsung.com>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Parse error (lack thereof) on incomplete loops
Date: Thu, 4 Oct 2018 13:34:53 -0700 [thread overview]
Message-ID: <CAH+w=7ZLJ5iiph8jpsSiLKdhkozqH+o_kJk7=zfK3DLBegft8g@mail.gmail.com> (raw)
In-Reply-To: <20181004163158eucas1p234a045be013b5463d8db44314ed217dc~adN28lJmq0822408224eucas1p2F@eucas1p2.samsung.com>
On Thu, Oct 4, 2018 at 9:32 AM Peter Stephenson
<p.stephenson@samsung.com> 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?
next prev parent reply other threads:[~2018-10-04 20:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20181004154947epcas4p2441e109a2c4e060bf39f0f6925e98241@epcas4p2.samsung.com>
2018-10-04 15:49 ` Bart Schaefer
2018-10-04 16:31 ` Peter Stephenson
2018-10-04 20:04 ` Marc Chantreux
2018-10-04 20:37 ` Bart Schaefer
2018-10-05 6:04 ` Marc Chantreux
2018-10-04 20:34 ` Bart Schaefer [this message]
2018-10-05 9:14 ` Peter Stephenson
2018-10-05 13:26 ` Daniel Shahaf
2018-10-05 13:47 ` Peter Stephenson
2018-10-05 17:04 ` Daniel Shahaf
2018-10-06 1:47 ` Bart Schaefer
2018-10-06 11:15 ` Peter Stephenson
2018-10-06 11:55 ` Peter Stephenson
2018-10-06 18:21 ` Peter Stephenson
2018-10-07 3:51 ` Bart Schaefer
2018-10-07 18:16 ` Bart Schaefer
2018-10-08 10:07 ` Peter Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH+w=7ZLJ5iiph8jpsSiLKdhkozqH+o_kJk7=zfK3DLBegft8g@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=p.stephenson@samsung.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).