zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: complete rpm --{resign,addsign} in local
Date: Wed, 7 Jun 2000 10:01:55 +0200 (MET DST)	[thread overview]
Message-ID: <200006070801.KAA12563@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Mon, 5 Jun 2000 15:03:04 +0000


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


             reply	other threads:[~2000-06-07  8:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-07  8:01 Sven Wischnowsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-06-06  9:56 Sven Wischnowsky
2000-06-05  8:54 Sven Wischnowsky
2000-06-04 19:37 ` Chmouel Boudjnah
2000-06-04 21:09   ` Clint Adams
2000-06-05  1:13     ` Bart Schaefer
2000-06-05  1:18   ` Bart Schaefer
2000-06-05  9:47     ` Oliver Kiddle
2000-06-05 15:03       ` Bart Schaefer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200006070801.KAA12563@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).