From: Peter Stephenson <pws@csr.com>
To: zsh-workers <zsh-workers@sunsite.dk>
Subject: Re: setopt globcomplete and () broken
Date: Tue, 10 Mar 2009 17:34:24 +0000 [thread overview]
Message-ID: <20090310173424.1af302c5@news01> (raw)
In-Reply-To: <20090310135146.30c0c794@news01>
On Tue, 10 Mar 2009 13:51:46 +0000
Peter Stephenson <pws@csr.com> wrote:
> elif [[ "$tmp1" = (#b)(*[^\$])(\(\([^\|~]##\)\)) ]]; then
> tmp2=( "$tmp2[@]" "${match[1]}((${tmp3}${match[2][3,-1]}" )
I thought I was on the way to understanding what was going on here, but
this attempt to match some form of glob qualifiers has stumped me. Why are
we specially matching a pattern ending with glob qualifiers wrapped in
double parentheses? What we're matching against, $tmp1, comes from patterns
supplied to _files or _path_files as an argument; I can't see any sign the
double parentheses are used, and the expansion manual says
A glob subexpression that would normally be taken as glob qualifiers, for
example (^x), can be forced to be treated as part of the glob pattern by
doubling the parentheses, in this case producing ((^x)).
Yet we are treating it as if it's a glob expression ($tmp3 is the
new glob qualifier we are trying to insinuate into the list).
Can I simply hold my breath until it goes away?
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
next prev parent reply other threads:[~2009-03-10 17:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 13:25 Mikael Magnusson
2009-03-10 13:51 ` Peter Stephenson
2009-03-10 17:34 ` Peter Stephenson [this message]
2009-03-10 18:04 ` Mikael Magnusson
2009-03-10 18:18 ` Peter Stephenson
2009-03-10 18:30 ` Mikael Magnusson
2009-03-11 4:22 ` Bart Schaefer
2009-03-13 9:56 ` Peter Stephenson
2009-03-13 15:08 ` Bart Schaefer
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=20090310173424.1af302c5@news01 \
--to=pws@csr.com \
--cc=zsh-workers@sunsite.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).