From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10015 invoked from network); 27 Jul 2000 08:10:24 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 27 Jul 2000 08:10:24 -0000 Received: (qmail 8711 invoked by alias); 27 Jul 2000 08:10:15 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 12398 Received: (qmail 8704 invoked from network); 27 Jul 2000 08:10:14 -0000 From: "Bart Schaefer" Message-Id: <1000727081007.ZM31861@candle.brasslantern.com> Date: Thu, 27 Jul 2000 08:10:07 +0000 In-Reply-To: <200007270717.JAA15601@beta.informatik.hu-berlin.de> Comments: In reply to Sven Wischnowsky "PATCH: Re: problem with _arguments" (Jul 27, 9:17am) References: <200007270717.JAA15601@beta.informatik.hu-berlin.de> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-workers@sunsite.auc.dk Subject: Re: PATCH: Re: problem with _arguments MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Jul 27, 9:17am, Sven Wischnowsky wrote: } } The patch will make it show the message and the option, which is what } should have been done before. If this is good or if it should only } complete the option is a different question. Hm. Hm? Recalling that the original spec was: - the function has one optional option '-l' with no parameter - the first parameter can't be completed - subsequent parameters are files I think _arguments has done the right thing, because any string other than "-l" might just be a first parameter that happens to begin with hyphen. However, if the spec had been "the first parameter must not begin with a hyphen but cannot be completed" then I don't know how to express that in the current _arguments syntax without using a state machine, which seems like overkill in this situation. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net