From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Stefan Kangas Newsgroups: gmane.emacs.devel Subject: Re: master d8da850: Document cairo-related fallout to font-backend settings Date: Tue, 21 Jan 2020 00:12:22 +0100 Message-ID: References: <20200120162048.23970.80216@vcs0.savannah.gnu.org> <20200120162050.08A5421148@vcs0.savannah.gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="46163"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Emacs developers To: Robert Pluim Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jan 21 00:13:44 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1itgEp-000Bxn-TV for ged-emacs-devel@m.gmane-mx.org; Tue, 21 Jan 2020 00:13:43 +0100 Original-Received: from localhost ([::1]:45532 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1itgEo-0003K4-UQ for ged-emacs-devel@m.gmane-mx.org; Mon, 20 Jan 2020 18:13:42 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59944) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1itgDj-0002J3-GI for emacs-devel@gnu.org; Mon, 20 Jan 2020 18:12:36 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1itgDi-0000Jf-Dm for emacs-devel@gnu.org; Mon, 20 Jan 2020 18:12:35 -0500 Original-Received: from mail-pl1-f175.google.com ([209.85.214.175]:41129) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1itgDi-0000J1-8J for emacs-devel@gnu.org; Mon, 20 Jan 2020 18:12:34 -0500 Original-Received: by mail-pl1-f175.google.com with SMTP id t14so460473plr.8 for ; Mon, 20 Jan 2020 15:12:34 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DTZwlixZB+NPs+gisce14IxeC2Fv9aZzC2yFRegMJJw=; b=p2WZe/B8q1XyDb5TOHgbJy0m22qWul4LwicQ6F4O/QLgS/t/xfKnzQpGd/voHC4nSX IencYbmHqZibb8IBP4i1LIClDPtzNSSsTq2FjwHxpLu53IxMpNthCfcKm674/yhkhAjT xzs5YtqMTqKRMoXCfidyBqX3rwPq4fh8gyhCNxQ7XEc9QF+ukQ7LVw28+0MAhEMcrITo hmYVgTzPt15dy+I9ldOSWIo5a+FtOBNzF6WgbMLhLyFqNpVA+Kit8I01nx1T0ecsd4TT vuMBwdyfO7BSK1Yl2NxfKyYHV8pSrK0GxiHkV5UsTsVZpOqb2qoGFSSIkuHz4FObDDIY O9Lg== X-Gm-Message-State: APjAAAXe+VrzrCyXhLgUyAerkxckzNXoeC2fFfp1tKQJ1X8czTbPpMu9 ax4Qhd1CRY8oaAIukjU964MjgiEtWHPOXJo96prgPWGe X-Google-Smtp-Source: APXvYqw0E++5xiR8FDyahYMUfEE7rNkq+BibF7mGI15sB1X9BlXA3468bw7wObKRtiWV2FXEE8F7jB867+wqXv/SMgI= X-Received: by 2002:a17:90a:b008:: with SMTP id x8mr1705303pjq.106.1579561953180; Mon, 20 Jan 2020 15:12:33 -0800 (PST) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 209.85.214.175 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:244446 Archived-At: Robert Pluim 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