From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>,
<zsh-workers@sunsite.auc.dk>
Subject: RE: PATCH: _expand, _expand_word, and their doc
Date: Thu, 21 Sep 2000 10:33:10 +0400 [thread overview]
Message-ID: <000201c02395$cf594fd0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <1000920175716.ZM31823@candle.brasslantern.com>
> +inserted into the command line. This style is most useful when set
> +only for very specific completion contexts.
I continue to ask myself just how useful it is.
completions style is tested only in _expand. It is either called from
_main_complete or directly (currently from _expand_word only). At the time
when completions style is tested, context is
:completion::expand::
-or-
:completion:expand-word:expand::
(I just realized, that completer has fixed value in this case :-)
Even if _main_complete would have set command name, the most sepecific context
would be
:completion:*:expand:${command_name}::
Anything more specific is set (if ever) only inside of per-command competion
function. It means, that at most you can request insertion of all completions
for a given command. It is very unlikely that anybody ever really wants it.
While in case of 'cvs rm TAB' insertion is appropriate, it is hardly useful in
case of 'cvs -TAB'. And currently even this is not possible - at most you can
state that all completions should be inserted for a given widget :-))
Unless I again miss something obvious.
-andrej
next prev parent reply other threads:[~2000-09-21 6:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-20 17:57 Bart Schaefer
2000-09-21 5:07 ` Bart Schaefer
2000-09-21 6:33 ` Andrej Borsenkow [this message]
2000-09-21 14:37 ` Bart Schaefer
2000-09-21 14:59 ` Andrej Borsenkow
2000-10-05 8:13 Sven Wischnowsky
2000-10-05 15:21 ` Bart Schaefer
2000-10-05 15:34 ` Andrej Borsenkow
2000-10-05 17:11 ` Bart Schaefer
2000-10-06 8:14 Sven Wischnowsky
2000-10-06 12:34 ` Andrej Borsenkow
2000-10-06 13:00 ` Sven Wischnowsky
2000-10-08 19:35 ` Bart Schaefer
2000-10-09 11:49 Sven Wischnowsky
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='000201c02395$cf594fd0$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=schaefer@candle.brasslantern.com \
--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).