From: Tanaka Akira <akr@jaist.ac.jp>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: _archie
Date: 21 Oct 1999 18:05:48 +0900 [thread overview]
Message-ID: <rsqwvshgk2b.fsf@crane.jaist.ac.jp> (raw)
In-Reply-To: Sven Wischnowsky's message of "Thu, 21 Oct 1999 10:32:40 +0200 (MET DST)"
In article <199910210832.KAA32127@beta.informatik.hu-berlin.de>,
Sven Wischnowsky <wischnow@informatik.hu-berlin.de> writes:
> It completed files for me, so I've just added the `*.y' case. Maybe
> you tried it without 8340?
Yes. I received 8340 after I sent 8343.
Thanks. All reported problems are fixed. But...
Now, I use zsh with patches up to 8352.
Z(2):akr@is27e1u11% Src/zsh -f
is27e1u11% bindkey -e; fpath=($PWD/Completion/*(/)); autoload -U compinit; compinit -D; compdef _tst tst
is27e1u11% compconf group_matches=yes message_format='%d' description_format='%d'
is27e1u11% compconf describe_options=yes describe_values=yes option_prefix=yes
(1) archie -N<TAB>
is27e1u11% archie -N<TAB><TAB>
->
is27e1u11% archie -N-D
flex -C<TAB> has same problem.
(2) bison -b <TAB>
is27e1u11% bison -b <TAB><TAB><TAB>
->
is27e1u11% bison -b V
(3) bison -vV<TAB>
is27e1u11% bison -vV<TAB>
It should complete other option letters.
(4) cvs -<TAB>
is27e1u11% cvs -<TAB>
is27e1u11% _tst () { _arguments -o '*::msg:_files' }
is27e1u11% tst -<TAB>
Although they complete nothing, they should complete options.
--
Tanaka Akira
next prev parent reply other threads:[~1999-10-21 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-21 8:32 Sven Wischnowsky
1999-10-21 9:05 ` Tanaka Akira [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-10-21 12:42 Sven Wischnowsky
1999-10-21 10:31 Sven Wischnowsky
1999-10-21 11:28 ` Tanaka Akira
1999-10-18 9:16 Sven Wischnowsky
1999-10-20 16:15 ` Tanaka Akira
1999-10-16 4:47 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=rsqwvshgk2b.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).