From: Eli Zaretskii <eliz@gnu.org>
To: Toon claes <toon@to1.studio>
Cc: 62355@debbugs.gnu.org
Subject: bug#62355: 30.0.50; C-g doesn't always quit minibuffer on first press
Date: Wed, 22 Mar 2023 05:29:46 +0200 [thread overview]
Message-ID: <831qlh79at.fsf@gnu.org> (raw)
In-Reply-To: <b8979de9939d41d0ed5ca85d0699bdde.toon@to1.studio> (message from Toon claes on Tue, 21 Mar 2023 20:16:17 +0100)
> Date: Tue, 21 Mar 2023 20:16:17 +0100
> From: Toon claes <toon@to1.studio>
>
> For a while I've been having trouble C-g isn't quitting the minibuffer
> after the first press.
>
> When I start Emacs freshly I can press M-x, that triggers the
> minibuffer, and pressing C-g quits the minibuffer again.
>
> But after a short while of use this behaviour changes. Pressing M-x
> still triggers the minibuffer, but pressing C-g prints "[Quit]" while it
> keeps the minibuffer active. Only after pressing C-g a second time the
> minibuffer is actually quit.
>
> I was able to reproduce in "emacs -Q", but I haven't so far been able to
> reproduce with "emacs -Q -nw", although I'm not sure it's related to any
> of that.
>
> Below is the output of "C-h l" (view-lossage) reproducing the issue:
>
> C-x b ;; switch-to-buffer
> C-g ;; abort-minibuffers
> M-x ;; execute-extended-command
> C-g C-g ;; abort-minibuffers
> C-h l ;; view-lossage
>
> You can see the first time I press C-g once to abort-minibuffers. The
> second time I have to C-g twice.
>
> This time it happened right after a fresh start of "emacs -Q", but
> sometimes I have to do a lot more actions before the double C-g is
> needed.
This is normal when you have switched away of the active minibuffer
with "C-x o" or something similar. The "[Quit]" message (in brackets)
is a telltale sign that the minibuffer is active and waiting for you
to finish some interaction.
However, if you can show a recipe to reproduce this, we could be sure.
next prev parent reply other threads:[~2023-03-22 3:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 19:16 bug#62355: 30.0.50; C-g doesn't always quit minibuffer on first press Toon claes
2023-03-22 3:29 ` Eli Zaretskii [this message]
2023-03-23 19:31 ` Sean Whitton
2023-03-23 19:47 ` Drew Adams
2023-03-23 20:09 ` Eli Zaretskii
2023-03-24 0:01 ` Sean Whitton
2023-03-24 6:12 ` Eli Zaretskii
2023-03-24 7:56 ` Toon Claes
2023-03-24 11:56 ` Eli Zaretskii
2023-03-24 15:32 ` Toon Claes
2023-03-24 18:32 ` Eli Zaretskii
2023-03-24 19:17 ` Sean Whitton
2023-03-24 12:39 ` João Távora
2023-03-26 20:44 ` bug#62468: 30.0.50; Improve Icomplete while-no-input s.t. C-g quits the minibuffer Sean Whitton
2023-03-24 21:59 ` bug#62355: 30.0.50; C-g doesn't always quit minibuffer on first press Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831qlh79at.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62355@debbugs.gnu.org \
--cc=toon@to1.studio \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).