From: Jesse Sheidlower <jester@panix.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: 51277@debbugs.gnu.org
Subject: bug#51277: 27.1; menu-set-font not loading correct font
Date: Wed, 20 Oct 2021 07:30:21 -0400 [thread overview]
Message-ID: <YW/9zZLNtEsc/jWG@panix.com> (raw)
In-Reply-To: <87zgr42i78.fsf@gmail.com>
On Wed, Oct 20, 2021 at 10:50:35AM +0200, Robert Pluim wrote:
> >>>>> On Tue, 19 Oct 2021 14:17:01 -0400, Jesse Sheidlower <jester@panix.com> said:
>
> Jesse> On Tue, Oct 19, 2021 at 09:14:34PM +0300, Eli Zaretskii wrote:
> >> > Date: Tue, 19 Oct 2021 14:08:43 -0400
> >> > From: Jesse Sheidlower <jester@panix.com>
> >> > Cc: 51277@debbugs.gnu.org
> >> >
> >> > > Another thing I see is that you have 3 active font backends: xfont,
> >> > > ftfont, and fcrhb. Maybe that has something to do with the issue...
> >> >
> >> > Is there a "best" one to use?
> >>
> >> That'd be fcrhb.
> >>
> >> > And what's the correct sequence to test this in our current framework?
> >>
> >> What would you like to test?
>
> Jesse> Whether using a single font backend will allow Emacs to find the font
> Jesse> I'm trying to select.
>
> If you want to test restricting emacs to a single font-backend, put
> something like the following in your .emacs
>
> (add-to-list 'default-frame-alist '(font-backend ftcrhb))
>
> (and note that itʼs spelled 'ftcrhb', not 'fcrhb').
>
> If the font is found with xfont or ftfont, but not with ftcrhb, that
> would be somewhat surprising, given that ftcrhb finds the 'bold' version.
Thank you for this. I saw that that was a way to do it, but putting it
in my .emacs conflicts with running emacs -Q. But assuming that it's
OK at this point to run emacs without -Q, I did try it.
There is no difference in the result: whether I restrict emacs to xfont,
ftfont, or ftcrhb, it still loads the "Bold" file even when I select the
"Book" version from menu-set-font.
Where does this leave us? It does still seem like a bug (albeit one that
apparently affects very few people).
Jesse
next prev parent reply other threads:[~2021-10-20 11:30 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
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 [this message]
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=YW/9zZLNtEsc/jWG@panix.com \
--to=jester@panix.com \
--cc=51277@debbugs.gnu.org \
--cc=rpluim@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).