From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9167 invoked from network); 7 Jun 2000 08:02:25 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 7 Jun 2000 08:02:25 -0000 Received: (qmail 29109 invoked by alias); 7 Jun 2000 08:02:01 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11793 Received: (qmail 29098 invoked from network); 7 Jun 2000 08:02:00 -0000 Date: Wed, 7 Jun 2000 10:01:55 +0200 (MET DST) Message-Id: <200006070801.KAA12563@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: "Bart Schaefer"'s message of Mon, 5 Jun 2000 15:03:04 +0000 Subject: Re: PATCH: complete rpm --{resign,addsign} in local Bart Schaefer wrote: > On Jun 5, 10:54am, Sven Wischnowsky wrote: > > ... > > } What makes me cringe is the case where we have -xy and both options > } have arguments... > > You mean like `tar fvcbz foo.tar.gz 1024 foo'? > > I don't think it's incumbent upon _arguments to handle this without help; > that's exactly what the state machine is for. It just has to be possible > to tell _arguments that other option letters are allowed in the string of > options even after one that has a following argument, so that it can go > to the right next state. > > This could be done by something like `_arguments -s+ ...' if it's too > awful to come up with still more OPTSPEC syntax (which I'm beginning to > believe that it is). After thinking some more about this... I think we have to make comparguments understand this because it has to be able to skip over the arguments when completer after them. Right? Maybe I'll have a look at this at the weekend. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de