From: Alexandre Duret-Lutz <duret_g@epita.fr>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: _arguments questions
Date: 05 Apr 2000 15:01:24 +0200 [thread overview]
Message-ID: <mvbaej8zopn.fsf@phobos.lrde.epita.fr> (raw)
In-Reply-To: Sven Wischnowsky's message of "Wed, 5 Apr 2000 14:03:09 +0200 (MET DST)"
>>> "Sven" == Sven Wischnowsky <wischnow@informatik.hu-berlin.de> writes:
[...]
Sven> This does that: if the action starts with `= '
[...]
Sven> Is the syntax weird enough?
Yes :=) Thanks.
(seeing this last line I thougt that `=)' may have been funnier,
since it would have looked `...:=)...' and there already
exists `...:->...')
[...]
This is an use of `= ' :
Index: Completion/User/_prcs
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/User/_prcs,v
retrieving revision 1.1.1.6
diff -u -r1.1.1.6 _prcs
--- Completion/User/_prcs 2000/03/11 00:08:12 1.1.1.6
+++ Completion/User/_prcs 2000/04/05 12:51:14
@@ -136,7 +136,7 @@
'(--new)-N[compare new files against empty files]' \
"(-P)--exclude-project-file[don't diff the project file]" \
"(--exclude-project-file)-P[don't diff the project file]" \
- '--[introduce diff options]:*::diff options: _diff_options ${PRCS_DIFF_COMMAND:-diff}' \
+ '--[introduce diff options]:*::diff options:= _diff_options ${PRCS_DIFF_COMMAND:-diff}' \
':project name:_prcs_projects' \
'*:file or directory:_files'
;;
--
Alexandre Duret-Lutz
next prev parent reply other threads:[~2000-04-05 13:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-05 12:03 Sven Wischnowsky
2000-04-05 13:01 ` Alexandre Duret-Lutz [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-04-05 9:43 Sven Wischnowsky
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=mvbaej8zopn.fsf@phobos.lrde.epita.fr \
--to=duret_g@epita.fr \
--cc=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).