unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: daniele@grinta.net, emacs-devel@gnu.org
Subject: Re: Increase default `line-spacing' to 0.05, 0.10 or 0.15 [proposal]
Date: Thu, 06 May 2021 20:57:38 +0300	[thread overview]
Message-ID: <83pmy3d9t9.fsf@gnu.org> (raw)
In-Reply-To: <83sg2zda04.fsf@gnu.org> (message from Eli Zaretskii on Thu, 06 May 2021 20:53:31 +0300)

> Date: Thu, 06 May 2021 20:53:31 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: emacs-devel@gnu.org
> 
> > From: Daniele Nicolodi <daniele@grinta.net>
> > Date: Thu, 6 May 2021 18:57:46 +0200
> > 
> > I didn't look at the code, but I don't think this is true: on my Emacs,
> > lines containing only "." or containing only "l" have exactly the same
> > height, as I would expect.
> 
> You assume that the metrics of these two glyphs are different in
> monospaced fonts?
> 
> > Also, lines containing only a new line character (thus no printable
> > characters) still have the same height as lines with content, as
> > expected.
> 
> Newline leaves no glyphs on display, so their metrics cannot be
> calculated from the font.
> 
> > Are you sure Emacs does not consider the maximum ascent and descent of
> > each _font_ contained in a line and not of each _glyph_?
> 
> Why do you think there's a difference?

And in any case, line-spacing of nil adds nothing to the metrics, no
matter where they come from.  IOW, Emacs doesn't determine this; the
font does.



  reply	other threads:[~2021-05-06 17:57 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-04 15:57 Increase default `line-spacing' to 0.05, 0.10 or 0.15 [proposal] Stefan Kangas
2021-05-04 16:12 ` Óscar Fuentes
2021-05-04 16:59   ` Jim Porter
2021-05-05  7:08     ` Augusto Stoffel
2021-05-05  8:51       ` Daniel Mendler
2021-05-05 19:47       ` Stefan Kangas
2021-05-06  9:26         ` Augusto Stoffel
2021-05-06 10:10           ` Eli Zaretskii
2021-05-06 11:47             ` Augusto Stoffel
2021-05-06 11:57               ` Eli Zaretskii
2021-05-06 12:27                 ` Augusto Stoffel
2021-05-06 15:21                   ` Eli Zaretskii
2021-05-06 15:46                     ` Augusto Stoffel
2021-05-06 16:16                       ` Eli Zaretskii
2021-05-06 12:30                 ` Gregory Heytings
2021-05-06 15:22                   ` Eli Zaretskii
2021-05-06 16:21                     ` Gregory Heytings
2021-05-06 16:29                       ` Eli Zaretskii
2021-05-06 16:57                         ` Daniele Nicolodi
2021-05-06 17:53                           ` Eli Zaretskii
2021-05-06 17:57                             ` Eli Zaretskii [this message]
2021-05-06 20:24                             ` Daniele Nicolodi
2021-05-06 17:01                         ` Gregory Heytings
2021-05-06 17:34                           ` Eli Zaretskii
2021-05-06 18:15                             ` Gregory Heytings
2021-05-06 20:22           ` Stefan Kangas
2021-05-06 20:21     ` Stefan Kangas
2021-05-06 23:17       ` Jim Porter
2021-05-07  6:03         ` Yuri Khan
2021-05-07  4:05       ` Eli Zaretskii
2021-05-04 16:18 ` Eli Zaretskii
2021-05-04 21:29   ` Stefan Kangas
2021-05-05  2:28     ` Eli Zaretskii
2021-05-05  5:14 ` Richard Stallman
2021-05-05 19:16   ` Stefan Kangas
2021-05-06 20:21     ` Stefan Kangas
2021-05-07  4:03       ` Eli Zaretskii
2021-05-07 18:43         ` Stefan Kangas
2021-05-08  6:19           ` Eli Zaretskii
2021-05-08  7:51             ` Daniele Nicolodi
2021-05-08  8:06               ` Eli Zaretskii
2021-05-08  9:40                 ` Daniele Nicolodi
2021-05-05 12:18 ` Daniele Nicolodi
2021-05-05 19:17   ` Stefan Kangas

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=83pmy3d9t9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=daniele@grinta.net \
    --cc=emacs-devel@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).