unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniele Nicolodi <daniele@grinta.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Increase default `line-spacing' to 0.05, 0.10 or 0.15 [proposal]
Date: Sat, 8 May 2021 11:40:55 +0200	[thread overview]
Message-ID: <c1e2f467-d4ec-e02e-469a-1282367037ed@grinta.net> (raw)
In-Reply-To: <83k0o9abub.fsf@gnu.org>

On 08/05/2021 10:06, Eli Zaretskii wrote:
>> From: Daniele Nicolodi <daniele@grinta.net>
>> Date: Sat, 8 May 2021 09:51:12 +0200
>>
>> On 08/05/2021 08:19, Eli Zaretskii wrote:
>>> On the implementation side, I'm not sure I understand how do you
>>> intend to implement these values: 110% of what?  Line spacing is
>>> eventually a pixel value; you can, of course, compute it in percents
>>> of the font size, but then the nominal spacing will not have the 100%
>>> or 1.0 value, right?  So how do you intend to convert the value in the
>>> menu into the actual line-spacing value?
>>
>> The documentation for the line-spacing variable says:
>>
>> Documentation:
>> Additional space to put between lines when displaying a buffer. The
>> space is measured in pixels, and put below lines on graphic displays,
>> see ‘display-graphic-p’.
>> If value is a floating point number, it specifies the spacing relative
>> to the default frame line height.  A value of nil means add no extra space.
>>
>> I think the values in the menu would simply be divided by 100.
> 
> So you are saying that 100% would mean line-spacing equal to the
> default frame line height?  That would mean the line height that is
> twice as high as the default, so (a) 100% is hardly a good
> description, and (b) how do you provide an option to get back to the
> default value?
> 
> IOW, the default is that we add zero spacing, and that makes percent
> notation not trivially convertible.  As the doc string says, this is
> _additional_ space.

I have no idea what the author of the patch had in mind, I wa trying to
offer an interpretation. But, indeed simply dividing by 100 does not
work. Dividinng by 100 and subtracting 1 results in a number in the
correct range. However, I agree that "line spacing 100%" is a very bad
description of what the setting does.

Either the setting is called line "line height" with suggested values an
a neighborhood of 100%, or "line spacing" with values in a neighborhood
of 0% (ie 0%, 5%, 10% or so).

Cheers,
Dan




  reply	other threads:[~2021-05-08  9:40 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
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 [this message]
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=c1e2f467-d4ec-e02e-469a-1282367037ed@grinta.net \
    --to=daniele@grinta.net \
    --cc=eliz@gnu.org \
    --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).