From: Tanaka Akira <akr@m17n.org>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: _arguments -C cleanup (was: Re: PATCH: _look)
Date: 05 May 2000 23:46:42 +0900 [thread overview]
Message-ID: <hvou2gdnjfx.fsf@serein.m17n.org> (raw)
In-Reply-To: <200005051337.PAA06691@beta.informatik.hu-berlin.de> (Sven Wischnowsky's message of "Fri, 5 May 2000 15:37:03 +0200 (MET DST)")
In article <200005051337.PAA06691@beta.informatik.hu-berlin.de>,
Sven Wischnowsky <wischnow@informatik.hu-berlin.de> writes:
> Akira, in _look there was a compadd without a _wanted/description or
> anything. I've made it use the `value' tag with a `values'
> description, is there anything more precise we could use or is that ok?
Sorry. I forgot it. I think `word prefix' is better for explanation.
Also this adds completion for an optional second argument.
Index: Completion/User/_look
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/User/_look,v
retrieving revision 1.2
diff -u -r1.2 _look
--- Completion/User/_look 2000/05/05 13:38:46 1.2
+++ Completion/User/_look 2000/05/05 14:43:30
@@ -7,11 +7,12 @@
'-t+[termination character]:termination character:' \
'-f[case insensitive]' \
'-d[dictionary order]' \
- ':string:->string' && return 0
+ ':string:->string' \
+ ':dictionary file:_files -f' && return 0
case "$state" in
string)
[[ -n "$PREFIX" ]] &&
- _wanted values expl value compadd - $(_call values $words[1] $PREFIX)
+ _wanted values expl 'word prefix' compadd - $(_call values $words[1] $PREFIX)
;;
esac
--
Tanaka Akira
prev parent reply other threads:[~2000-05-05 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-05 13:37 Sven Wischnowsky
2000-05-05 14:46 ` Tanaka Akira [this message]
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=hvou2gdnjfx.fsf@serein.m17n.org \
--to=akr@m17n.org \
--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).