From: Robert Pluim <rpluim@gmail.com>
To: "T.V Raman" <raman@google.com>
Cc: Stefan Kangas <stefan@marxist.se>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: master d8da850: Document cairo-related fallout to font-backend settings
Date: Tue, 21 Jan 2020 17:54:59 +0100 [thread overview]
Message-ID: <m2sgk8px5o.fsf@gmail.com> (raw)
In-Reply-To: <m25zh4rfae.fsf@gmail.com> (Robert Pluim's message of "Tue, 21 Jan 2020 16:38:01 +0100")
>>>>> On Tue, 21 Jan 2020 16:38:01 +0100, Robert Pluim <rpluim@gmail.com> said:
>>>>> On Tue, 21 Jan 2020 06:54:36 -0800, "T.V Raman" <raman@google.com> said:
TVR> Stefan Kangas <stefan@marxist.se> writes:
TVR> Also, perhaps update frames.texi to indicate that ftcr and ftcrhb are
TVR> mutually incompatible. Having both doesn't appear to hurt right now, but
TVR> might perhaps cause issues later?
Robert> I updated frames.texi on emacs-27 earlier in the week along those
Robert> lines. Having both doesnʼt hurt, they're not incompatible, you just can
Robert> only have one or the other (and you canʼt switch between them dynamically).
Let me qualify that: you can in fact use the ftcr font backend even if
your emacs is built with HarfBuzz, but you need to make that decision
at frame creation time. Iʼll reword NEWS and frames.texi to that
effect.
Robert
next prev parent reply other threads:[~2020-01-21 16:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200120162048.23970.80216@vcs0.savannah.gnu.org>
[not found] ` <20200120162050.08A5421148@vcs0.savannah.gnu.org>
2020-01-20 21:05 ` master d8da850: Document cairo-related fallout to font-backend settings Stefan Kangas
2020-01-20 21:50 ` Robert Pluim
2020-01-20 23:12 ` Stefan Kangas
2020-01-21 7:44 ` Robert Pluim
2020-01-21 15:32 ` Eli Zaretskii
2020-01-21 15:39 ` Robert Pluim
2020-01-21 15:47 ` Eli Zaretskii
2020-01-22 7:22 ` Robert Pluim
2020-01-22 15:52 ` Eli Zaretskii
2020-01-22 16:11 ` Robert Pluim
2020-01-22 16:55 ` Eli Zaretskii
2020-01-22 16:53 ` Eli Zaretskii
2020-01-22 16:59 ` Robert Pluim
2020-01-22 17:38 ` Eli Zaretskii
2020-01-21 14:54 ` T.V Raman
2020-01-21 15:38 ` Robert Pluim
2020-01-21 16:54 ` Robert Pluim [this message]
2020-01-21 17:04 ` Eli Zaretskii
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=m2sgk8px5o.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=raman@google.com \
--cc=stefan@marxist.se \
/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).