Re: Emacs 28: Specific TTF font gets loaded with font-backend x instead of ftcrhb

[Tassilo Horn <tsdh@gnu.org>]

Tassilo Horn <tsdh@gnu.org> writes:

> That's signalled in composite.c's Fcomposition_get_gstring function,
> either line 1738 or 1749.  I've set beakpoints there, and now I have an
> emacs instance halted at 1749.
>
> Thread 1 "emacs" hit Breakpoint 4, Fcomposition_get_gstring (
>     from=<optimized out>, to=<optimized out>, font_object=XIL(0x5555562346e5), 
>     string=XIL(0x555556a34ec4)) at composite.c:1749
> 1749		error ("Attempt to shape unibyte text");

Oh, of course I've forgotten the most obvious part, i.e., frame 0:

(gdb) pp string
"--"
(gdb) pp font_object
#<font-object "-JB  -JetBrains Mono-normal-normal-normal-*-15-*-*-*-m-0-iso10646-1">

And indeed, the mode-line in a Gnus Summary buffer starts with "U:---".

--8<---------------cut here---------------start------------->8---
mode-line-format is a variable defined in ‘C source code’.
Its value is
("%e" mode-line-front-space mode-line-mule-info mode-line-client mode-line-modified mode-line-remote mode-line-frame-identification mode-line-buffer-identification "   " mode-line-position
 (vc-mode vc-mode)
 "  " mode-line-modes mode-line-misc-info mode-line-end-spaces)
Local in buffer *Summary nnimap+Fastmail:mailinglists/help-gnu-emacs*; global value is 
("%e" mode-line-front-space mode-line-mule-info mode-line-client mode-line-modified mode-line-remote mode-line-frame-identification mode-line-buffer-identification "   " mode-line-position
 (vc-mode vc-mode)
 "  " mode-line-modes mode-line-misc-info mode-line-end-spaces)
--8<---------------cut here---------------end--------------->8---

Bye,
Tassilo