From: "T.V Raman" <raman@google.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: Robert Pluim <rpluim@gmail.com>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: master d8da850: Document cairo-related fallout to font-backend settings
Date: Tue, 21 Jan 2020 06:54:36 -0800 [thread overview]
Message-ID: <p917e1koo5v.fsf@google.com> (raw)
In-Reply-To: <CADwFkm=+YFLSVy71_b9scEU1C4eeh-ECfuKuhqqRjqgb6jwdtQ@mail.gmail.com> (Stefan Kangas's message of "Tue, 21 Jan 2020 00:12:22 +0100")
Stefan Kangas <stefan@marxist.se> writes:
Also, perhaps update frames.texi to indicate that ftcr and ftcrhb are
mutually incompatible. Having both doesn't appear to hurt right now, but
might perhaps cause issues later?> Robert Pluim <rpluim@gmail.com> writes:
>
>> The correct choice depends on how their Emacs has been built; ftcr and
>> ftcrhb are mutually exclusive [1](see my earlier update to the elisp
>> manual). I guess we could say something like this:
>
> Indeed, I read that after I wrote the above.
>
>> -Cairo. Use either 'ftcr' or 'ftcrhb' instead for FreeType and
>> -FreeType + HarfBuzz respectively. 'x' is still a valid backend.
>> -
>> +Cairo. Use 'ftcrhb' if your Emacs was built with HarfBuzz support,
>> +and 'ftcr' otherwise. You can this determine by checking
>> +'system-configuration-features'. 'x' is still a valid backend.
>
> Thank you, that is much better. Please install.
>
>> [1] My master plan to remove as many different variations as possible
>> seems to get shot down every time I suggest it :-)
>
> BTW, if 'ftcr' only works when built without HarfBuzz, and 'ftcrhb'
> only works with HarfBuzz, can't we just use 'ftcr' and detect HarfBuzz
> automatically for the user?
>
> Best regards,
> Stefan Kangas
>
--
next prev parent reply other threads:[~2020-01-21 14: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 [this message]
2020-01-21 15:38 ` Robert Pluim
2020-01-21 16:54 ` Robert Pluim
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=p917e1koo5v.fsf@google.com \
--to=raman@google.com \
--cc=emacs-devel@gnu.org \
--cc=rpluim@gmail.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 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.