From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 826 invoked from network); 14 Nov 2003 10:48:15 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 14 Nov 2003 10:48:15 -0000 Received: (qmail 3543 invoked by alias); 14 Nov 2003 10:47:57 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6769 Received: (qmail 3477 invoked from network); 14 Nov 2003 10:47:56 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 14 Nov 2003 10:47:56 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [62.189.183.235] by sunsite.dk (MessageWall 1.0.8) with SMTP; 14 Nov 2003 10:47:56 -0000 Received: from EXCHANGE02.csr.com (unverified) by MAILSWEEPER01.csr.com (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Fri, 14 Nov 2003 10:47:55 +0000 Received: from csr.com ([192.168.144.127]) by EXCHANGE02.csr.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 14 Nov 2003 10:49:00 +0000 To: zsh-users@sunsite.dk Subject: Re: Completion function for bitkeeper? In-reply-to: "Oliver Kiddle"'s message of "Fri, 14 Nov 2003 09:04:56 +0100." <29114.1068797096@gmcs3.local> Date: Fri, 14 Nov 2003 10:47:52 +0000 Message-ID: <644.1068806872@csr.com> From: Peter Stephenson X-OriginalArrivalTime: 14 Nov 2003 10:49:00.0435 (UTC) FILETIME=[E96CD630:01C3AA9C] Oliver Kiddle wrote: > For '*:desc:{_foo}' style actions, this is run: > > eval "$action[@]" > > and for '*:desc: _foo', this is run: > > eval "action=( $action )" > "$action[@]" > > Can anyone tell me what practical difference that makes, if any? > > What might be a good plan is to deprecate the initial space feature and > then, by only documenting expl under the {eval-string} form of action, > it will be easier make things clear in the documentation. I don't think we *need* both, and the brace is clearer --- more to the point, use of the space is almost completely opaque, plus it's hard to search for in the documentation. So switching the code makes sense. However, we might need a pointer in case people wonder about it, and since the documentation consists of one sentence it's not clear how much difference it makes to change it there (except to say it's deprecated). What about a single unquoted space to indicate no matches? Why do we need the space at all? Surely if there's nothing there it indicates no possible matches? It's all a bit Zen-like. -- Peter Stephenson Software Engineer CSR Ltd., Science Park, Milton Road, Cambridge, CB4 0WH, UK Tel: +44 (0)1223 692070 ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **********************************************************************