From: Stefan Monnier <monnier@iro.umontreal.ca>
To: rms@gnu.org
Cc: 9598@debbugs.gnu.org
Subject: bug#9598: 24.0.50; completion goes too far
Date: Mon, 10 Oct 2011 22:52:50 -0400 [thread overview]
Message-ID: <jwvmxd82qjy.fsf-monnier+gnus-read-ephemeral-bug@gnu.org> (raw)
In-Reply-To: <E1R8acK-0004ao-EA@fencepost.gnu.org> (Richard Stallman's message of "Tue, 27 Sep 2011 12:34:48 -0400")
> It's somewhat difficult to distinguish the "all-completions for display"
> case from the "all-completions for completion" in the existing
> completion framework.
> But I'll see how we can get that behavior.
> I thought the distinction is between `try-completions' and
> `all-completions'. What am I missing?
Completion styles other than plain prefix completion
(e.g. partial-completion, substring completion, ...) can't just use
try-completion, so they use all-completions and then merge the resulting
entries to construct the result of completion.
So `all-completions' is sometimes used to build a *Completions* buffer,
but it's also used internally in various cases to perform completion.
So removing the current buffer from completion means it needs to be
removed from `all-completions's output, whereas displaying it in
*Completions* means it should be included in `all-completions's output.
This said, I can't think of any reason why it's important to show the
current buffer in *Completions* for C-x b since C-x b is about switching
to another buffer.
Stefan
next prev parent reply other threads:[~2011-10-11 2:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-25 17:34 bug#9598: 24.0.50; completion goes too far Richard Stallman
2011-09-25 18:47 ` Drew Adams
2011-09-26 1:00 ` Richard Stallman
2011-09-26 1:53 ` Drew Adams
2011-09-26 6:09 ` Eli Zaretskii
2011-09-26 10:42 ` Richard Stallman
2011-09-26 11:34 ` Eli Zaretskii
2011-09-26 21:12 ` Richard Stallman
2022-02-06 0:05 ` bug#12916: 24.2; Completion for "C-x b" does not include current buffer Lars Ingebrigtsen
2011-09-26 2:45 ` bug#9598: 24.0.50; completion goes too far Stefan Monnier
2011-09-26 10:42 ` Richard Stallman
2011-09-27 2:25 ` Stefan Monnier
2011-09-27 16:34 ` Richard Stallman
2011-10-11 2:52 ` Stefan Monnier [this message]
2011-10-11 22:01 ` Richard Stallman
2016-01-31 14:30 ` bug#9598: Status: C-x b completion should also display current buffer Marcin Borkowski
2016-01-31 16:18 ` bug#12916: " Drew Adams
2016-01-31 16:56 ` Eli Zaretskii
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=jwvmxd82qjy.fsf-monnier+gnus-read-ephemeral-bug@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=9598@debbugs.gnu.org \
--cc=rms@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).