From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3502 invoked from network); 25 Feb 2003 09:33:36 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 25 Feb 2003 09:33:36 -0000 Received: (qmail 15856 invoked by alias); 25 Feb 2003 09:33:28 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 18288 Received: (qmail 15849 invoked from network); 25 Feb 2003 09:33:27 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 25 Feb 2003 09:33:27 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [193.109.254.147] by sunsite.dk (MessageWall 1.0.8) with SMTP; 25 Feb 2003 9:33:27 -0000 X-VirusChecked: Checked X-Env-Sender: kiddleo@logica.com X-Msg-Ref: server-17.tower-27.messagelabs.com!1046165606!1175 Received: (qmail 12853 invoked from network); 25 Feb 2003 09:33:26 -0000 Received: from iris.logica.co.uk (158.234.9.163) by server-17.tower-27.messagelabs.com with SMTP; 25 Feb 2003 09:33:26 -0000 Received: from finches.logica.co.uk ([158.234.142.11]) by iris.logica.co.uk (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id JAA21438 for ; Tue, 25 Feb 2003 09:33:25 GMT X-Authentication-Warning: iris.logica.co.uk: Host [158.234.142.11] claimed to be finches.logica.co.uk Received: from finches.logica.co.uk (localhost [127.0.0.1]) by finches.logica.co.uk (8.11.6/8.11.6/SuSE Linux 0.5) with ESMTP id h1P9b6b01455 for ; Tue, 25 Feb 2003 10:37:06 +0100 In-reply-to: <1030223014259.ZM11349@candle.brasslantern.com> From: Oliver Kiddle References: <1030223014259.ZM11349@candle.brasslantern.com> To: zsh-workers@sunsite.dk Subject: Re: Doc for compdef and #compdef is out of date Date: Tue, 25 Feb 2003 10:37:06 +0100 Message-ID: <1453.1046165826@finches.logica.co.uk> Sender: kiddleo@logica.com On 23 Feb, Bart wrote: > There's no mention of `#compdef -T ...' or of what that translates into > in the actual `compdef' command; there's also no mention of using a comma- > separated list of context names [as is described under the entry for the > `_complete' function]. #compdef -T does not exist. See the first paragraph of 16795. And, I'm not sure what you mean by a comma-separated list of context names unless you just mean the -redirect-,op,command and -value-,name,command forms. Looking over the documentation for _complete and compdef/#compdef, it all looks complete and up-to-date to me. Much of _complete's documentation covering contexts should perhaps be moved to where compdef is documented so that _complete's documentation can focus on how it fits in relative to _expand, _approximate and other completers while documenting the contexts near compdef makes it more obvious that the names used with compdef can be contexts as well as command names. Only thing which does seem to be missing is the -N option from the compdef synopsis. Other than that, I can't see what I could add to it. And just something I noticed in _complete's documentation, does anyone know what the point of the $compcontext additions in 12449 and 12483 were. Where might you set compcontext to an array? I can sort-of understand the use in _nslookup but that is the only use. Oliver This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.