From: martin rudalics via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, rahguzar@zohomail.eu, r.diaz@uam.es,
rdiaz02@gmail.com, 70038@debbugs.gnu.org
Subject: bug#70038: 29.3.50; Shift up/down in buffer with images on M-x other-window with some fonts
Date: Sun, 7 Apr 2024 10:24:29 +0200 [thread overview]
Message-ID: <3ee13fbd-2ba0-4fca-b5ed-b61f1d8dc527@gmx.at> (raw)
In-Reply-To: <867cha37of.fsf@gnu.org>
> There's one more aspect of this that bothers me: when we resize the
> mini-window, we set the frame's frozen_window_starts flag, but we seem
> to never reset it.
>
> Martin, can you help out here? I don't see shrink_mini_window being
> called with non-zero DELTA anywhere, including when the mini-window is
> exited and is resized to its normal one-line height. Instead, this
> resizing is performed by restore_window_configuration, called from
> read_minibuf, but I don't see FRAME_WINDOWS_FROZEN being reset
> anywhere there. I don't think it's correct for us to leave the
> frame's frozen_window_starts flag set forever once it was raised,
Just for the record: Here I once used a version of shrink_mini_window
that went as
/** Shrink mini-window W to its minimum height. */
void
shrink_mini_window (struct window *w)
{
/* Just attempt to shrink it to zero, grow_mini_window makes sure it
does not get to small. */
FRAME_WINDOWS_FROZEN (WINDOW_XFRAME (w)) = false;
grow_mini_window (w, -WINDOW_PIXEL_HEIGHT (w));
}
where grow_mini_window took care of the rest. But I don't call
shrink_mini_window any more and so the flag remains stuck here as well.
> so I
> guess we should do something in minibuffer_unwind to reset that flag?
Would that be sufficient? Don't we freeze also when resizing the echo
area?
martin
next prev parent reply other threads:[~2024-04-07 8:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 20:25 bug#70038: 29.3.50; Shift up/down in buffer with images on M-x other-window with some fonts Ramon Diaz-Uriarte
2024-03-28 5:58 ` Eli Zaretskii
2024-03-28 7:52 ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-28 8:36 ` Eli Zaretskii
2024-03-28 16:12 ` Ramon Diaz-Uriarte
2024-03-28 16:59 ` Ramon Diaz-Uriarte
2024-03-28 17:24 ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-28 19:50 ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-31 18:43 ` Ramon Diaz-Uriarte
2024-04-06 12:33 ` Eli Zaretskii
2024-04-06 14:08 ` Eli Zaretskii
2024-04-06 14:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-07 8:24 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-04-07 9:13 ` Eli Zaretskii
2024-04-07 10:12 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-07 11:28 ` Eli Zaretskii
2024-04-08 9:07 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-13 10:10 ` Eli Zaretskii
2024-04-14 8:31 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-14 9:28 ` Eli Zaretskii
2024-04-15 9:23 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-15 13:54 ` Eli Zaretskii
2024-04-17 8:02 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-17 12:58 ` Eli Zaretskii
2024-04-28 8:51 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-28 9:15 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-29 9:47 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-29 12:51 ` Eli Zaretskii
2024-04-11 13:56 ` Ramon Diaz-Uriarte
2024-04-11 15:36 ` Eli Zaretskii
2024-04-12 16:43 ` Ramon Diaz-Uriarte
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ee13fbd-2ba0-4fca-b5ed-b61f1d8dc527@gmx.at \
--to=bug-gnu-emacs@gnu.org \
--cc=70038@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=r.diaz@uam.es \
--cc=rahguzar@zohomail.eu \
--cc=rdiaz02@gmail.com \
--cc=rudalics@gmx.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.