From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34663@debbugs.gnu.org, stefan@marxist.se
Subject: bug#34663: remove ftx font backend
Date: Tue, 07 Jan 2020 08:14:48 +0100 [thread overview]
Message-ID: <m2blrfagbb.fsf@gmail.com> (raw)
In-Reply-To: <83woa4c52l.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 07 Jan 2020 05:34:42 +0200")
>>>>> On Tue, 07 Jan 2020 05:34:42 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> From: Robert Pluim <rpluim@gmail.com>
>> Cc: Stefan Kangas <stefan@marxist.se>, 34663@debbugs.gnu.org
>> Date: Tue, 07 Jan 2020 00:05:36 +0100
>>
Eli> . please add a NEWS entry about ftx's removal (in the "Installation
Eli> Changes" section)
Eli> . please add a NEWS entry on the emacs-27 branch saying that this
Eli> font backend is deprecated and will be removed
>>
>> Can we do something similar for XFT (and flip --with-cairo to
>> enabled)?
Eli> I understand about enabling Cairo, but what exactly are you proposing
Eli> to do with XFT?
Add an entry to NEWS on master that itʼs deprecated and will be
removed, and add verbiage to configure telling people to install cairo
development packages if XFT is detected. That means weʼd remove XFT in
emacs-29.
Robert
next prev parent reply other threads:[~2020-01-07 7:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <hfef7vf6ri.fsf@fencepost.gnu.org>
2019-10-06 12:58 ` bug#34663: remove ftx font backend Stefan Kangas
2019-10-06 13:01 ` Stefan Kangas
2019-10-06 17:58 ` Eli Zaretskii
2019-10-06 20:04 ` Stefan Kangas
2020-01-02 20:44 ` Stefan Kangas
2020-01-03 7:35 ` Eli Zaretskii
2020-01-06 23:05 ` Robert Pluim
2020-01-07 3:34 ` Eli Zaretskii
2020-01-07 7:14 ` Robert Pluim [this message]
2020-01-07 15:55 ` Eli Zaretskii
2020-01-07 15:59 ` Robert Pluim
2020-01-07 16:14 ` Eli Zaretskii
2020-01-08 10:09 ` Stefan Kangas
2020-01-15 0:57 ` Stefan Kangas
2020-01-15 16:16 ` Eli Zaretskii
2020-01-15 17:24 ` Eli Zaretskii
2020-01-15 19:06 ` Stefan Kangas
2020-01-15 19:23 ` Eli Zaretskii
2020-01-15 19:57 ` Stefan Kangas
2020-01-15 18:59 ` Stefan Kangas
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=m2blrfagbb.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=34663@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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).