zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Question about _complete_help
Date: Tue, 7 Dec 1999 09:22:26 +0100 (MET)	[thread overview]
Message-ID: <199912070822.JAA06893@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Mon, 6 Dec 1999 18:36:53 +0300


Andrej Borsenkow wrote:

> I noted some difference between doc and actual output. Doc states:
> 
> The completion system represents such a context as a hierarchical name
> with components separated by colons. For example the name
> :complete:dvips:-o-1 is used when completing the first argument of the
> -o option of the dvips command.

Then your doc is out-of-date. At least mine says `:complete::dvips::-o-1'
and that ever since I made the command name be surrounded by double
colons, as you observed looking at the output of _complete_help:

> where actual output of _complete_help gives:
> 
> bor@itsrm2:~%> dvips -o ^Xh
> tags in context `:complete::dvips::-o-1':
>     arguments
>     globbed-files directories all-files
> 
> Are these double colons significant? This is really misleading. Note that for
> the command position:
> 
> bor@itsrm2:~%>
> tags in context `:complete:-command-':
>     commands executables jobs builtins functions aliases reserved-words
>     jobs
> 
> these double colons do not appear.

That's right. The double colons are *only* used around command names,
to make it very easy to unambiguously match it. See 8777 for further
enlightenment (and the up-to-date version of the docs, where I
mentioned this explicitly).


Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~1999-12-07  8:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-07  8:22 Sven Wischnowsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-12-06 15:36 Andrej Borsenkow

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=199912070822.JAA06893@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).