From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: harfbuzz 2f72162: Fix crash in the Cairo build Date: Fri, 14 Dec 2018 18:45:50 +0200 Message-ID: <83pnu4f45d.fsf@gnu.org> References: <20181214085417.15440.18845@vcs0.savannah.gnu.org> <20181214085418.6616820538@vcs0.savannah.gnu.org> <831s6kgrtj.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1544805886 29080 195.159.176.226 (14 Dec 2018 16:44:46 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 14 Dec 2018 16:44:46 +0000 (UTC) Cc: ari.roponen@gmail.com, emacs-devel@gnu.org To: Robert Pluim Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Dec 14 17:44:42 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gXqZr-0007QB-99 for ged-emacs-devel@m.gmane.org; Fri, 14 Dec 2018 17:44:39 +0100 Original-Received: from localhost ([::1]:34445 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gXqbx-00085o-SC for ged-emacs-devel@m.gmane.org; Fri, 14 Dec 2018 11:46:49 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56125) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gXqbA-00084f-2r for emacs-devel@gnu.org; Fri, 14 Dec 2018 11:46:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gXqb9-0000ef-8w for emacs-devel@gnu.org; Fri, 14 Dec 2018 11:46:00 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:49632) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gXqb5-0000cd-57; Fri, 14 Dec 2018 11:45:55 -0500 Original-Received: from [176.228.60.248] (port=1345 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1gXqb4-0002pD-LE; Fri, 14 Dec 2018 11:45:55 -0500 In-reply-to: (message from Robert Pluim on Fri, 14 Dec 2018 17:16:46 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:231843 Archived-At: > From: Robert Pluim > Cc: emacs-devel@gnu.org, ari.roponen@gmail.com > Date: Fri, 14 Dec 2018 17:16:46 +0100 > > Aligning ftfont.c and ftcrfont.c is pretty easy. Did you want me to > try to unify xftfont.c in there as well? If that makes sense, i.e. if the commonality seems to justify that, then yes. > Iʼm tempted to get rid of ftxfont.c as well, unless someone is > actually still using that. [1] I think this is a decision for another time. In any case, we cannot just remove it, we need to deprecate it first. We may declare it deprecated now, and perhaps cause its inclusion to trigger some deprecation message during building Emacs. > [1] How many different font backends can we come up with using only 3 > letters? That calls for a Lisp program, no? Thanks.