From: Peter Stephenson <pws@csr.com>
To: Zsh <zsh-workers@sunsite.dk>
Subject: Re: Just to make sure I'm understanding it...
Date: Thu, 07 Aug 2003 10:56:01 +0100 [thread overview]
Message-ID: <3927.1060250161@csr.com> (raw)
In-Reply-To: "DervishD"'s message of "Wed, 06 Aug 2003 21:35:57 +0200." <20030806193557.GA463@DervishD>
DervishD wrote:
> Well, in function 'insert-files' there is a line, just at the
> beginning, that reads 'files=( *(N) )', and I want to make sure I
> understand it. Since it starts with a parenthesis, it is (AFAIK) a
> candidate for filename generation. The asterisk seems to be the
> pattern an the 'N' in the parentheses is a glob qualifier (namely the
> 'set NULL_GLOB for this pattern' qualifier). What I don't understand
> is, why the spaces around the pattern and the qualifier?
They're optional, they're just there for readability.
files=(*(N))
will work but looks like the logo of a secret society. What you're
probably missing is the the outer parentheses are there to turn the
assignment into an array assignment, they're nothing to do with
globbing. In this case the place where you can't have spaces is around
the `='.
files=(
*(N)
)
works, too. It's one of the advantages of arrays --- you can make the
assignments much neater.
However,
files=*(N)
*doesn't* work. The right hand side of normal assignment doesn't do
globbing (unless you have the option GLOB_ASSIGN set, which we don't
recommend). This was changed a while ago: the problem was that if there
were multiple matches, an array assignment was done, while if there was
just one, because of the use of scalar syntax a scalar assignment was
done. The new arrangement (with GLOB_ASSIGN unset) is much neater.
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK Tel: +44 (0)1223 692070
**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential
and/or privileged material.
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by
persons or entities other than the intended recipient is
prohibited.
If you received this in error, please contact the sender and
delete the material from any computer.
**********************************************************************
next prev parent reply other threads:[~2003-08-07 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 19:35 DervishD
2003-08-07 9:56 ` Peter Stephenson [this message]
2003-08-07 10:33 ` DervishD
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=3927.1060250161@csr.com \
--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).