all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tim Ruffing <crypto@timruffing.de>
Cc: luangruo@yahoo.com, 67810@debbugs.gnu.org
Subject: bug#67810: 29.1; fonts use synthetic bold on Linux / pgtk
Date: Thu, 14 Dec 2023 12:04:04 +0200	[thread overview]
Message-ID: <83le9xqewb.fsf@gnu.org> (raw)
In-Reply-To: <d0bfcc83868f6c4acb212094fdceb62a0dc0def8.camel@timruffing.de> (message from Tim Ruffing on Thu, 14 Dec 2023 10:54:45 +0100)

> From: Tim Ruffing <crypto@timruffing.de>
> Cc: 67810@debbugs.gnu.org
> Date: Thu, 14 Dec 2023 10:54:45 +0100
> 
> So I think whether overstriking is performed should ideally be a
> property of the font. Having some variable similar to the existing 
> vertical-centering-font-regexp would be great, and this would also make
> it possible to turn off overstriking globally.
> 
> Do you think that's a reasonable thing to add?

What are the chances of someone wanting to disable this feature only
for some fonts?  If we want to allow disabling it globally, it should
be a simple matter of adding a boolean variable exposed to Lisp, and
then performing this only when the variable doesn't inhibit that.

Adding a font property, or a regexp for matching fonts which are
exempt from this, are by contrast much more complex and require more
changes.  For a feature that was so far requested by a single user,
I'm not sure this is justified.

As for your example: if Doom uses this for icons, why cannot Doom
refrain from using bold face for these cases?





  reply	other threads:[~2023-12-14 10:04 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13 12:03 bug#67810: 29.1; fonts use synthetic bold on Linux / pgtk Tim Ruffing
2023-12-13 12:39 ` Eli Zaretskii
2023-12-13 13:28   ` Tim Ruffing
2023-12-13 13:39     ` Eli Zaretskii
2023-12-13 15:09       ` Tim Ruffing
2023-12-13 15:43         ` Tim Ruffing
2023-12-14  0:09         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-14  7:28           ` Eli Zaretskii
2023-12-14  9:32             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-14  9:54             ` Tim Ruffing
2023-12-14 10:04               ` Eli Zaretskii [this message]
2023-12-14 10:37                 ` Tim Ruffing
2023-12-14 11:19                   ` Eli Zaretskii
2023-12-14 11:26                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-14 15:06                   ` Tim Ruffing
2023-12-14 22:55                     ` Stefan Kangas
2024-01-11 15:50                       ` Tim Ruffing
2024-01-12  1:46                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12  8:37                           ` Eli Zaretskii
2024-01-12  9:59                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 11:46                               ` Eli Zaretskii
2024-01-12 12:20                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 12:30                                   ` Eli Zaretskii
2024-01-12 13:12                                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-12 14:12                                       ` Eli Zaretskii
2024-01-13  0:46                                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-13  6:59                                           ` Eli Zaretskii
2024-01-14  1:02                                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14  6:24                                               ` Eli Zaretskii
2024-01-14  8:09                                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14  9:33                                                   ` Eli Zaretskii
2024-01-14 13:44                                                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 14:03                                                       ` Eli Zaretskii
2024-01-14 14:19                                                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 14:55                                                           ` Eli Zaretskii
2024-01-15 13:11                                             ` Tim Ruffing
2024-01-13  6:37                           ` Stefan Kangas
2024-01-14  0:55                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14  5:23                               ` Stefan Kangas
2024-01-14 10:20                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 12:21                                   ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 14:10                                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-14 16:37                                       ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15  0:36                                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15 13:56                                           ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-15 14:02                                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83le9xqewb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=67810@debbugs.gnu.org \
    --cc=crypto@timruffing.de \
    --cc=luangruo@yahoo.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.