From: Yuri D'Elia <wavexx@thregr.org>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
dgutov@yandex.ru, larsi@gnus.org, monnier@iro.umontreal.ca,
emacs-devel@gnu.org
Subject: Re: Incorrect font weight selected
Date: Thu, 06 Jan 2022 10:49:55 +0100 [thread overview]
Message-ID: <87bl0p9opf.fsf@wavexx.thregr.org> (raw)
In-Reply-To: <87wnjd66hs.fsf@yahoo.com>
On Thu, Jan 06 2022, Po Lu wrote:
> Yuri D'Elia <wavexx@thregr.org> writes:
>
>> This seems to work correctly for me now, however I'm only testing on
>> x11. font_open_by_name is not used in many places aside frame creation.
>
> FWIW, this breaks the Haiku font driver (displaying etc/HELLO becomes
> very slow afterwards) -- if someone wants this installed, no matter, I
> will fix it afterwards, but this could be indicative of some larger
> problems.
Uuh, didn't think of trying etc/HELLO.
However after this and report from Sean, that I agree that at least for
the moment reverting 1b2511f seems the best course of action.
But this all smells of some deeper underlying problem to me.
next prev parent reply other threads:[~2022-01-06 9:49 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 14:51 Incorrect font weight selected Yuri D'Elia
2021-12-17 18:55 ` Eli Zaretskii
2021-12-17 19:47 ` Yuri D'Elia
2021-12-17 20:27 ` Eli Zaretskii
2021-12-17 21:25 ` Yuri D'Elia
2021-12-18 6:32 ` Eli Zaretskii
2021-12-18 10:43 ` Yuri D'Elia
2021-12-18 11:41 ` Eli Zaretskii
2021-12-18 12:00 ` Yuri D'Elia
2021-12-18 12:49 ` Eli Zaretskii
2021-12-19 11:14 ` Yuri D'Elia
2021-12-19 12:46 ` Eli Zaretskii
2021-12-19 13:17 ` Yuri D'Elia
2021-12-19 13:32 ` Lars Ingebrigtsen
2021-12-19 23:24 ` Yuri D'Elia
2021-12-20 10:34 ` Lars Ingebrigtsen
2021-12-20 19:43 ` Stefan Monnier
2021-12-20 19:52 ` Eli Zaretskii
2021-12-20 20:14 ` Stefan Monnier
2021-12-20 20:19 ` Eli Zaretskii
2021-12-21 4:22 ` Dmitry Gutov
2021-12-21 12:18 ` Eli Zaretskii
2021-12-21 12:27 ` Yuri D'Elia
2021-12-21 14:19 ` Eli Zaretskii
2022-01-05 16:19 ` Yuri D'Elia
2022-01-05 17:05 ` Eli Zaretskii
2022-01-05 17:11 ` Yuri D'Elia
2022-01-05 18:04 ` Eli Zaretskii
2022-01-05 18:08 ` Yuri D'Elia
2022-01-05 19:07 ` Eli Zaretskii
2022-01-05 23:16 ` Yuri D'Elia
2022-01-06 7:09 ` Eli Zaretskii
2022-01-06 9:46 ` Yuri D'Elia
2022-01-06 12:22 ` Eli Zaretskii
2022-01-05 21:57 ` Dmitry Gutov
2022-01-05 23:15 ` Yuri D'Elia
2022-01-05 23:15 ` Yuri D'Elia
2022-01-06 5:15 ` Sean Whitton
2022-01-06 0:41 ` Po Lu
2022-01-06 0:54 ` Po Lu
2022-01-06 9:49 ` Yuri D'Elia [this message]
2022-01-06 12:21 ` Eli Zaretskii
2021-12-21 13:52 ` John ff
2021-12-20 20:05 ` Stefan Monnier
2021-12-20 15:16 ` Eli Zaretskii
2021-12-18 23:26 ` Sean Whitton
2021-12-19 6:44 ` Eli Zaretskii
2021-12-19 11:29 ` Yuri D'Elia
2021-12-19 12:52 ` Eli Zaretskii
2021-12-19 12:57 ` Yuri D'Elia
2021-12-19 13:32 ` Eli Zaretskii
2021-12-19 21:03 ` Sean Whitton
2021-12-19 22:04 ` Yuri D'Elia
2021-12-19 22:39 ` Sean Whitton
2021-12-20 21:59 ` Sean Whitton
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=87bl0p9opf.fsf@wavexx.thregr.org \
--to=wavexx@thregr.org \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
/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).