GNU bug report logs - #51277
27.1; menu-set-font not loading correct font

Previous Next

Package: emacs;

Reported by: Jesse Sheidlower <jester <at> panix.com>

Date: Mon, 18 Oct 2021 22:09:02 UTC

Severity: normal

Found in version 27.1

Full log


Message #26 received at 51277 <at> debbugs.gnu.org (full text, mbox):

From: Jesse Sheidlower <jester <at> panix.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 51277 <at> debbugs.gnu.org
Subject: Re: bug#51277: 27.1; menu-set-font not loading correct font
Date: Tue, 19 Oct 2021 14:08:43 -0400
On Tue, Oct 19, 2021 at 08:29:30PM +0300, Eli Zaretskii wrote:
> > Date: Tue, 19 Oct 2021 12:47:39 -0400
> > From: Jesse Sheidlower <jester <at> panix.com>
> > Cc: 51277 <at> debbugs.gnu.org
> > 
> > >   (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.
> > 
> > OK, just to clarify, I ran this command immediately after selecting the "Book" font from menu-set-font, and incorrectly getting the bold font. I did not then run the set-face-attribute command discussed above. The result was:
> > 
> > 
> > (pp font-log) 
> > ((sort-by "-*-bold-normal-normal-*-22-*" "ftcrhb:-H&Co-Operator Mono SSm-normal-normal-normal-*-m-0-iso10646-1")
> >  (list "-H&Co-Operator Mono SSm-*-iso8859-1"
> >        ["-H&Co-Operator Mono SSm-light-normal-normal-*-m-0-iso10646-1" "-H&Co-Operator Mono SSm-normal-normal-normal-*-m-0-iso10646-1" "-H&Co-Operator Mono SSm-light-italic-normal-*-m-0-iso10646-1" "-H&Co-Operator Mono SSm-light-normal-normal-*-m-0-iso10646-1" "-H&Co-Operator Mono SSm-light-italic-normal-*-m-0-iso10646-1" "-H&Co-Operator Mono SSm-light-italic-normal-*-m-0-iso10646-1" "-H&Co-Operator Mono SSm-light-normal-normal-*-m-0-iso10646-1" "-H&Co-Operator Mono SSm-normal-italic-normal-*-m-0-iso10646-1"])
> 
> Thanks, the only thing I find strange here is that Emacs never tries
> to look for "book" font, nor even under one of its aliases.
> 
> 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? And what's the correct sequence to test this in our current framework?

Thanks.




This bug report was last modified 3 years and 319 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.