From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: peter.mao@gmail.com, 65191@debbugs.gnu.org
Subject: bug#65191: 29.1; -ms and -cr CL options don't work
Date: Fri, 11 Aug 2023 15:36:17 +0800 [thread overview]
Message-ID: <87350qqbda.fsf@yahoo.com> (raw)
In-Reply-To: <83leeighy4.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 11 Aug 2023 10:24:19 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> I don't think I understand this well enough to discuss this
> intelligently, so please elaborate on what happens, and include
> pointers to more of the code so I and others could complement the
> descriptions with what's actually in the code, and maybe suggest
> alternative ways of dealing with this.
>
> Not responding to Cairo setting changes sounds like a loss: what
> features are currently based on that, and would be lost if we revert
> this support? Also, can't you think about an alternative way of
> handling dynamic settings that will let us eat the cake, but also have
> it?
The problem boils down to apply_xft_settings, within xsettings.c. Under
Cairo, that function calls:
FcConfigSubstitute (NULL, pat, FcMatchPattern);
options = cairo_font_options_create ();
ftcrfont_get_default_font_options (dpyinfo, options); <------
cairo_ft_font_options_substitute (options, pat);
cairo_font_options_destroy (options);
FcDefaultSubstitute (pat);
to retrieve the settings currently in effect, and compare them against
the updated settings within the XSettings event. If a divergence is
located, a config-changed event is sent. Under Xft, the following code
is ultimately run:
XftDefaultSet (dpyinfo->display, pat);
but Cairo provides no analog, so these settings are never saved back to
Cairo (nor can I find any means by which to do so.)
next prev parent reply other threads:[~2023-08-11 7:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 3:00 bug#65191: 29.1; -ms and -cr CL options don't work Peter Mao
2023-08-10 7:01 ` Eli Zaretskii
2023-08-10 7:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-10 7:19 ` Eli Zaretskii
2023-08-10 7:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-10 7:47 ` Eli Zaretskii
2023-08-10 7:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <CAEK3s1NrTSTtvQKkhOYaUPafZoSn=Gm=QaYwPO8UUmTC66bUgw@mail.gmail.com>
[not found] ` <CAEK3s1Mtt5jckJzptYdhK4jU5tS0k1SJHXy6DgTGY94CjoYSFQ@mail.gmail.com>
[not found] ` <87il9mqhj1.fsf@yahoo.com>
2023-08-11 5:43 ` Peter Mao
2023-08-11 6:06 ` Peter Mao
2023-08-11 6:23 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-12 4:36 ` Peter Mao
2023-08-12 4:44 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-11 6:22 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-11 7:24 ` Eli Zaretskii
2023-08-11 7:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-08-11 11:05 ` Eli Zaretskii
2023-08-12 0:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87350qqbda.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=65191@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=peter.mao@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 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.