unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Gregory Heytings <gregory@heytings.org>
Cc: 50178-done@debbugs.gnu.org
Subject: bug#50178: 28.0.50; Size of echo area does not account for line-spacing
Date: Wed, 25 Aug 2021 19:09:14 +0200	[thread overview]
Message-ID: <87fsuxe9j9.fsf@telefonica.net> (raw)
In-Reply-To: <ba9bdda48fa571e04237@heytings.org> (Gregory Heytings's message of "Wed, 25 Aug 2021 14:33:35 +0000")

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. It's also true that those
systems work on pixels (or some other suitable, fine-grained unit) all
the way, they do not reveal themselves as TTY-oriented systems when the
user says "ok, then put this right here." The impossibility you mention
is a limitation of Emacs.

So going back to Emacs, the doctstring of max-mini-window-height is

"...
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.) Maybe because the relevant use case was to support resizing
the mini window on a way that guarantees that certain number of lines
(rendered on the default font) will fit on it?





  reply	other threads:[~2021-08-25 17:09 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 [this message]
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=87fsuxe9j9.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --cc=50178-done@debbugs.gnu.org \
    --cc=gregory@heytings.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).