From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3512 invoked from network); 14 Nov 2003 13:10:24 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 14 Nov 2003 13:10:24 -0000 Received: (qmail 25423 invoked by alias); 14 Nov 2003 13:10:07 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6770 Received: (qmail 25403 invoked from network); 14 Nov 2003 13:10:07 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 14 Nov 2003 13:10:07 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [193.109.254.211] by sunsite.dk (MessageWall 1.0.8) with SMTP; 14 Nov 2003 13:10:6 -0000 X-VirusChecked: Checked X-Env-Sender: okiddle@yahoo.co.uk X-Msg-Ref: server-7.tower-36.messagelabs.com!1068815405!1808700 X-StarScan-Version: 5.1.13; banners=-,-,- Received: (qmail 10310 invoked from network); 14 Nov 2003 13:10:05 -0000 Received: from iris.logica.co.uk (158.234.9.163) by server-7.tower-36.messagelabs.com with SMTP; 14 Nov 2003 13:10:05 -0000 Received: from gmcs3.local ([158.234.142.61]) by iris.logica.co.uk (8.12.3/8.12.3/Debian -4) with ESMTP id hAEDA4Ab030420 for ; Fri, 14 Nov 2003 13:10:05 GMT Received: from gmcs3.local (localhost [127.0.0.1]) by gmcs3.local (8.11.6/8.11.6/SuSE Linux 0.5) with ESMTP id hAED9JQ22729 for ; Fri, 14 Nov 2003 14:09:19 +0100 To: zsh-users@sunsite.dk X-VirusChecked: Checked X-StarScan-Version: 5.0.7; banners=.,-,- In-reply-to: <644.1068806872@csr.com> From: Oliver Kiddle References: <644.1068806872@csr.com> Subject: Re: Completion function for bitkeeper? Date: Fri, 14 Nov 2003 14:09:19 +0100 Message-ID: <22727.1068815359@gmcs3.local> Peter wrote: > 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). Do we need to actually say it's deprecated? Can't we just remove that part of the documentation and add a bit under the brace form about expl. We can mention in the next release note and in a comment inside _arguments that the feature is 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. Yes, that's also pointless. Virtually nobody bothers to use it anyway. Leaving the action empty is what most people have done (though varying on whether to include the trailing colon). So we can get rid of that from the documentation too. I'll come up with a patch this weekend. Including finding all the places we've used the initial space in existing functions. Oliver