unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuri Khan <yuri.v.khan@gmail.com>
To: Jim Porter <jporterbugs@gmail.com>
Cc: Stefan Kangas <stefankangas@gmail.com>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: Increase default `line-spacing' to 0.05, 0.10 or 0.15 [proposal]
Date: Fri, 7 May 2021 13:03:01 +0700	[thread overview]
Message-ID: <CAP_d_8UO=NcBEpS63=iiA8ynhhwyE1sniCmV5oXJxaApjOaaCA@mail.gmail.com> (raw)
In-Reply-To: <CANh=_JF0wj6sPOE-TSLca-T_sfRL1ez3M-BnooKzRAgW=+1YHw@mail.gmail.com>

On Fri, 7 May 2021 at 06:18, Jim Porter <jporterbugs@gmail.com> wrote:

> Yeah, Emacs' reliance on using characters to draw lines would probably
> lead me to set `line-spacing' back to 0 if this were changed. It would
> be interesting if Emacs were able to handle these issues, e.g. by
> adding some special handling when it sees box-drawing characters, but
> that would probably be a lot of work.

The Kitty terminal emulator has a configuration option for increasing
the line spacing. To mitigate the box drawing characters issue, it
implements rendering them in code. (This also helps when a font does
not have glyphs for box drawing characters.)

https://github.com/kovidgoyal/kitty/blob/master/kitty/fonts/box_drawing.py

The high-level architecture is:

* Kitty keeps a texture that caches glyphs of fonts being used.
* For most characters, that texture is populated by rendering them
with the appropriate font (chosen by the user in configuration or by
font fallback).
* For box drawing characters, there is a mapping from character code
to a list of rendering functions, and they are called to render into
the texture.

Of course, Kitty has it easier because it only has to deal with a
single font size, and I’m not sure if it does complex script shaping
correctly.



  reply	other threads:[~2021-05-07  6:03 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 [this message]
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='CAP_d_8UO=NcBEpS63=iiA8ynhhwyE1sniCmV5oXJxaApjOaaCA@mail.gmail.com' \
    --to=yuri.v.khan@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=jporterbugs@gmail.com \
    --cc=stefankangas@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).