From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.bugs Subject: bug#38442: 27.0.50; segmentation fault switching to cairo Date: Mon, 2 Dec 2019 19:08:13 +0100 Message-ID: References: <83tv6kn2ap.fsf@gnu.org> <83sgm4lzup.fsf@gnu.org> <22778C0D-D396-45A2-8D53-2D24795A59D3@gnu.org> <83r21mlnen.fsf@gnu.org> <83d0d6liuc.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000a018f30598bc78de" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="198529"; mail-complaints-to="usenet@blaine.gmane.org" Cc: rpluim@gmail.com, ola.nilsson@gmail.com, 38442@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Dec 02 19:09:13 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1ibq8F-000pV5-II for geb-bug-gnu-emacs@m.gmane.org; Mon, 02 Dec 2019 19:09:11 +0100 Original-Received: from localhost ([::1]:42752 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ibq8E-00072A-Aa for geb-bug-gnu-emacs@m.gmane.org; Mon, 02 Dec 2019 13:09:10 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58437) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ibq87-0006yZ-Cq for bug-gnu-emacs@gnu.org; Mon, 02 Dec 2019 13:09:04 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ibq86-0002Cm-6N for bug-gnu-emacs@gnu.org; Mon, 02 Dec 2019 13:09:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:32933) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ibq86-0002CZ-3F for bug-gnu-emacs@gnu.org; Mon, 02 Dec 2019 13:09:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1ibq85-0003wB-Sv for bug-gnu-emacs@gnu.org; Mon, 02 Dec 2019 13:09:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Juanma Barranquero Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 02 Dec 2019 18:09:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 38442 X-GNU-PR-Package: emacs Original-Received: via spool by 38442-submit@debbugs.gnu.org id=B38442.157531013715125 (code B ref 38442); Mon, 02 Dec 2019 18:09:01 +0000 Original-Received: (at 38442) by debbugs.gnu.org; 2 Dec 2019 18:08:57 +0000 Original-Received: from localhost ([127.0.0.1]:38906 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ibq80-0003vn-Dw for submit@debbugs.gnu.org; Mon, 02 Dec 2019 13:08:57 -0500 Original-Received: from mail-qk1-f193.google.com ([209.85.222.193]:46334) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ibq7y-0003vV-91 for 38442@debbugs.gnu.org; Mon, 02 Dec 2019 13:08:54 -0500 Original-Received: by mail-qk1-f193.google.com with SMTP id f5so384908qkm.13 for <38442@debbugs.gnu.org>; Mon, 02 Dec 2019 10:08:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rySaSmFXyR7ic/05+rwxXaX0FTQRdYkQkQbBFQkLuDM=; b=rvEqe+kCNqZZOetd8p3BhwJrZr6hhHgbSVk1uR4cRpEhUCZJjXEkGwBAbBaaslV9gr Z1+Rc/pUvat1/AkeQW+SmiBagqFusLL7XhMlkjsWe7sR3KlODuuXC7zwFqoNOTz902tM PJByHuVRi8eqwaDEvcbS/x/gTQzBGPDZtU+dGDDiS/sX+c2GzjuYe9hD+j5hl/3oncAa t4yDVAZEpJsfXBB0pHyk1XGG/8v91lohAVqKDfqB0Gba+BKYFtNi7+KNoNYLobKna0Mg xosHN0Ane2S8fGuXG048tMn4xtVZbcbA6fpG7z6H5dc+LkZBTWLbGBbY1J+EncdodXU4 gsNw== 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=rySaSmFXyR7ic/05+rwxXaX0FTQRdYkQkQbBFQkLuDM=; b=YhsmmxguP1LDMVelDFxUaIfjYpriBF/XTZIbo55fJJgiwqZRA6wfnnD85OuHVikxFC dNYur71zPbVVn9/7ADgV9dx9xfHiUP095Q0lpM5TSH7uT96HpCMDpKnK8u1InFqcuWcE ZdksEsJ2bDg6IRdurx+m2y/2AZdi5OsUUI9O1OII5VFFzLkhGEGYMl59znrnNDpgQEmx kd9k04uGZ2CNw7Y3zBhtpl13pkniSLAVb0pCGXh7A4Ka/uMLgLvBZtVi7WrLrBq6F8uF /J94nRWrSNrh8dlHiWjSXLCebVYc4d+SX1NBzicCx14+bk6Pu+XvavnX/tJjEvVUpBZE kRwg== X-Gm-Message-State: APjAAAXgBMnIS5/ssdst4GTGgeQf4QhaHAwsYAA68Za7d10xAVJrwB2E WKUuSUoX2ThSAnj4wfLPYZIbShaVvuw0DtRS/F0= X-Google-Smtp-Source: APXvYqyFG1udgxKZ7OhwpgOtbesfdKdgQAk947VVtQle4sPXo+V3QD01Zm3GwbD6GAhxC562ugZ2gu/DekDXS71anD8= X-Received: by 2002:a37:8505:: with SMTP id h5mr33189qkd.281.1575310128583; Mon, 02 Dec 2019 10:08:48 -0800 (PST) In-Reply-To: <83d0d6liuc.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:172779 Archived-At: --000000000000a018f30598bc78de Content-Type: text/plain; charset="UTF-8" On Mon, Dec 2, 2019 at 6:48 PM Eli Zaretskii wrote: > The uniscribe backend will not be used unless Emacs is started with it > being in the list of backends to register. That's what I thought. > Every font that can use Uniscribe can also use HarfBuzz. So this is > not a problem, and users have no reason to wish to use Uniscribe when > they restore their sessions. That's an argument to remove support for Uniscribe. I imagine that, if we haven't done that, it's likely because there could be some problematic font that would behave better with Uniscribe than Harfbuzz, isn't it? > Moreover, unless Emacs is started with Uniscribe (via the -xrm > command-line switch, or via the Registry), it will be unable to use > Uniscribe even if we tell it via the frameset. Again, that was my understanding. All in all, I think I would prefer to keep font-backend and filter it out on restoring when/if necessary; but I don't have a compelling use case, so I'll just filter it out entirely. We can always change it later if the need arises. I'll commit it ASAP. Thanks, Juanma --000000000000a018f30598bc78de Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Mon, Dec 2, 2019 at 6:48 P= M Eli Zaretskii <eliz@gnu.org> wr= ote:

> The uniscribe backend will not be used unless Emacs is sta= rted with it
> being in the list of backends to register.

That= 's what I thought.

> Every font that can use Uniscribe can al= so use HarfBuzz.=C2=A0 So this is
> not a problem, and users have no = reason to wish to use Uniscribe when
> they restore their sessions.
That's an argument to remove support for Uniscribe. I imagine tha= t, if we
haven't done that, it'= s likely because there could be some problematic
font that would behave better with Uniscribe than Harfbuzz,= isn't it?

> Moreover, unless Emacs is started with Uniscribe= (via the -xrm
> command-line switch, or via the Registry), it will b= e unable to use
> Uniscribe even if we tell it via the frameset.
<= br>Again, that was my understanding.

All in all, I think I would pre= fer to keep font-backend and filter it out
on restoring when/if necessary; but I don't have a compelling= use case,
so I'll just filte= r it out entirely. We can always change it later if the
need arises.

I'll commit it ASAP.

= Thanks,

=C2=A0 =C2=A0 Juanma
--000000000000a018f30598bc78de--