From: Drew Adams <drew.adams@oracle.com>
To: Sean Whitton <spwhitton@spwhitton.name>,
Eli Zaretskii <eliz@gnu.org>, Toon claes <toon@to1.studio>,
"62355@debbugs.gnu.org" <62355@debbugs.gnu.org>
Cc: "João Távora" <joaotavora@gmail.com>
Subject: bug#62355: 30.0.50; C-g doesn't always quit minibuffer on first press
Date: Thu, 23 Mar 2023 19:47:49 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488BF356C9D7BEB1EBF50ABF3879@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87zg83e032.fsf@melete.silentflame.com>
Whether or not there's a bug here I leave up
to you. (But I concur with what Eli said.)
___
While you're using the minibuffer, you
(interactively), as well as code running during
the interaction, can do any number of things,
some of which can initiate contexts where `C-g'
does something specific (e.g. exits from some
interaction within that context). This is of
course amplified if you (or some code) initiates
a recursive minibuffer.
Things to remember here:
1. `C-g' is a general command. Its behavior
is specific to the latest context for which it
has a meaning/behavior.
2. To exit the minibuffer (a single level)
directly, you can always use `C-]', which runs
the command `abort-recursive-edit'.
Get in the habit of using `C-j' to cancel/abort
the current minibuffer level.
If you have non-nil `enable-recursive-edit'
then you can also do this when in the minibuffer,
to exit _all_ minibuffer levels and return to
top level: `M-x top-level'. (It also exits all
recursive edits, not just recursive minibuffers.)
next prev parent reply other threads:[~2023-03-23 19:47 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
2023-03-23 19:31 ` Sean Whitton
2023-03-23 19:47 ` Drew Adams [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SJ0PR10MB5488BF356C9D7BEB1EBF50ABF3879@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=62355@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=joaotavora@gmail.com \
--cc=spwhitton@spwhitton.name \
--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 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.