From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-7507-mason-zsh=primenet.com.au@sunsite.dk>
Received: (qmail 19540 invoked from network); 10 Jun 2004 15:44:38 -0000
Received: from thor.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.86)
  by ns1.primenet.com.au with SMTP; 10 Jun 2004 15:44:38 -0000
Received: (qmail 28160 invoked from network); 10 Jun 2004 15:44:02 -0000
Received: from sunsite.dk (130.225.247.90)
  by a.mx.sunsite.dk with SMTP; 10 Jun 2004 15:44:02 -0000
Received: (qmail 23164 invoked by alias); 10 Jun 2004 15:43:46 -0000
Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 7507
Received: (qmail 23154 invoked from network); 10 Jun 2004 15:43:46 -0000
Received: from thor.dotsrc.org (HELO a.mx.sunsite.dk) (qmailr@130.225.247.86)
  by sunsite.dk with SMTP; 10 Jun 2004 15:43:43 -0000
Received: (qmail 27248 invoked from network); 10 Jun 2004 15:43:42 -0000
Received: from moonbase.zanshin.com (root@64.84.47.139)
  by a.mx.sunsite.dk with SMTP; 10 Jun 2004 15:43:41 -0000
Received: from toltec.zanshin.com (toltec.zanshin.com [64.84.47.166])
	by moonbase.zanshin.com (8.12.11/8.12.11) with ESMTP id i5AFhd4B030183
	for <zsh-users@sunsite.dk>; Thu, 10 Jun 2004 08:43:39 -0700
Date: Thu, 10 Jun 2004 08:43:26 -0700 (PDT)
From: Bart Schaefer <schaefer@brasslantern.com>
Sender: schaefer@toltec.zanshin.com
Reply-To: Zsh Users <zsh-users@sunsite.dk>
To: Zsh Users <zsh-users@sunsite.dk>
Subject: Re: Named directories expansion
In-Reply-To: <20040609162148.GA11140@DervishD>
Message-ID: <Pine.LNX.4.44.0406100837500.7158-100000@toltec.zanshin.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Checker-Version: SpamAssassin 2.63 on a.mx.sunsite.dk
X-Spam-Level: 
X-Spam-Status: No, hits=0.0 required=6.0 tests=none autolearn=no version=2.63
X-Spam-Hits: 0.0

On Wed, 9 Jun 2004, DervishD wrote:

>     list=(**/*~(/explicit/path|~X))
> 
>     Will the named dir be expanded inside the expression?

No.

> In the manual I've read that each word is checked to see if it starts
> with an unquoted '~', is that quoted inside a (...) expression?

It's not quoted, but it's also not the start of a word.  "Word" here has
the very specific meaning of a shell-parser syntactic word, which means
that a word "starts" only immediately after an unquoted $IFS character, or
(as a special case) after a colon found to the right of the equal sign in
certain assignment expressions.