From: Robert Dallas Gray <mail@robertdallasgray.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 15886@debbugs.gnu.org
Subject: bug#15886: 24.3.50; Incorrect window-text-height with non-zero line-spacing
Date: Wed, 13 Nov 2013 20:36:14 +0000 [thread overview]
Message-ID: <4D2C9983-9E63-44F6-83A6-3D306B9EC79C@robertdallasgray.com> (raw)
In-Reply-To: <83a9h811r7.fsf@gnu.org>
On 13 Nov 2013, at 20:32, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Robert Dallas Gray <mail@robertdallasgray.com>
>> Date: Wed, 13 Nov 2013 19:23:19 +0000
>>
>> On a graphical display, when `line-spacing' is non-zero,
>> `window-text-height' reports an incorrect number; equally,
>> `set-window-text-height' can't be used properly. This impacts on
>> libraries which use `set-window-text-height' e.g. to attempt to size a
>> window accurately.
>
> Those libraries should use 'window-screen-lines' instead.
>
> I think 'window-text-height' should continue doing what it does, as
> many packages, and Emacs itself, depend on its current behavior.
OK, but is there a parallel setter method, or some way to set the height of a window in pixels, so that a window could be correctly sized taking into account line-spacing?
Incidentally, the particular library that raised this issue for me was grizzl (https://github.com/d11wtq/grizzl).
next prev parent reply other threads:[~2013-11-13 20:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 19:23 bug#15886: 24.3.50; Incorrect window-text-height with non-zero line-spacing Robert Dallas Gray
2013-11-13 20:32 ` Eli Zaretskii
2013-11-13 20:36 ` Robert Dallas Gray [this message]
2013-11-13 20:44 ` Eli Zaretskii
2013-11-13 20:55 ` Robert Dallas Gray
2013-11-13 21:16 ` Eli Zaretskii
2013-11-13 21:27 ` Robert Dallas Gray
2013-11-14 3:44 ` Eli Zaretskii
[not found] ` <CAOTeZj9_+4P1yUFpObLV+acFxpZyHsPG0uW2HyV=34zOQUT88Q@mail.gmail.com>
2013-11-14 18:07 ` Eli Zaretskii
2013-11-14 19:24 ` Robert Dallas Gray
2020-10-28 7:39 ` Stefan Kangas
2013-11-14 7:38 ` martin rudalics
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=4D2C9983-9E63-44F6-83A6-3D306B9EC79C@robertdallasgray.com \
--to=mail@robertdallasgray.com \
--cc=15886@debbugs.gnu.org \
--cc=eliz@gnu.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).