From: Eli Zaretskii <eliz@gnu.org>
To: Markus Triska <triska@metalevel.at>
Cc: 67715@debbugs.gnu.org
Subject: bug#67715: 28.2; Minibuffer content is sometimes unexpectedly partially hidden
Date: Fri, 08 Dec 2023 22:35:20 +0200 [thread overview]
Message-ID: <838r64zb3r.fsf@gnu.org> (raw)
In-Reply-To: <87plzg5xff.fsf@metalevel.at> (message from Markus Triska on Fri, 08 Dec 2023 20:03:32 +0100)
tags 67715 wontfix
thanks
> From: Markus Triska <triska@metalevel.at>
> Date: Fri, 08 Dec 2023 20:03:32 +0100
>
> To reproduce the issue, please start Emacs with:
>
> $ emacs -Q
>
> Then put the following form in the *scratch* buffer and evaluate it with
> C-x e:
>
> (let ((f (selected-frame)))
> (with-selected-frame (make-frame)
> (switch-to-buffer (get-buffer-create "other")))
> (select-frame-set-input-focus f)
> (let ((win (get-buffer-window "other" t)))
> (when win
> (with-selected-window win
> (recenter 0)))
> (with-selected-window (minibuffer-window)
> (unwind-protect
> (progn
> (setq-local face-remapping-alist `((default :height 2.0)))
> (insert "hello")
> (read-key))
> (erase-buffer)))))
>
> "hello" is shown in the minibuffer, but it is partially hidden.
>
> For comparison, in Emacs 28.1, "hello" is fully visible.
>
> Can you reproduce this issue, and if possible, could you please restore
> the behaviour of Emacs 28.1 and earlier versions for this example?
The change which caused this cannot be reverted, since it will
reintroduce a worse bug (bug#24285).
Why did you expect the mini-window to resize in this case? Emacs
doesn't resize a window just because you enlarge a font shown in that
window, which makes some of the text invisible because it not longer
fits into the window's dimensions. The automatic resizing of the
mini-window is reserved for its uses to prompt the user and to show
echo-area messages, whereas your snippet just uses it as a normal
window showing some buffer.
So I don't think we will change this behavior, and you will need to
find another way of ensuring the enlarged text is visible, in your
real-life use case.
Sorry.
next prev parent reply other threads:[~2023-12-08 20:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 19:03 bug#67715: 28.2; Minibuffer content is sometimes unexpectedly partially hidden Markus Triska
2023-12-08 20:35 ` Eli Zaretskii [this message]
2023-12-09 7:04 ` Markus Triska
2023-12-09 7:59 ` Eli Zaretskii
2023-12-09 9:04 ` Markus Triska
2023-12-09 11:18 ` Eli Zaretskii
2023-12-10 8:12 ` Markus Triska
2023-12-10 9:27 ` Eli Zaretskii
2023-12-11 17:12 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 7:43 ` Markus Triska
2024-01-14 8:49 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-09 17:02 ` Eli Zaretskii
2023-12-09 20:09 ` Markus Triska
2023-12-09 20:20 ` Eli Zaretskii
2023-12-09 21:11 ` Markus Triska
2023-12-10 5:44 ` Eli Zaretskii
2023-12-10 17:59 ` Markus Triska
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=838r64zb3r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=67715@debbugs.gnu.org \
--cc=triska@metalevel.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 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).