unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: 50178-done@debbugs.gnu.org
Subject: bug#50178: 28.0.50; Size of echo area does not account for line-spacing
Date: Thu, 26 Aug 2021 09:54:51 +0200	[thread overview]
Message-ID: <2acd8c0f-443e-3521-20a4-05369193b899@gmx.at> (raw)
In-Reply-To: <87k0k9er3w.fsf@telefonica.net>

 > On true pixel-oriented systems there are APIs for querying the display
 > engine about several metrics. Then you can place the text at certain
 > pixel coordinates. Emacs, however, is a Frankenstein system, that uses
 > pixels (on graphic frames) but the text positioning depends on previous
 > text, i.e. for vertical positioning it is a line-based, not pixel-based,
 > system. Therefore, when you just need to output some lines, you must
 > deal with pixels, translate back to lines and, to add insult to injury,
 > resort to post-facto information.

Users think in terms of lines and columns.  True pixel-oriented systems
are not convenient for editing.  A few days ago I spent a couple of
hours to remove one single line from a pdf-document using LibreOffice.
I almost succeeded.

 > As useful as it would be an API that returns how many lines fit on a
 > given window. Or, on this case, max-mini-window-height being a true
 > indication of the capacity of the mini window on terms of the current
 > display settings, which is what the users want 99.9% of the time.

Did you try with `redisplay-adhoc-scroll-in-resize-mini-windows' as
Gregory proposed?

martin





  parent reply	other threads:[~2021-08-26  7:54 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
2021-08-25 20:10                             ` Óscar Fuentes
2021-08-26  6:34                               ` Eli Zaretskii
2021-08-26  7:54                       ` martin rudalics [this message]
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=2acd8c0f-443e-3521-20a4-05369193b899@gmx.at \
    --to=rudalics@gmx.at \
    --cc=50178-done@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).