From: Tom <adatgyujto@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Substring matching for info index command
Date: Sun, 7 Dec 2014 14:16:38 +0000 (UTC) [thread overview]
Message-ID: <loom.20141207T151328-959@post.gmane.org> (raw)
In-Reply-To: d4ac20c6-a256-4e01-85e4-eb941212d1ca@default
Drew Adams <drew.adams <at> oracle.com> writes:
>
> In other words, the problem is not with completion; it is
> with the way `Info-index' gathers the completion candidates
> from the indexes. It does that by simply searching for
> your input, as a prefix (prepended by `* ', which is what
> is on the index-entry line in the index.
Thanks for your investigation, but why should info use
my input to gather completion candidates? It should
gather all candiates and pass them them to
completing-read, shouldn't it?
Isn't it a bug? Incosistent behavior with the
builtin completion-styles?
next prev parent reply other threads:[~2014-12-07 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 12:15 Substring matching for info index command Tom
2014-12-07 14:06 ` Drew Adams
2014-12-07 14:16 ` Tom [this message]
2014-12-07 14:56 ` Drew Adams
2014-12-07 15:56 ` Eli Zaretskii
2014-12-07 16:02 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20141207T151328-959@post.gmane.org \
--to=adatgyujto@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).