From: Eli Zaretskii <eliz@gnu.org>
To: rudalics@gmx.at
Cc: yuan.mei.list@gmail.com, emacs-devel@gnu.org
Subject: Re: Redisplay issue
Date: Fri, 04 Dec 2015 13:12:50 +0200 [thread overview]
Message-ID: <83r3j2h3gt.fsf@gnu.org> (raw)
In-Reply-To: <83twnyh3zo.fsf@gnu.org>
> Date: Fri, 04 Dec 2015 13:01:31 +0200
> Sun-Java-System-SMTP-Warning: Lines longer than SMTP allows found and
> truncated.
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: yuan.mei.list@gmail.com, emacs-devel@gnu.org
>
> > Date: Fri, 04 Dec 2015 11:21:57 +0100
> > From: martin rudalics <rudalics@gmx.at>
> > CC: yuan.mei.list@gmail.com, emacs-devel@gnu.org
> >
> > >> So it's the Cairo font backend. 59 text lines plus one menu bar line
> > >> give the 60 pixels difference.
> > >
> > > I don't understand how can it do that with the same size of the same
> > > font. Some bug in ftcrfont.c, perhaps?
> >
> > Do what?
>
> Compute a different frame-char-height for the same font and font size.
In case this is not clear: xterm.c computes FRAME_LINE_HEIGHT as
follows:
get_font_ascent_descent (font, &font_ascent, &font_descent);
FRAME_LINE_HEIGHT (f) = font_ascent + font_descent;
So the result comes from 2 values determined only by the frame's
default font. These values are returned by the font back-end that
accesses the font, so only the font back-end could have affected them
for the same font.
next prev parent reply other threads:[~2015-12-04 11:12 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 22:31 Redisplay issue Yuan MEI
2015-11-28 8:06 ` Eli Zaretskii
2015-11-28 8:27 ` Yuan MEI
2015-11-28 9:44 ` Eli Zaretskii
2015-11-28 20:19 ` Yuan MEI
2015-11-28 20:49 ` Eli Zaretskii
2015-11-29 2:54 ` Yuan MEI
2015-11-29 15:42 ` Eli Zaretskii
2015-11-29 23:35 ` Yuan MEI
2015-11-30 16:16 ` Eli Zaretskii
2015-12-01 4:51 ` Yuan MEI
2015-12-01 16:01 ` Eli Zaretskii
2015-12-02 4:35 ` Yuan MEI
2015-12-02 13:57 ` Eli Zaretskii
2015-12-03 4:55 ` Yuan MEI
2015-12-03 7:47 ` Eli Zaretskii
2015-12-03 8:09 ` Yuan MEI
2015-12-03 10:23 ` Eli Zaretskii
2015-12-03 18:16 ` martin rudalics
2015-12-03 21:23 ` Yuan MEI
2015-12-04 8:08 ` martin rudalics
2015-12-04 8:30 ` Yuan MEI
2015-12-04 8:48 ` martin rudalics
2015-12-04 8:54 ` Yuan MEI
2015-12-04 8:56 ` martin rudalics
2015-12-04 9:00 ` Yuan MEI
2015-12-04 9:05 ` martin rudalics
2015-12-04 9:47 ` Eli Zaretskii
2015-12-04 10:21 ` martin rudalics
2015-12-04 11:01 ` Eli Zaretskii
2015-12-04 11:12 ` Eli Zaretskii [this message]
2015-12-05 0:25 ` YAMAMOTO Mitsuharu
2015-12-05 9:17 ` Eli Zaretskii
2015-12-06 0:49 ` Yuan MEI
2015-12-07 3:33 ` YAMAMOTO Mitsuharu
2015-12-07 17:19 ` Eli Zaretskii
2015-12-08 4:03 ` YAMAMOTO Mitsuharu
2015-12-11 8:48 ` Eli Zaretskii
2015-11-28 21:44 ` joakim
2015-11-29 0:14 ` Yuan MEI
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=83r3j2h3gt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
--cc=yuan.mei.list@gmail.com \
/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).