all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Amin Bandali <bandali@gnu.org>
Cc: 57555@debbugs.gnu.org
Subject: bug#57555: 29.0.50; variable-pitch font issue with medium weight default font
Date: Mon, 05 Sep 2022 18:51:02 +0300	[thread overview]
Message-ID: <83o7vtkeft.fsf@gnu.org> (raw)
In-Reply-To: <87y1uxg8px.fsf@gnu.org> (message from Amin Bandali on Mon, 05 Sep 2022 11:08:10 -0400)

> From: Amin Bandali <bandali@gnu.org>
> Cc: 57555@debbugs.gnu.org
> Date: Mon, 05 Sep 2022 11:08:10 -0400
> 
> (when (display-graphic-p)
>   (set-fontset-font t 'arabic "Vazir"))
> 
> And further down:
> 
> (when (display-graphic-p)
>   (with-eval-after-load 'faces
>     (let ((grey "#e7e7e7"))
>       (set-face-attribute 'fixed-pitch nil :family "Source Code Pro")
>       (set-face-attribute 'mode-line nil
>                           :background grey
>                           :inherit 'fixed-pitch))))

Does it change anything if you remove the customization of fixed-pitch
face?

> > Can't you customize the variable-pitch face to specify the FreeSans
> > family, or even to specify the exact font you want Emacs to use?  That
> > should allow you to override any built-in heuristics that Emacs uses
> > when it has no other restrictions.
> >
> 
> This indeed doesn't seem to work anymore.  With the following,
> 
>     (set-face-attribute 'variable-pitch nil :family "FreeSans")
> 
> Emacs picks/uses Source Code Pro medium for variable-pitch (confirmed
> visually and with describe-char), even though describe-face for
> variable-pitch shows the family set as "FreeSans".  This used to work
> before, but not anymore.

Even if you set the face's font explicitly by its full XLFD name, not
implicitly via :family?





  reply	other threads:[~2022-09-05 15:51 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 [this message]
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
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

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

  git send-email \
    --in-reply-to=83o7vtkeft.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=57555@debbugs.gnu.org \
    --cc=bandali@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 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.