From: Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: bracket expressions and POSIX
Date: Sat, 30 Jun 2001 20:00:34 +0100 [thread overview]
Message-ID: <20010630190039.59EB714286@pwstephenson.fsnet.co.uk> (raw)
In-Reply-To: "Clint Adams"'s message of "Fri, 29 Jun 2001 14:22:15 EDT." <20010629142215.A8431@dman.com>
Clint Adams wrote:
> POSIX says that \ loses its special meaning within a bracket
> expression for pattern matching and also that ! is the
> ^ character in that context.
>
> So this strikes me as non-compliant:
>
> % emulate sh
> % touch \\test abc
> % echo [!a]*
> zsh: event not found: a]
We can't do much directly about this (i.e. with BANG_HISTORY), as Bart
pointed out.
> % echo [\!a]*
> \test
Ooh err. I don't like that one at all.
> % echo [\]*
> []*
> % echo [\\]*
> \test
These are non-compliant, but it's actually useful being able to quote
things in a range with a backslash, particularly square brackets, rather
than rely on the rather tricky rules of positioning (anyone remember off
the top of their head how to match both a `]' and a `-'?). I hope
it will be possible to turn this into an option (part of SH_GLOB?) by
un-nulling the backslashes. It's possible the extra test could make a
noticeable effect on the speed of pattern compilation, but again I hope
not. I haven't looked at the code.
--
Peter Stephenson <pws@pwstephenson.fsnet.co.uk>
Work: pws@csr.com
Web: http://www.pwstephenson.fsnet.co.uk
next prev parent reply other threads:[~2001-06-30 17:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-29 18:22 Clint Adams
2001-06-30 2:14 ` Bart Schaefer
2001-06-30 19:00 ` Peter Stephenson [this message]
2001-06-30 18:25 ` Bart Schaefer
2001-07-02 6:13 ` Andrej Borsenkow
2001-07-02 7:10 ` Bart Schaefer
2001-07-02 7:33 ` Andrej Borsenkow
2001-07-02 7:44 ` Andrej Borsenkow
2001-07-02 13:41 ` Clint Adams
2001-07-02 14:47 ` Andrej Borsenkow
2001-07-02 14:57 ` Clint Adams
2001-07-02 13:31 ` Clint Adams
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=20010630190039.59EB714286@pwstephenson.fsnet.co.uk \
--to=pws@pwstephenson.fsnet.co.uk \
--cc=zsh-workers@sunsite.auc.dk \
/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).