GNU bug report logs - #43440
completion in minibuffer missing initial asterisk

Previous Next

To reply to this bug, email your comments to 43440 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
To: bug-gnu-emacs <at> gnu.org
Subject: completion in minibuffer missing initial asterisk
Date: Wed, 16 Sep 2020 13:54:03 +0800

[Message part 1 (text/plain, inline)]

What's the deal? All the completions start with a "*",
so why doesn't the one being built in the minibuffer have it?

[30194-0.jpg (image/jpeg, inline)]

[Message part 3 (text/plain, inline)]

I typed:
 C-x b [switch-to-buffer]
 u [self-insert-command]
 n [self-insert-command]
 s [self-insert-command]
 <tab> [minibuffer-complete]
 <tab> [minibuffer-complete]

emacs-version "26.3" Tested with emacs -q too.

Message #8 received at 43440 <at> debbugs.gnu.org (full text, mbox):

From: Stephen Berman <stephen.berman <at> gmx.net>
To: 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Cc: 43440 <at> debbugs.gnu.org
Subject: Re: bug#43440: completion in minibuffer missing initial asterisk
Date: Wed, 16 Sep 2020 09:36:41 +0200

On Wed, 16 Sep 2020 13:54:03 +0800 積丹尼 Dan Jacobson <jidanni <at> jidanni.org> wrote:

> What's the deal? All the completions start with a "*",
> so why doesn't the one being built in the minibuffer have it?

It's not just "*" but any string that all completion candidates share.
I think this is related to the issue raised in bug#38476 (which is a
feature request following on bug#38458).

Steve Berman

Message #11 received at 43440 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Stephen Berman <stephen.berman <at> gmx.net>
Cc: 43440 <at> debbugs.gnu.org,
 積丹尼 Dan Jacobson <jidanni <at> jidanni.org>
Subject: Re: bug#43440: completion in minibuffer missing initial asterisk
Date: Thu, 17 Sep 2020 17:26:53 +0200

[Message part 1 (text/plain, inline)]

Stephen Berman <stephen.berman <at> gmx.net> writes:

> On Wed, 16 Sep 2020 13:54:03 +0800 積丹尼 Dan Jacobson
> <jidanni <at> jidanni.org> wrote:
>
>> What's the deal? All the completions start with a "*",
>> so why doesn't the one being built in the minibuffer have it?
>
> It's not just "*" but any string that all completion candidates share.
> I think this is related to the issue raised in bug#38476 (which is a
> feature request following on bug#38458).

It's kinda similar, but in this case the problem is more glaring -- all
the completion candidates share the same prefix, so why isn't that
prefix included in the completion string?

Here's the reproducible test case:

(progn
  (switch-to-buffer "foobar1")
  (switch-to-buffer "foobar2")
  (switch-to-buffer "*scratch*")
  (call-interactively 'switch-to-buffer))

Eval and then type `bar TAB':

[Message part 2 (image/png, inline)]

[Message part 3 (text/plain, inline)]

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.