From: Martijn Dekker <martijn@inlv.org>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: spurious 'case' parse error
Date: Fri, 22 Sep 2017 15:11:26 +0100 [thread overview]
Message-ID: <6fb7e839-48ce-51a4-1d64-bbbf498c5bfb@inlv.org> (raw)
The following causes a spurious parse error in zsh:
case x in
(x)echo ok ;;
esac
Output:
test.zsh:2: parse error near `ok'
The cause is the lack of space after the ')'; that space should be
optional, but is mandatory in zsh.
Interestingly, this works:
case x in
x)echo ok ;;
esac
Confirmed in zsh 5.0.7 through current git. (I didn't test earlier
versions.)
- Martijn
next reply other threads:[~2017-09-22 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 14:11 Martijn Dekker [this message]
2017-09-22 15:42 ` Bart Schaefer
2017-09-22 16:59 ` Martijn Dekker
2017-09-23 17:16 ` 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=6fb7e839-48ce-51a4-1d64-bbbf498c5bfb@inlv.org \
--to=martijn@inlv.org \
--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).