From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Andreas Schwab <schwab@linux-m68k.org>
Cc: 29347@debbugs.gnu.org, rms@gnu.org
Subject: bug#29347: 27.0.50; C-g doesn't quit minibuffer
Date: Sun, 19 Nov 2017 11:11:38 -0800 (PST) [thread overview]
Message-ID: <6064751b-d52f-408a-9975-3336fcfb27a8@default> (raw)
In-Reply-To: <<83o9nydun1.fsf@gnu.org>>
> > > I meant enable-recursive-minibuffers, which AFAIK doesn't have any
> > > indications.
> >
> > A recursive minibuffer can be exited like an ordinary minibuffer, and
> > exiting it will return to the buffer from where you entered it.
>
> And that buffer to which you return is also a minibuffer. IOW, if you
> are N levels deep in a recursive minibuffer, you cannot exit it until
> you type C-g N times. This could be perceived as "C-g doesn't quit
> the minibuffer".
Clearly C-g _did_ quit the current minibuffer, in that scenario.
If you are in the Nth minibuffer then hitting C-g N times quits
N minibuffers - you are no longer in any minibuffer. (To quit
all minibuffers you can use C-].)
I don't think that's what the problem reported refers to.
That's the normal behavior, and it always has been.
next prev parent reply other threads:[~2017-11-19 19:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 3:46 bug#29347: 27.0.50; C-g doesn't quit minibuffer Richard Stallman
2017-11-18 6:17 ` Andreas Schwab
2017-11-18 6:24 ` Drew Adams
2017-11-18 8:04 ` Eli Zaretskii
2017-11-19 3:21 ` Richard Stallman
2017-11-19 3:42 ` Eli Zaretskii
2017-11-19 8:33 ` Andreas Schwab
2017-11-19 15:44 ` Eli Zaretskii
2017-11-19 17:21 ` Andreas Schwab
2017-11-19 17:51 ` Eli Zaretskii
[not found] ` <<83o9nydun1.fsf@gnu.org>
2017-11-19 19:11 ` Drew Adams [this message]
2017-11-20 2:56 ` Richard Stallman
2017-11-20 2:55 ` Richard Stallman
2017-11-19 18:09 ` Richard Stallman
2017-11-20 18:09 ` Mike Gerwitz
2017-11-20 18:36 ` Eli Zaretskii
2017-11-20 20:26 ` Mike Gerwitz
2017-11-24 16:17 ` Eli Zaretskii
2017-11-24 21:14 ` Eli Zaretskii
2017-11-24 21:41 ` Eli Zaretskii
2017-11-25 23:16 ` bug#29370: " Richard Stallman
2017-11-27 4:48 ` Mike Gerwitz
2017-11-27 16:16 ` Eli Zaretskii
2017-11-27 23:28 ` bug#29370: " Richard Stallman
2017-11-28 3:33 ` Eli Zaretskii
2017-12-01 8:37 ` bug#29347: " Eli Zaretskii
2017-11-20 21:51 ` Richard Stallman
[not found] <<E1eFu5X-0002CK-7x@fencepost.gnu.org>
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=6064751b-d52f-408a-9975-3336fcfb27a8@default \
--to=drew.adams@oracle.com \
--cc=29347@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rms@gnu.org \
--cc=schwab@linux-m68k.org \
/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).