From: Eli Zaretskii <eliz@gnu.org>
To: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>
Cc: tkk@misasa.okayama-u.ac.jp, emacs-devel@gnu.org
Subject: Re: line-pixel-height beyond eol
Date: Tue, 17 Oct 2017 19:37:25 +0300 [thread overview]
Message-ID: <831sm1g27u.fsf@gnu.org> (raw)
In-Reply-To: <20171017.092955.1163083656126984401.tkk@misasa.okayama-u.ac.jp> (message from Tak Kunihiro on Tue, 17 Oct 2017 09:29:55 +0900 (JST))
> Date: Tue, 17 Oct 2017 09:29:55 +0900 (JST)
> Cc: emacs-devel@gnu.org, tkk@misasa.okayama-u.ac.jp
> From: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>
>
> (a) emacs 26.0.90
> (b) emacs -Q
> (c) M-x eww www.gnu.org
> (d) C-u C-u C-n (to move to GNU picture)
> (e) M-: (set-window-hscroll nil 100)
> (f) C-l C-l (locate GNU-picture line to the top of the screen)
>
> Let me define `physical height' as length of height of a line, that is measured by physical scale.
> After operation (e), physical height of GNU-picture line is (frame-char-height) such as 20 pixel.
> After operation (f), physical height of GNU-picture line is tall such like 144 pixel.
>
> The same GNU-picture line is shown with different physical height
> depending on where the line is located. Is this expected behavior?
Yes, this is the intended behavior of the display engine.
prev parent reply other threads:[~2017-10-17 16:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 10:12 line-pixel-height beyond eol Tak Kunihiro
2017-09-12 15:13 ` Eli Zaretskii
2017-09-13 0:24 ` Tak Kunihiro
2017-09-13 15:28 ` Eli Zaretskii
2017-09-13 23:14 ` Tak Kunihiro
2017-09-14 17:53 ` Eli Zaretskii
2017-09-15 1:39 ` Tak Kunihiro
2017-09-15 17:35 ` Eli Zaretskii
2017-09-23 12:57 ` Tak Kunihiro
2017-09-23 13:16 ` Eli Zaretskii
2017-10-05 9:50 ` Tak Kunihiro
2017-10-09 13:31 ` Eli Zaretskii
2017-10-16 5:13 ` Tak Kunihiro
2017-10-16 16:16 ` Eli Zaretskii
2017-10-17 0:29 ` Tak Kunihiro
2017-10-17 16:37 ` Eli Zaretskii [this message]
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=831sm1g27u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=tkk@misasa.okayama-u.ac.jp \
/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).