From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: Proposed removal of struct frame->select_mini_window_flag.
Date: Wed, 18 May 2022 19:19:49 +0300 [thread overview]
Message-ID: <83pmkaertm.fsf@gnu.org> (raw)
In-Reply-To: <YoUXLNsEpXhHyRoA@ACM> (message from Alan Mackenzie on Wed, 18 May 2022 15:56:28 +0000)
> Date: Wed, 18 May 2022 15:56:28 +0000
> From: Alan Mackenzie <acm@muc.de>
>
> I came across struct frame->select_mini_window_flag while looking at bug
> #55414.
>
> More accurately, my attention was diverted for over an hour, trying to
> work out how this boolean could be maintained in a consistent state,
> given that it gets splatted to false every time Fselect_window gets
> called.
>
> Then it dawned on me that the variable has no function - if the
> mini-window is the selected window, this is fully represented by struct
> frame->selected_window's value.
>
> So, I propose to remove this variable and all its "uses". Does anybody
> object?
I don't think I follow. Did you see this fragment in frame.c:
sf->select_mini_window_flag = MINI_WINDOW_P (XWINDOW (sf->selected_window));
selected_frame = frame;
move_minibuffers_onto_frame (sf, for_deletion);
if (f->select_mini_window_flag
&& !NILP (Fminibufferp (XWINDOW (f->minibuffer_window)->contents, Qt)))
f->selected_window = f->minibuffer_window;
How will this logic work without that flag?
next prev parent reply other threads:[~2022-05-18 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 15:56 Proposed removal of struct frame->select_mini_window_flag Alan Mackenzie
2022-05-18 16:19 ` Eli Zaretskii [this message]
2022-05-18 17:03 ` Alan Mackenzie
2022-05-18 17:16 ` Eli Zaretskii
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=83pmkaertm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.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).