From: martin rudalics <rudalics@gmx.at>
To: Alan Mackenzie <acm@muc.de>, Drew Adams <drew.adams@oracle.com>
Cc: "al@petrofsky.org" <al@petrofsky.org>,
"63967@debbugs.gnu.org" <63967@debbugs.gnu.org>,
Eli Zaretskii <eliz@gnu.org>,
"monnier@iro.umontreal.ca" <monnier@iro.umontreal.ca>
Subject: bug#63967: 28.2; switch-to-buffer in normal window fails if minibuffer window is active
Date: Mon, 12 Jun 2023 09:17:29 +0200 [thread overview]
Message-ID: <d1a5f5d9-b91a-c95a-b66c-44112ab388f4@gmx.at> (raw)
In-Reply-To: <ZIXvzgSY3jFaGY6a@ACM>
> It might be useful to compare with the way most non-Emacs systems cope
> with these problems: they use what are known as "modal" dialogue boxes.
> Having initiated one of these, there is no way of doing anything else in
> the system, including looking at a buried frame, until the "modal"
> dialogue has been terminated or aborted. I think Emacs's way is better,
> even if not perfect.
Alas, this is no longer true. Start Emacs 29 via
emacs -Q --eval "(setq default-frame-alist '((minibuffer . nil)))"
Now type C-x 5 o to switch to the normal, minibuffer-less frame and then
type C-x f. Next try to access the normal frame via C-x o, C-x 5 o, the
window manager's Alt-TAB or any other key combination. This used to
work ever since. Now you are in a modal dialogue exactly as described
above.
martin
next prev parent reply other threads:[~2023-06-12 7:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 21:32 bug#63967: 28.2; switch-to-buffer in normal window fails if minibuffer window is active Al Petrofsky
2023-06-09 11:16 ` Eli Zaretskii
2023-06-09 15:08 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-09 16:09 ` Eli Zaretskii
2023-06-09 19:18 ` Eli Zaretskii
2023-06-10 15:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-10 19:42 ` Alan Mackenzie
2023-06-11 5:03 ` Eli Zaretskii
2023-06-11 13:40 ` Alan Mackenzie
2023-06-11 13:53 ` Eli Zaretskii
2023-06-13 18:43 ` Eli Zaretskii
2023-06-13 21:36 ` Alan Mackenzie
2023-06-14 12:15 ` Eli Zaretskii
2023-06-15 10:25 ` Alan Mackenzie
2023-06-17 11:31 ` Alan Mackenzie
2023-06-17 13:08 ` Eli Zaretskii
2023-06-17 13:52 ` martin rudalics
2023-06-17 16:23 ` Alan Mackenzie
2023-06-17 18:46 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-11 14:35 ` Drew Adams
2023-06-11 16:01 ` Alan Mackenzie
2023-06-12 7:17 ` martin rudalics [this message]
2023-06-12 12:04 ` Eli Zaretskii
2023-06-11 16:12 ` Eli Zaretskii
2023-06-09 16:52 ` Gregory Heytings
2023-06-09 17:21 ` Eli Zaretskii
2023-06-09 20:04 ` Gregory Heytings
2023-06-10 5:59 ` Eli Zaretskii
2023-06-10 6:39 ` Gregory Heytings
2023-06-10 6:45 ` Eli Zaretskii
2023-06-10 8:45 ` Gregory Heytings
2023-06-10 6:52 ` martin rudalics
2023-06-10 8:28 ` Eli Zaretskii
2023-06-10 14:51 ` martin rudalics
2023-06-10 17:09 ` Eli Zaretskii
2023-06-11 8:10 ` martin rudalics
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=d1a5f5d9-b91a-c95a-b66c-44112ab388f4@gmx.at \
--to=rudalics@gmx.at \
--cc=63967@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=al@petrofsky.org \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).