From: Tanaka Akira <akr@jaist.ac.jp>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Completion/Cvs/
Date: 01 Sep 1999 21:01:34 +0900 [thread overview]
Message-ID: <rsqg10yu9gh.fsf@crane.jaist.ac.jp> (raw)
In-Reply-To: Sven Wischnowsky's message of "Wed, 1 Sep 1999 13:03:03 +0200 (MET DST)"
In article <199909011103.NAA00249@beta.informatik.hu-berlin.de>,
Sven Wischnowsky <wischnow@informatik.hu-berlin.de> writes:
> The patch was mostly cosmetic, in fact. The question is: will users
> think that `-e+::..' does what they want in this case or not?
> Personally I don't care much if the patch is included or, since I
> would use `-e-:..' in such cases.
I think the behavior before 7596 is reasonable though I don't know
command that is fit to use it.
> @@ -535,6 +537,7 @@
> optbeg="$nargbeg"
> argbeg="$nargbeg"
> fromrest=yes
> + [[ "$def" = \*::* ]] && opt=''
> fi
> fi
>
Hm.
is27e1u11% bindkey -e; fpath=($PWD/Completion/*(/)); autoload -U compinit; compinit -D; compdef _tst tst
is27e1u11% compconf group_matches=yes
is27e1u11% compconf message_format='%d'
is27e1u11% compconf description_format='%d'
is27e1u11% _tst () { _arguments '-e+:editor:(vi)' '*::mesg:false' }
is27e1u11% tst -e<TAB>
This should complete `vi', but does not.
is27e1u11% cvs <TAB>
add commit export log release tag watchers
admin diff history login remove unedit
annotate edit import logout rtag update
checkout editors init rdiff status watch
Also, this should complete cvs common options addition to cvs commands.
Reverting the hunk fix this problem. Is this correct?
--
Tanaka Akira
next prev parent reply other threads:[~1999-09-01 12:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-01 11:03 Sven Wischnowsky
1999-09-01 12:01 ` Tanaka Akira [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-09-01 12:23 Sven Wischnowsky
1999-09-01 9:25 Sven Wischnowsky
1999-09-01 10:35 ` Tanaka Akira
1999-08-31 15:03 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=rsqg10yu9gh.fsf@crane.jaist.ac.jp \
--to=akr@jaist.ac.jp \
--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).