From: Eli Zaretskii <eliz@gnu.org>
To: Jesse Sheidlower <jester@panix.com>
Cc: 51277@debbugs.gnu.org
Subject: bug#51277: 27.1; menu-set-font not loading correct font
Date: Tue, 19 Oct 2021 18:58:04 +0300 [thread overview]
Message-ID: <837de9c8hf.fsf@gnu.org> (raw)
In-Reply-To: <YW7DRKnyxUA28Txb@panix.com> (message from Jesse Sheidlower on Tue, 19 Oct 2021 09:08:20 -0400)
> Date: Tue, 19 Oct 2021 09:08:20 -0400
> From: Jesse Sheidlower <jester@panix.com>
> Cc: 51277@debbugs.gnu.org
>
> > Sorry, I meant to say "M-:" instead of "M-x". It was a typo.
>
> OK, in this case, yes, it produces the, um, desired effect: Emacs
> displays with the "Book", rather than the "Bold", version of that font.
OK, so at least you have a workaround for this strange problem.
> Yes, it works correctly with certain other fonts. For example, DejaVu
> Sans Mono Book is correctly displayed by menu-set-font and correctly
> loaded by Emacs.
>
> I do note that the filename of the "Book" variant of DejaVu Sans Mono
> does not contain the word "Book"; the filename is simply DejaVuSans.ttf.
> I don't know if that's relevant.
I don't think it is, no.
> Given that the recipe "emacs -Q -fn 'Operator Mono SSm'" followed by
> "M-: (set-face-attribute 'default nil :weight 'book) RET" does produce
> the desired result, does that tell us anything useful about what's going
> on, to either fix Emacs or to communicate something with Hoefler about
> fixing their font?
It puzzles me, I expected that set-face-attribute won't work as well.
Now I don't know what to think. Hmm... maybe the font processing log
will give a clue? In "emacs -Q", do
M-: (setq font-log nil) RET
then repeat the recipe with selecting that problematic font, and after
that go to *scratch* and type
(pp font-log) C-j
where C-j should be typed with cursor after the closing paren of
"(pp font-log)". Then post the result here.
next prev parent reply other threads:[~2021-10-19 15:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 22:08 bug#51277: 27.1; menu-set-font not loading correct font Jesse Sheidlower
2021-10-19 11:08 ` Eli Zaretskii
[not found] ` <YW64Fi5/BIFRQ0R5@panix.com>
2021-10-19 12:43 ` Eli Zaretskii
2021-10-19 13:08 ` Jesse Sheidlower
2021-10-19 15:58 ` Eli Zaretskii [this message]
2021-10-19 16:47 ` Jesse Sheidlower
2021-10-19 17:29 ` Eli Zaretskii
2021-10-19 18:08 ` Jesse Sheidlower
2021-10-19 18:14 ` Eli Zaretskii
2021-10-19 18:17 ` Jesse Sheidlower
2021-10-20 8:50 ` Robert Pluim
2021-10-20 11:30 ` Jesse Sheidlower
2021-10-20 12:36 ` Eli Zaretskii
2021-10-20 15:02 ` Robert Pluim
2021-10-20 15:12 ` Lars Ingebrigtsen
2021-10-20 15:20 ` Robert Pluim
2021-10-20 16:22 ` Eli Zaretskii
2021-10-21 2:13 ` Lars Ingebrigtsen
2021-10-21 2:11 ` Lars Ingebrigtsen
2021-10-21 7:40 ` Robert Pluim
2021-10-21 12:59 ` Lars Ingebrigtsen
2021-10-21 15:37 ` Robert Pluim
2021-10-22 14:27 ` Lars Ingebrigtsen
2021-10-20 12:31 ` Eli Zaretskii
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=837de9c8hf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51277@debbugs.gnu.org \
--cc=jester@panix.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).