zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Why zsh chose to be non-compliant in pattern matching
Date: Mon, 29 Feb 2016 10:27:41 +0000	[thread overview]
Message-ID: <20160229102741.6c1d5518@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <CALS7p_ccvXTx4STR+kgbsC_QhV1Rrd_uMxYEu5-xCFAHzx5A-w@mail.gmail.com>

On Mon, 29 Feb 2016 17:00:28 +0700
Cuong Manh Le <cuong.manhle.vn@gmail.com> wrote:
> The super user in U&L site post his opinion at
> http://unix.stackexchange.com/a/266394/38906
> 
> He said that the pattern matching spec is unspecified for quoted characters
> inside bracket expression. What is your opinion?

He's talking about the standard, which indeed doesn't say anything about
the subject.

[
    If an open bracket introduces a bracket expression as in XBD RE
    Bracket Expression, except that the <exclamation-mark> character (
    '!' ) shall replace the <circumflex> character ( '^' ) in its role
    in a non-matching list in the regular expression notation, it shall
    introduce a pattern bracket expression. A bracket expression
    starting with an unquoted <circumflex> character produces
    unspecified results. Otherwise, '[' shall match the character
    itself.

There's a reference there to regular expressions, for which only
backslash quoting is valid, as far as I'm aware.  Zsh has supported
that for quite a while.

I think it's more a question of current practice.  It's probably
widespread enough now to be standardisable.

pws


  reply	other threads:[~2016-02-29 10:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26  1:02 Cuong Manh Le
2016-02-26  8:43 ` Bart Schaefer
2016-02-29 10:00   ` Cuong Manh Le
2016-02-29 10:27     ` Peter Stephenson [this message]
2016-02-29 22:28       ` 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=20160229102741.6c1d5518@pwslap01u.europe.root.pri \
    --to=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).