From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: _arguments questions
Date: Wed, 5 Apr 2000 11:43:20 +0200 (MET DST) [thread overview]
Message-ID: <200004050943.LAA02547@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Alexandre Duret-Lutz's message of 05 Apr 2000 11:28:48 +0200
Alexandre Duret-Lutz wrote:
> >>> "Sven" == Sven Wischnowsky <wischnow@informatik.hu-berlin.de> writes:
>
> ...
>
> Sven> Because of that (;-) and because it isn't quite the same (but I
> Sven> confess, I had the same idea...). Especially, adding this dummy
> Sven> element might be useful to combine with both `::' and `:::'.
>
> An helper function ?
>
> _with_dummy_arg0 () { # I'm not good at finding names...
> words=(dummy $words)
> (( ++CURRENT ))
> $@
> }
>
> _arguments -a -b '-c:*::blah: _with_dummy_arg0 _arguments -c -d -e'
I thought about that, too. And then thought this could easily be put
in _arguments, i.e. make it just look for a certain prefix in the
action -- as if there were a function called. I couldn't find another
use for this dummy-insertion-function...
> Quite ugly, but looks understandable. But taht way we can't get
> the 'parent' option (-c) for the dummy as you suggested.
We could. _arguments itself would probably use the same it puts into
$curcontext... (which in turn made me think that this wasn't so clever
an idea anyway).
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-04-05 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-05 9:43 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-04-05 12:03 Sven Wischnowsky
2000-04-05 13:01 ` Alexandre Duret-Lutz
2000-04-05 8:11 Sven Wischnowsky
2000-04-05 9:28 ` Alexandre Duret-Lutz
2000-04-04 12:54 Sven Wischnowsky
2000-04-04 15:59 ` Alexandre Duret-Lutz
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=200004050943.LAA02547@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).