From: Marlon Richert <marlon.richert@gmail.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Inconsistent parse error output
Date: Wed, 8 Feb 2023 09:57:55 +0200 [thread overview]
Message-ID: <CAHLkEDtog5HMeU-rVA-pB5895h-PCs_0mbtvKG+vfSoaVbpmJg@mail.gmail.com> (raw)
% done; foo
zsh: parse error near `done'
% :; done; foo
zsh: parse error near `done'
% if; done; foo
zsh: parse error near `done'
% if; then done; foo
zsh: parse error near `foo'
%
I would've expected that last one to produce the same error output as
the previous ones.
This can lead to confusing output when the parse error occurs in a file:
% > tst << EOF
if :; then
:
done
# lots
# of
# comments
foo
EOF
% source tst
tst:9: parse error near `foo'
%
reply other threads:[~2023-02-08 7:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAHLkEDtog5HMeU-rVA-pB5895h-PCs_0mbtvKG+vfSoaVbpmJg@mail.gmail.com \
--to=marlon.richert@gmail.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).