* Bug with icomplete-mode
@ 2015-05-16 11:49 Slawomir Nowaczyk
2015-05-16 14:03 ` Dmitry Gutov
0 siblings, 1 reply; 3+ messages in thread
From: Slawomir Nowaczyk @ 2015-05-16 11:49 UTC (permalink / raw)
To: emacs-devel
Hello,
I have recently switched from (now obsolete) iswitchb to icomplete-mode
and I have encountered an issue with that.
emacs -Q
(icomplete-mode t)
(setq icomplete-show-matches-on-no-input t)
(get-buffer-create "aaa")
(get-buffer-create "bbb")
Press C-x b (switch buffer)
C-. (select buffer "aaa")
C-j
Emacs switches to "*Messages*", not the "aaa" buffer I have selected.
As far as I can tell, it's because of this part in the minibuffer-force-complete-and-exit
(if (and (eq (minibuffer-prompt-end) (point-max))
minibuffer-default)
;; Use the provided default if there's one (bug#17545).
--
Best wishes,
Slawomir Nowaczyk
( Slawomir.Nowaczyk@hh.se )
Program: A magic spell cast over a computer allowing it to turn
one's input into error messages.
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Bug with icomplete-mode
2015-05-16 11:49 Bug with icomplete-mode Slawomir Nowaczyk
@ 2015-05-16 14:03 ` Dmitry Gutov
2015-05-17 12:36 ` Stephen Leake
0 siblings, 1 reply; 3+ messages in thread
From: Dmitry Gutov @ 2015-05-16 14:03 UTC (permalink / raw)
To: Slawomir Nowaczyk, emacs-devel
On 05/16/2015 02:49 PM, Slawomir Nowaczyk wrote:
> Emacs switches to "*Messages*", not the "aaa" buffer I have selected.
Yep, looks like a problem. But next time please do M-x report-emacs-bug.
> As far as I can tell, it's because of this part in the minibuffer-force-complete-and-exit
> (if (and (eq (minibuffer-prompt-end) (point-max))
> minibuffer-default)
> ;; Use the provided default if there's one (bug#17545).
And this part is due to the bug that is referenced in the comment.
Looking at it, it seems that a better way to resolve it would be to
always make the default value the first item, even when it's not in the
collection passed to completing-read.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Bug with icomplete-mode
2015-05-16 14:03 ` Dmitry Gutov
@ 2015-05-17 12:36 ` Stephen Leake
0 siblings, 0 replies; 3+ messages in thread
From: Stephen Leake @ 2015-05-17 12:36 UTC (permalink / raw)
To: emacs-devel
Dmitry Gutov <dgutov@yandex.ru> writes:
> On 05/16/2015 02:49 PM, Slawomir Nowaczyk wrote:
>
>> Emacs switches to "*Messages*", not the "aaa" buffer I have selected.
>
> Yep, looks like a problem. But next time please do M-x report-emacs-bug.
>
>> As far as I can tell, it's because of this part in the minibuffer-force-complete-and-exit
>> (if (and (eq (minibuffer-prompt-end) (point-max))
>> minibuffer-default)
>> ;; Use the provided default if there's one (bug#17545).
>
> And this part is due to the bug that is referenced in the comment.
>
> Looking at it, it seems that a better way to resolve it would be to
> always make the default value the first item, even when it's not in
> the collection passed to completing-read.
+1
--
-- Stephe
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-05-17 12:36 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-05-16 11:49 Bug with icomplete-mode Slawomir Nowaczyk
2015-05-16 14:03 ` Dmitry Gutov
2015-05-17 12:36 ` Stephen Leake
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).