GNU bug report logs - #62355
30.0.50; C-g doesn't always quit minibuffer on first press

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Sean Whitton <spwhitton <at> spwhitton.name>
Cc: toon <at> to1.studio, joaotavora <at> gmail.com, 62355 <at> debbugs.gnu.org
Subject: bug#62355: 30.0.50; C-g doesn't always quit minibuffer on first press
Date: Fri, 24 Mar 2023 09:12:13 +0300

> Date: Thu, 23 Mar 2023 17:01:08 -0700
> From: Sean Whitton <spwhitton <at> spwhitton.name>
> Cc: toon <at> to1.studio, 62355 <at> debbugs.gnu.org, joaotavora <at> gmail.com
> 
> On Thu, Mar 23, 2023 at 10:09:00PM +0200, Eli Zaretskii wrote:
> >
> > It isn't a bug, but the expected and intentional behavior.
> 
> I thought that the idea with Icomplete &c. was that they would stop what they
> are doing in response to any keystrokes, not requiring an explicit quit, in
> order to be maximally unobtrusive.

We may be talking about two different issues.  The original report
doesn't mention Icomplete (AFAIU), it mentions the fact that C-g,
instead of exiting the minibuffer, just displays "[Quit]" (note the
brackets).  That is the expected and intentional behavior in Emacs 28
and later when Emacs needs to display an echo-area message and the
minibuffer is active.  Prior to Emacs 28, the echo-area message would
instead overwrite the minibuffer contents or conceal it for prolonged
periods of time.

You seem to be talking about something else, perhaps related to what
Icomplete does.  But I'm not at all sure what you describe is the same
behavior as the OP described.

Previous Next

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