From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: completion docs
Date: Tue, 2 May 2000 13:18:41 +0200 (MET DST) [thread overview]
Message-ID: <200005021118.NAA02586@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: Tanaka Akira's message of 02 May 2000 18:17:58 +0900
Tanaka Akira wrote:
> In article <200005020811.KAA29433@beta.informatik.hu-berlin.de>,
> Sven Wischnowsky <wischnow@informatik.hu-berlin.de> writes:
>
> > @@ -1705,12 +1710,12 @@
> >
> > For example:
> >
> > -example(zstyle ':completion:*:complete:gunzip:*' tag-order \
> > - arguments options)
> > +example(zstyle ':completion:*:complete:-command-:*' tag-order \
> > + 'commands functions')
> >
> > -specifies that completion after tt(gunzip) should offer completions for
> > -both arguments and options immediately, instead of offering first
> > -arguments and then option as usual.
> > +specifies that completion in command position after tt(gunzip) should
> > +offer only completions for external commands and shell functions
> > +immediately.
> >
> > In addition to tag names, each string in the value may take one of the
> > following forms:
>
> gunzip? The example doesn't mention gunzip.
Argh. Forgot to delete some words.
> Also note that, I think auto-descrive style mentioned in line 2911 is
> obsolete.
It's named auto-description, right.
Thanks.
Bye
Sven
Index: Doc/Zsh/compsys.yo
===================================================================
RCS file: /cvsroot/zsh/zsh/Doc/Zsh/compsys.yo,v
retrieving revision 1.29
diff -u -r1.29 compsys.yo
--- Doc/Zsh/compsys.yo 2000/05/02 08:14:29 1.29
+++ Doc/Zsh/compsys.yo 2000/05/02 11:17:25
@@ -1713,9 +1713,8 @@
example(zstyle ':completion:*:complete:-command-:*' tag-order \
'commands functions')
-specifies that completion in command position after tt(gunzip) should
-offer only completions for external commands and shell functions
-immediately.
+specifies that completion in command position should offer only
+completions for external commands and shell functions immediately.
In addition to tag names, each string in the value may take one of the
following forms:
@@ -2908,7 +2907,7 @@
given in brackets at the end, as in `tt(-q[query operation])'. The
tt(verbose) style is used to decide if these
explanation strings should be printed when options are listed. If no
-explanation string is given but the tt(auto-describe) style is
+explanation string is given but the tt(auto-description) style is
set and only one argument is described for this var(opt-spec), the
option will be described by the value of the style with any appearance
of the sequence `tt(%d)' in it replaced by the description for the
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-05-02 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-02 11:18 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-05-02 8:11 Sven Wischnowsky
2000-05-02 9:17 ` Tanaka Akira
2000-05-03 16:43 ` Bart Schaefer
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=200005021118.NAA02586@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).