From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: <zsh-users@sunsite.auc.dk>
Subject: RE: completion with globbing, take 2
Date: Wed, 20 Sep 2000 19:06:54 +0400 [thread overview]
Message-ID: <001a01c02314$69b93f40$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <1000919020251.ZM30124@candle.brasslantern.com>
> } > The most obvious thing would be to have _match itself recognize the
> } > completions style.
> }
> } Is is not enough. See later.
>
> Not enough for what?
>
I must apologize. For some reason I had impression, that _expand offers all
possible *completions* in addition to expansions. What led me to it was
There is another style, completions, which allows _expand to
display or insert all _completions_ generated for the string. The
use of this is that the tags expansions and all-expansions are
available, unlike with _complete.
Actually, you can either insert all completions (without possibility to menu
select AND without doing full completion - it is using only _complete so
matching won't work) *or* choose from the expansions. Docs could be more clear
on this point.
-andrej
next prev parent reply other threads:[~2000-09-20 15:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-17 17:50 E. Jay Berkenbilt
2000-09-17 18:43 ` Bart Schaefer
2000-09-17 23:03 ` E. Jay Berkenbilt
2000-09-18 0:17 ` completion and globbing, part 2 E. Jay Berkenbilt
2000-09-18 6:53 ` Andrej Borsenkow
2000-09-18 9:59 ` insert-all-matches example " Andrej Borsenkow
2000-09-18 17:28 ` completion with globbing, take 2 Bart Schaefer
2000-09-18 18:08 ` Andrej Borsenkow
2000-09-19 2:02 ` Bart Schaefer
2000-09-20 15:06 ` Andrej Borsenkow [this message]
2000-09-20 16:12 ` Bart Schaefer
2000-09-18 22:07 ` E. Jay Berkenbilt
2000-09-19 2:14 ` Bart Schaefer
2001-02-20 9:55 ` Job Table Nick Cross
2000-09-18 6:07 ` completion with globbing, take 2 Andrej Borsenkow
2000-10-04 11:14 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='001a01c02314$69b93f40$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=zsh-users@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).