From: Eli Zaretskii <eliz@gnu.org>
To: <miha@kamnitnik.top>
Cc: larsi@gnus.org, 55403@debbugs.gnu.org
Subject: bug#55403: 29.0.50; quit-window may select an inactive minibuffer window
Date: Sat, 14 May 2022 10:07:24 +0300 [thread overview]
Message-ID: <83r14wlhhv.fsf@gnu.org> (raw)
In-Reply-To: <8735hchaz6.fsf@miha-pc> (bug-gnu-emacs@gnu.org)
> Cc: 55403@debbugs.gnu.org
> Date: Sat, 14 May 2022 08:41:49 +0200
> From: miha--- via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> >> emacs -q:
> >>
> >> (setq read-minibuffer-restore-windows nil)
> >> M-x, to open a minibuffer
> >> C-h b, to display a help buffer from this minibuffer
> >> C-g, to quit the minibuffer
> >> C-x C-o, to select the window showing the help buffer
> >> q, (quit-window) will select the inactive minibuffer window
> >
> > I'm unable to reproduce this on the current trunk.
>
> It's not entirely obvious that an inactive minibuffer window is selected
> because the point is not immediately visible. Perhaps try to press C-n
> at the end of the recipe, which makes the point visible, and see that
> the mini-window is indeed selected.
I can reproduce in today's master, but "C-x C-o" should be "C-x o",
right?
next prev parent reply other threads:[~2022-05-14 7:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 21:36 bug#55403: 29.0.50; quit-window may select an inactive minibuffer window miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-14 2:46 ` Lars Ingebrigtsen
2022-05-14 6:41 ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-14 7:07 ` Eli Zaretskii [this message]
2022-05-14 7:48 ` martin rudalics
2022-05-14 7:55 ` martin rudalics
2022-05-14 9:08 ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-18 9:15 ` 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=83r14wlhhv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55403@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=miha@kamnitnik.top \
/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).