From: Vincent Bernat <bernat@luffy.cx>
To: Eli Zaretskii <eliz@gnu.org>, Po Lu <luangruo@yahoo.com>
Cc: 43128@debbugs.gnu.org, mituharu@math.s.chiba-u.ac.jp
Subject: bug#43128: Acknowledgement (27.1; DPI change not detected after switching to Emacs 27.1)
Date: Thu, 27 Oct 2022 18:55:52 +0200 [thread overview]
Message-ID: <96ed612e-efdf-8c46-e488-39a39a5beb0d@luffy.cx> (raw)
In-Reply-To: <83k04lkyyz.fsf@gnu.org>
On 2022-10-27 18:33, Eli Zaretskii wrote:
>> Date: Tue, 25 Oct 2022 23:02:16 +0200
>> From: Vincent Bernat <bernat@luffy.cx>
>> Cc: mituharu@math.s.chiba-u.ac.jp, 43128@debbugs.gnu.org
>>
>>> I'll try to do something, but I have no experience with either Xft or
>>> Cairo, so if that's something clever to do, I am likely to fail.
>>
>> I was able to build this patch. I did replace XftDefaultSubstitute() by
>> something that looks correct. However, for XftDefaultSet(), it seems
>> there is no mechanism to override the defaults for fontconfig or cairo,
>> so it seems not needed to find a substitute.
>
> Sorry, I don't understand. Are you saying that the patch you posted
> solves the problem for you? Then what do you mean in the last
> sentence above about XftDefaultSet?
The patch works for me, but I was unable to replace XftDefaultSet. From
my understanding, while Xft has a way to override the defaults, this is
not the case for fontconfig and Cairo. So, I suppose this is not needed
for fontconfig and Cairo and other parts of the code should ensure the
new settings are used without relying on defaults.
Also, the Cairo-specific part of the patch makes no difference for me. I
have included it because Cairo documentation says to put it there.
next prev parent reply other threads:[~2022-10-27 16:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 7:31 bug#43128: 27.1; DPI change not detected after switching to Emacs 27.1 Vincent Bernat
[not found] ` <handler.43128.B.15988596567523.ack@debbugs.gnu.org>
2020-09-02 7:28 ` bug#43128: Acknowledgement (27.1; DPI change not detected after switching to Emacs 27.1) Vincent Bernat
2020-09-02 7:51 ` Vincent Bernat
2020-09-02 7:58 ` YAMAMOTO Mitsuharu
2020-09-02 8:20 ` Vincent Bernat
2020-09-02 14:16 ` Eli Zaretskii
2020-09-02 18:10 ` Vincent Bernat
2020-09-02 14:18 ` Eli Zaretskii
2020-11-23 17:36 ` Eli Zaretskii
2021-07-18 21:38 ` Vincent Bernat
2021-07-19 12:03 ` Eli Zaretskii
2021-07-19 12:09 ` Vincent Bernat
2022-10-25 21:02 ` Vincent Bernat
2022-10-27 16:33 ` Eli Zaretskii
2022-10-27 16:55 ` Vincent Bernat [this message]
2022-10-28 0:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28 7:30 ` Eli Zaretskii
2022-10-29 12:30 ` bug#43128: Changed the font selection after 52d4c98cec0901ef5cc1c55d5b3b33ac9d9c519f OGAWA Hirofumi
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=96ed612e-efdf-8c46-e488-39a39a5beb0d@luffy.cx \
--to=bernat@luffy.cx \
--cc=43128@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=mituharu@math.s.chiba-u.ac.jp \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.