From: martin rudalics <rudalics@gmx.at>
To: "Iris García" <iris.garcia.desebastian@gmail.com>, 48674@debbugs.gnu.org
Cc: Alan Mackenzie <acm@muc.de>
Subject: bug#48674: Frames and minibuffer bug
Date: Wed, 26 May 2021 19:45:11 +0200 [thread overview]
Message-ID: <1911d1b0-ed9f-7359-b28c-fbaef27df8f3@gmx.at> (raw)
In-Reply-To: <CALBoQjqKBLr4u_sZttgjd53gniqrn0=CbHnTquq9JnUAbKyWLw@mail.gmail.com>
merge 48674 48675
quit
Thanks for the report. I've just tried to merge this with the following
one.
> 4. M-x (The bug appears, it is not possible to write in the minibuffer)
The crucial part is the
(dolist (frame (frame-list))
(with-selected-frame frame
setting the cursor is not necessary to reproduce it. Since the bug does
not appear with Emacs 27, this could be due to Alan's minibuffer window
changes.
> Note:
> As soon as the new frame is destroyed, it is possible again to write in the
> minibuffer.
Right but as soon as I make another frame and type M-x I get
completing-read-default: Command attempted to use minibuffer while in minibuffer
so I'm at the same time in the active minibuffer and a normal buffer.
martin
next prev parent reply other threads:[~2021-05-26 17:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 11:23 bug#48674: Frames and minibuffer bug Iris García
2021-05-26 17:45 ` martin rudalics [this message]
2021-05-27 10:34 ` Alan Mackenzie
2021-05-27 16:33 ` martin rudalics
2021-05-27 19:56 ` Iris García
2021-05-28 8:25 ` martin rudalics
2021-05-28 9:34 ` Iris García
2021-05-28 9:51 ` martin rudalics
2021-05-31 16:36 ` Alan Mackenzie
2021-06-01 11:29 ` Iris García
2021-05-27 20:01 ` Alan Mackenzie
2021-05-28 8:26 ` martin rudalics
2021-05-28 17:15 ` Alan Mackenzie
2021-05-28 20:14 ` Alan Mackenzie
2021-05-29 9:20 ` martin rudalics
2021-05-29 13:10 ` Alan Mackenzie
2021-05-29 15:12 ` martin rudalics
2021-05-29 15:24 ` Eli Zaretskii
2021-05-29 17:00 ` Alan Mackenzie
2021-05-30 13:58 ` Alan Mackenzie
2021-05-31 7:55 ` 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=1911d1b0-ed9f-7359-b28c-fbaef27df8f3@gmx.at \
--to=rudalics@gmx.at \
--cc=48674@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=iris.garcia.desebastian@gmail.com \
/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).