From: Bart Schaefer <schaefer@brasslantern.com>
To: Arseny Maslennikov <ar@cs.msu.ru>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: 'while do done' hangs interactive zsh
Date: Sun, 16 May 2021 11:02:04 -0700 [thread overview]
Message-ID: <CAH+w=7YQqiev2TrWLg-5jGh+Kac2KVe-xQ6JLpJFmaPHr8wsMw@mail.gmail.com> (raw)
In-Reply-To: <20210516164328.x7jnh3gfqfiidd7a@chazelas.org>
On Sun, May 16, 2021 at 9:43 AM Stephane Chazelas <stephane@chazelas.org> wrote:
>
> while LIST do LIST done
>
> LIST is not explicitely specified, but it does appear to be a
> list of 0 or more pipelines. Or in other words any script.
>
[...]
>
> ... other shells require at least one pipeline
> in the condition LIST (which to me just looks like an
> arbitrary, unecessary limitation), but that does not mean shell
> implementations have to return an error here.
Bash requires at least one pipeline in the do-LIST as well.
Is this worth making into an emulation-mode thing, i.e., adding a
couple of more conditions to my while-do-done patch?
The documentation for CSH_JUNKIE_LOOPS could do with some updating as well.
next prev parent reply other threads:[~2021-05-16 18:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 9:16 Arseny Maslennikov
2021-05-16 14:28 ` Bart Schaefer
2021-05-16 15:46 ` Bart Schaefer
2021-05-16 16:15 ` Mikael Magnusson
2021-05-16 16:22 ` Lawrence Velázquez
2021-05-16 17:47 ` Bart Schaefer
2021-05-16 18:23 ` Martijn Dekker
2021-05-16 19:59 ` Bart Schaefer
2021-05-16 20:34 ` Peter Stephenson
2021-05-16 21:19 ` [PATCH] volatile declarations (was Re: 'while do done' hangs interactive zsh) Bart Schaefer
2021-05-16 23:40 ` Martijn Dekker
2021-05-16 16:43 ` 'while do done' hangs interactive zsh Stephane Chazelas
2021-05-16 18:02 ` Bart Schaefer [this message]
2021-05-16 18:25 ` Martijn Dekker
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=7YQqiev2TrWLg-5jGh+Kac2KVe-xQ6JLpJFmaPHr8wsMw@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=ar@cs.msu.ru \
--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).