unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 57555@debbugs.gnu.org, gregory@heytings.org, bandali@gnu.org
Subject: bug#57555: 29.0.50; variable-pitch font issue with medium weight default font
Date: Wed, 07 Sep 2022 16:01:09 +0300	[thread overview]
Message-ID: <831qsnibje.fsf@gnu.org> (raw)
In-Reply-To: <87illznylq.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed,  07 Sep 2022 14:44:01 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: gregory@heytings.org,  bandali@gnu.org,  57555@debbugs.gnu.org
> Date: Wed, 07 Sep 2022 14:44:01 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> So we've come full circle.
> >
> > No, we haven't.
> 
> In what way isn't that "full circle"?

In the way I explained below:

> > Emacs works as expected: it requests a medium-weight
> > font for the variable-pitch face, because the fixed-pitch face was
> > customized to use a medium weight.  Since the font Amin wants to use
> > for variable-pitch doesn't have a medium variant, Emacs selects
> > another one.  There's no real problem I see here, except an issue with
> > user expectations not being satisfied.
> 
> I think that the vast majority of users would want Emacs to choose a
> different weight, but use the same font, which is what we had before we
> went full circle.

So maybe we should consider resetting just the weight attribute,
perhaps only if its value is 'medium' (assuming that solves this
particular issue).  That's a far cry from resetting all of them.





  reply	other threads:[~2022-09-07 13:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-03  1:35 bug#57555: 29.0.50; variable-pitch font issue with medium weight default font Amin Bandali
2022-09-03  6:23 ` Eli Zaretskii
2022-09-05  7:06   ` Amin Bandali
2022-09-05 11:57     ` Eli Zaretskii
2022-09-05 15:08       ` Amin Bandali
2022-09-05 15:51         ` Eli Zaretskii
2022-09-05 18:19           ` Amin Bandali
2022-09-05 18:43             ` Eli Zaretskii
2022-09-05 21:17               ` Gregory Heytings
2022-09-06  2:28                 ` Eli Zaretskii
2022-09-06  8:08                   ` Gregory Heytings
2022-09-06 12:50                     ` Eli Zaretskii
2022-09-06 13:09                       ` Gregory Heytings
2022-09-06 13:15                         ` Eli Zaretskii
2022-09-06 14:28                       ` Lars Ingebrigtsen
2022-09-06 15:42                         ` Eli Zaretskii
2022-09-07 12:44                           ` Lars Ingebrigtsen
2022-09-07 13:01                             ` Eli Zaretskii [this message]
2022-09-08 11:42                               ` Lars Ingebrigtsen
2022-09-08 13:34                                 ` Eli Zaretskii
2022-11-20 13:57                                   ` Gregory Heytings
2022-11-20 15:27                                     ` Amin Bandali
2022-11-20 15:46                                       ` Gregory Heytings
2022-11-20 16:13                                         ` Amin Bandali
2022-11-20 17:01                                           ` Gregory Heytings
2022-12-10 22:54                                             ` Gregory Heytings
2022-09-06  2:34                 ` Amin Bandali

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=831qsnibje.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=57555@debbugs.gnu.org \
    --cc=bandali@gnu.org \
    --cc=gregory@heytings.org \
    --cc=larsi@gnus.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).