* bug#43440: completion in minibuffer missing initial asterisk
@ 2020-09-16 5:54 積丹尼 Dan Jacobson
2020-09-16 7:36 ` Stephen Berman
0 siblings, 1 reply; 3+ messages in thread
From: 積丹尼 Dan Jacobson @ 2020-09-16 5:54 UTC (permalink / raw)
To: 43440
[-- Attachment #1: Type: text/plain, Size: 118 bytes --]
What's the deal? All the completions start with a "*",
so why doesn't the one being built in the minibuffer have it?
[-- Attachment #2: Why? --]
[-- Type: image/jpeg, Size: 24336 bytes --]
[-- Attachment #3: Type: text/plain, Size: 217 bytes --]
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#43440: completion in minibuffer missing initial asterisk
2020-09-16 5:54 bug#43440: completion in minibuffer missing initial asterisk 積丹尼 Dan Jacobson
@ 2020-09-16 7:36 ` Stephen Berman
2020-09-17 15:26 ` Lars Ingebrigtsen
0 siblings, 1 reply; 3+ messages in thread
From: Stephen Berman @ 2020-09-16 7:36 UTC (permalink / raw)
To: 積丹尼 Dan Jacobson; +Cc: 43440
On Wed, 16 Sep 2020 13:54:03 +0800 積丹尼 Dan Jacobson <jidanni@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
^ permalink raw reply [flat|nested] 3+ messages in thread
* bug#43440: completion in minibuffer missing initial asterisk
2020-09-16 7:36 ` Stephen Berman
@ 2020-09-17 15:26 ` Lars Ingebrigtsen
0 siblings, 0 replies; 3+ messages in thread
From: Lars Ingebrigtsen @ 2020-09-17 15:26 UTC (permalink / raw)
To: Stephen Berman; +Cc: 43440, 積丹尼 Dan Jacobson
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
Stephen Berman <stephen.berman@gmx.net> writes:
> On Wed, 16 Sep 2020 13:54:03 +0800 積丹尼 Dan Jacobson
> <jidanni@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':
[-- Attachment #2: Type: image/png, Size: 47723 bytes --]
[-- Attachment #3: Type: text/plain, Size: 105 bytes --]
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-09-17 15:26 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-09-16 5:54 bug#43440: completion in minibuffer missing initial asterisk 積丹尼 Dan Jacobson
2020-09-16 7:36 ` Stephen Berman
2020-09-17 15:26 ` Lars Ingebrigtsen
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.