From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: When and how to register various font backends
Date: Mon, 17 Jun 2019 11:41:00 +0200 [thread overview]
Message-ID: <m2k1dkh7mb.fsf@gmail.com> (raw)
In-Reply-To: 83d0jfw528.fsf@gnu.org
>>>>> On Sat, 15 Jun 2019 12:50:23 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> Date: Fri, 14 Jun 2019 17:47:07 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>> Cc: emacs-devel@gnu.org
>>
>> > (add-to-list 'default-frame-alist '(font-backend xft x)) works already, no? And
>> > presumably continues to work with your solution.
>>
>> No, it doesn't work with my solution, at least not reliably, because I
>> didn't intend it to work.
Eli> But what about being able to specify the backend(s) via
Eli> default-frame-alist in the init file, and expecting that to affect all
Eli> the frames including the initial one? Mitsuharu's proposal allows
Eli> that, whereas mine doesn't. That's because in my implementation the
Eli> font backend is registered at frame creation time, and only the
Eli> backends known to be requested at that time are registered. So when
Eli> we call modify-frame-parameters later, after processing the init file,
Eli> to make default-frame-alist parameters take effect, you cannot request
Eli> a backend that wasn't registered.
Eli> By contrast, Mitsuharu's method registers all the backends, but only
Eli> activates some of them. So modify-frame-parameters can work, because
Eli> it just needs to activate an already registered backend.
I see. I guess one potential fix would be to change the default value
of default-frame-alist, but that wouldnʼt help people who have already
customised it.
So it seems that Mitsuharu's proposal is the only one that fulfills
all your requirements.
Robert
next prev parent reply other threads:[~2019-06-17 9:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 19:40 When and how to register various font backends Eli Zaretskii
2019-06-14 9:14 ` Robert Pluim
2019-06-14 12:19 ` Eli Zaretskii
2019-06-14 13:16 ` Robert Pluim
2019-06-14 14:47 ` Eli Zaretskii
2019-06-15 9:50 ` Eli Zaretskii
2019-06-17 3:03 ` Michael Welsh Duggan
2019-06-17 9:41 ` Robert Pluim [this message]
2019-06-17 16:01 ` Eli Zaretskii
2019-06-18 1:29 ` YAMAMOTO Mitsuharu
2019-06-18 17:26 ` Eli Zaretskii
2019-06-18 23:21 ` YAMAMOTO Mitsuharu
2019-06-19 16:42 ` Eli Zaretskii
2019-06-14 16:54 ` Andy Moreton
2019-06-14 10:52 ` YAMAMOTO Mitsuharu
2019-06-14 11:52 ` Robert Pluim
2019-06-14 12:26 ` Eli Zaretskii
2019-06-14 13:24 ` Robert Pluim
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=m2k1dkh7mb.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).