From: Eli Zaretskii <eliz@gnu.org>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: gregory@heytings.org, 50178@debbugs.gnu.org
Subject: bug#50178: 28.0.50; Size of echo area does not account for line-spacing
Date: Wed, 25 Aug 2021 20:57:02 +0300 [thread overview]
Message-ID: <83zgt5tnkh.fsf@gnu.org> (raw)
In-Reply-To: <87fsuxe9j9.fsf@telefonica.net> (message from Óscar Fuentes on Wed, 25 Aug 2021 19:09:14 +0200)
> From: Óscar Fuentes <ofv@wanadoo.es>
> Date: Wed, 25 Aug 2021 19:09:14 +0200
> Cc: 50178-done@debbugs.gnu.org
>
> Gregory Heytings <gregory@heytings.org> writes:
>
> > Try emacs -Q, C-h h to see why it is impossible to have "an API that
> > returns how many lines fit on a given window".
>
> Any graphics environment worth its salt has methods for measuring
> whatever object without actually rendering it.
So does Emacs: that's what window-text-pixel-size does.
> If an integer, it specifies the maximum height in units of the
> mini-window frame’s default font’s height.
> "
>
> Why that was implemented that way? (instead of using pixels, for
> instance.)
Because in most cases it's more useful: it approximates the actual
number of lines quite well.
next prev parent reply other threads:[~2021-08-25 17:57 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
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 [this message]
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=83zgt5tnkh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=50178@debbugs.gnu.org \
--cc=gregory@heytings.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).