From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>,
"E. Jay Berkenbilt" <ejb@ql.org>
Cc: <zsh-workers@sunsite.auc.dk>
Subject: RE: still confused about completion and matching
Date: Tue, 24 Oct 2000 19:28:31 +0400 [thread overview]
Message-ID: <000f01c03dcf$10c403e0$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <1001024151504.ZM12258@candle.brasslantern.com>
>
> insert-unambiguous
> This is used by the _match and _approximate completer functions,
> where the possible completions may not have a common prefix so
> that menu completion is often the most useful may of choosing
> completions. If the style is set to `true', the completer will
> start menu completion only if no unambiguous string could be
> generated that is at least as long as the original string typed by
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> the user.
^^^^^^^^^^
That is the problem. It means, that if you have long pattern that results in
short match, menu completion is started.
I was never happy about it as well. But I switched to menu selection some time
ago :-)
-andrej
next prev parent reply other threads:[~2000-10-24 15:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-24 7:44 Sven Wischnowsky
2000-10-24 15:00 ` E. Jay Berkenbilt
2000-10-24 15:15 ` Bart Schaefer
2000-10-24 15:28 ` Andrej Borsenkow [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-10-25 7:50 Sven Wischnowsky
2000-11-06 15:34 ` E. Jay Berkenbilt
2000-10-25 7:12 Sven Wischnowsky
2000-10-25 7:41 ` Andrej Borsenkow
2000-10-23 13:20 Sven Wischnowsky
2000-10-19 9:11 Sven Wischnowsky
2000-10-20 16:38 ` E. Jay Berkenbilt
2000-10-20 16:57 ` Andrej Borsenkow
2000-10-20 20:45 ` E. Jay Berkenbilt
2000-10-23 7:15 ` Andrej Borsenkow
2000-10-23 13:11 ` E. Jay Berkenbilt
2000-10-16 8:05 Sven Wischnowsky
2000-10-17 19:30 ` E. Jay Berkenbilt
2000-10-13 11:03 Sven Wischnowsky
2000-10-12 19:56 E. Jay Berkenbilt
2000-10-12 20:32 ` E. Jay Berkenbilt
2000-10-16 5:01 ` 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='000f01c03dcf$10c403e0$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=ejb@ql.org \
--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).