GNU bug report logs - #39564
28.0.50; read-key function do not display the prompt if called from read-from-minibuffer

Previous Next

Package: emacs;

Reported by: Ergus <spacibba <at> aol.com>

Date: Tue, 11 Feb 2020 14:51:01 UTC

Severity: normal

Found in version 28.0.50

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Matt Kramer <mccleetus <at> gmail.com>
To: 39564 <at> debbugs.gnu.org
Subject: bug#39564: 
Date: Wed, 26 Feb 2020 12:04:25 -0800
[Message part 1 (text/plain, inline)]
In my case I *do* get different behavior in emacs -Q between 26.3 and
27.0.60 (75a9eee8b). I had to replace minibuffer-keyboard-quit with
abort-recursive-edit, since the former doesn't exist in 26.3. The initial
minibuffer hint looks the same in both cases:

0
1
2
3
4
5
6
7
8
9
10
Test1:
       ^
       |--- cursor

After pressing C-f, 26.3 gives the expected result:

0
1
2
3
4
5
6
7
8
9
10
Test2
     ^
     |--- cursor

However, 27.0.60 gives me the following bizarre content in the minibuffer
(where did that square bracket come from?):

0
1
2
3
4
5
6
7
8
9
10
Test1:  [0
1
2
3
4

in which the cursor is on the 0 at the very top. The read-key function
appears to be identical between the two revisions, aside from a trivial
change to support tab-bar, so I have no idea where the culprit may lie.
[Message part 2 (text/html, inline)]

This bug report was last modified 3 years and 93 days ago.

Previous Next


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