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: Fri, 14 Jun 2019 15:24:33 +0200 [thread overview]
Message-ID: <m2zhmkz4dq.fsf@gmail.com> (raw)
In-Reply-To: <838su4xsid.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 14 Jun 2019 15:26:18 +0300")
>>>>> On Fri, 14 Jun 2019 15:26:18 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> From: Robert Pluim <rpluim@gmail.com>
>> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
>> Date: Fri, 14 Jun 2019 13:52:28 +0200
>>
>> Whilst such an ability to change font backends is cool, I really donʼt
>> see it being very much used: as I said in my other message, in the
>> long term only the HarfBuzz backend will be supported, so I donʼt see
>> any need to add such infrastructure.
Eli> In addition to what I already wrote on this matter, there's one more
Eli> consideration we should keep in mind: Emacs should never put all of
Eli> its eggs into a single basket. As active as HarfBuzz development is
Eli> today, that could change in the future for reasons beyond our
Eli> control. So we should keep the mechanism of using more than a single
Eli> font backend, in case we will need to make another change such as the
Eli> one we did now with HarfBuzz.
I was not proposing that we remove the ability to change font
backends, just that we not implement the font backend superseding
stuff.
Robert
prev parent reply other threads:[~2019-06-14 13:24 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
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 [this message]
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=m2zhmkz4dq.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 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.