From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: _arguments problems
Date: Mon, 7 Feb 2000 09:54:46 +0100 (MET) [thread overview]
Message-ID: <200002070854.JAA30077@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Fri, 4 Feb 2000 18:35:57 +0000
Bart Schaefer wrote:
> On Feb 4, 10:59am, Sven Wischnowsky wrote (in 9559):
> } Subject: Re: _arguments problems
> }
> } *But* if we do that there wouldn't be a way to get at the options in
> } cases like this one (ok, it works with longer options but with short
> } ones like these one would have to type the whole option to complete
> } it). I'm really not sure if this is a good idea, I could only convince
> } myself to build that patch because one can always set the
> } prefix-needed style to false for such commands.
> }
> } I'd like to hear other opinions: does anyone think that this might
> } surprise users? Or maybe I'm worrying too much about to special a
> } case...
>
> On Feb 4, 3:18pm, Sven Wischnowsky wrote (in 9568):
> } Subject: Re: _arguments problems
> }
> } That's a completely different problem. And since the option-rest specs
> } do that I agree that normal rest specs should do the same.
>
> So ... should we *not* apply 9559 ?
[ It's 9560 ]
Personally, I'd prefer to not use the first hunk of 9560. But the
second one is needed in any case.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-02-07 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-07 8:54 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-05-10 7:42 Tanaka Akira
2000-02-04 9:59 Sven Wischnowsky
2000-02-04 13:16 ` Tanaka Akira
2000-02-04 14:18 ` Sven Wischnowsky
2000-02-04 18:35 ` Bart Schaefer
2000-02-03 19:14 Tanaka Akira
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=200002070854.JAA30077@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).