From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: 50178@debbugs.gnu.org
Subject: bug#50178: 28.0.50; Size of echo area does not account for line-spacing
Date: Tue, 24 Aug 2021 19:20:23 +0300 [thread overview]
Message-ID: <837dgax1a0.fsf@gnu.org> (raw)
In-Reply-To: <87a6l7ezks.fsf@telefonica.net> (message from Óscar Fuentes on Tue, 24 Aug 2021 15:34:27 +0200)
> From: Óscar Fuentes <ofv@wanadoo.es>
> Cc: 50178@debbugs.gnu.org
> Date: Tue, 24 Aug 2021 15:34:27 +0200
>
> There are some packages that works displaying a certain number of lines
> on the echo area (ido-grid-mode, for instance.) They set
> max-mini-window-height to an integer and expect that Emacs will take
> care of resizing the echo area accordingly, if possible. If the
> resulting echo area is not tall enough, there is a problem.
>
> IMO max-mini-window-height, when set to an integer, should mean "I want
> this many lines", as it does when line-spacing is nil.
But that's not the exact meaning of the value of that variable. The
doc string says:
If an integer, it specifies the maximum height in units of the
mini-window frame’s default font’s height. ^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
It is measured in units of the canonical character height, and that
doesn't take the line-spacing into account, like it doesn't take into
account faces that change the font or the size of the characters.
IOW, the value means "this many lines", but assuming that the line's
height is the one you get with the frame's default font.
You get the same in a window other than mini-window: if you set
line-spacing, chances are the last screen line will be only partially
visible. Why should the mini-window be different? it's just another
window.
So once again, I see no problem here, it's just Emacs display working
as designed in the face of variable-size fonts and window heights that
aren't necessarily an integral multiple of the font/line height.
next prev parent reply other threads:[~2021-08-24 16:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 2:08 bug#50178: 28.0.50; Size of echo area does not account for line-spacing Óscar Fuentes
2021-08-24 11:58 ` Eli Zaretskii
2021-08-24 13:34 ` Óscar Fuentes
2021-08-24 16:20 ` Eli Zaretskii [this message]
2021-08-24 17:44 ` Óscar Fuentes
2021-08-24 18:13 ` Eli Zaretskii
2021-08-24 18:38 ` Óscar Fuentes
2021-08-24 18:49 ` Eli Zaretskii
2021-08-24 19:36 ` Óscar Fuentes
2021-08-25 2:24 ` Eli Zaretskii
2021-08-25 7:49 ` martin rudalics
2021-08-25 9:01 ` Gregory Heytings
2021-08-25 10:49 ` Óscar Fuentes
2021-08-25 12:15 ` Eli Zaretskii
2021-08-25 14:33 ` Gregory Heytings
2021-08-25 17:09 ` Óscar Fuentes
2021-08-25 17:57 ` Eli Zaretskii
2021-08-25 20:10 ` Óscar Fuentes
2021-08-26 6:34 ` Eli Zaretskii
2021-08-26 7:54 ` martin rudalics
2021-08-26 8:12 ` 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=837dgax1a0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50178@debbugs.gnu.org \
--cc=ofv@wanadoo.es \
/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).