From: Chet Ramey <chet.ramey@case.edu>
To: Peter Stephenson <p.stephenson@samsung.com>,
Martijn Dekker <martijn@inlv.org>,
zsh-workers@zsh.org
Cc: chet.ramey@case.edu
Subject: Re: 'case' pattern matching bug with bracket expressions
Date: Thu, 14 May 2015 19:51:29 -0400 [thread overview]
Message-ID: <55553501.3050904@case.edu> (raw)
In-Reply-To: <20150514165557.59f6bdc9@pwslap01u.europe.root.pri>
On 5/14/15 11:55 AM, Peter Stephenson wrote:
> It occurs to me that other shells will treat whitespace as ending a
> pattern for syntactic reasons, even if logically it can't:
>
> [[ ' ' = [ ] ]]
>
> works in zsh, but is a parse error in bash.
Because shell metacharacters delimit words. The definition of a WORD
(and the use of WORDs as patterns) doesn't really change depending on
whether you're parsing a case command or a conditional command.
> (*) Relegated to a footnote because this is more of a rant than
> a useful comment: furthermore, the whole []] thing is designed
> so that you *don't* need to quote characters in the [...]. So
> do you, or don't you? Bleugh.
You do. Conditional commands use the same definition of WORD tokens
as everything else.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/
next prev parent reply other threads:[~2015-05-14 23:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 13:14 Martijn Dekker
2015-05-14 13:50 ` [BUG] " Martijn Dekker
2015-05-14 14:42 ` Peter Stephenson
2015-05-14 15:47 ` Martijn Dekker
2015-05-14 15:55 ` Peter Stephenson
2015-05-14 17:30 ` Bart Schaefer
2015-05-15 0:05 ` Chet Ramey
2015-05-14 23:51 ` Chet Ramey [this message]
2015-05-15 8:38 ` Peter Stephenson
2015-05-15 20:48 ` Peter Stephenson
2015-05-15 21:48 ` Bart Schaefer
2015-05-14 16:17 ` Peter Stephenson
2015-05-14 17:07 ` Martijn Dekker
2015-05-14 17:43 ` Peter Stephenson
2015-05-15 0:09 ` Chet Ramey
2015-05-14 23:59 ` Chet Ramey
2015-05-14 21:23 ` Chet Ramey
2015-05-14 23:45 ` Chet Ramey
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=55553501.3050904@case.edu \
--to=chet.ramey@case.edu \
--cc=martijn@inlv.org \
--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).