From: Robert Pluim <rpluim@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: ola.nilsson@gmail.com, 38442@debbugs.gnu.org
Subject: bug#38442: 27.0.50; segmentation fault switching to cairo
Date: Mon, 02 Dec 2019 08:54:59 +0100 [thread overview]
Message-ID: <m236e3uppo.fsf@gmail.com> (raw)
In-Reply-To: <CAAeL0STUXBDkkA94RkSkr3bw+sDtWVt=EaoYqmytFyBVsbGk-A@mail.gmail.com> (Juanma Barranquero's message of "Mon, 2 Dec 2019 00:55:29 +0100")
>>>>> On Mon, 2 Dec 2019 00:55:29 +0100, Juanma Barranquero <lekktu@gmail.com> said:
Juanma> I'm reluctant to filtering it out unconditionally, because the font-backend
Juanma> is something the users can specify for themselves, perhaps to fix some
Juanma> problem with their installation.
Juanma> The "right" fix, I think, would be either:
Juanma> - To filter it out when saving, if it is the default (i.e., '(harfbuzz gdi)
Juanma> on Windows, currently), or
Juanma> - To filter it out when loading, if the saved value is not supported on the
Juanma> running instance of Emacs.
The latter makes sense.
Juanma> The problem is, there's no way to get a list of supported font backends
Juanma> from elisp, there is?
No, but we could add one, or you could compare on load to
(frame-parameter nil 'font-backend)
Robert
next prev parent reply other threads:[~2019-12-02 7:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-30 23:03 bug#38442: 27.0.50; segmentation fault switching to cairo Ola Nilsson
2019-12-01 3:38 ` Eli Zaretskii
2019-12-01 17:28 ` Eli Zaretskii
2019-12-01 23:55 ` Juanma Barranquero
2019-12-02 7:54 ` Robert Pluim [this message]
2019-12-02 8:08 ` Juanma Barranquero
2019-12-02 8:36 ` Eli Zaretskii
2019-12-02 12:57 ` Juanma Barranquero
2019-12-02 16:09 ` Eli Zaretskii
2019-12-02 17:28 ` Juanma Barranquero
2019-12-02 17:48 ` Eli Zaretskii
2019-12-02 18:08 ` Juanma Barranquero
2019-12-02 18:21 ` Juanma Barranquero
2019-12-02 20:27 ` Eli Zaretskii
2019-12-02 20:36 ` Juanma Barranquero
2019-12-04 20:32 ` Ola Nilsson
2019-12-05 3:30 ` Eli Zaretskii
2019-12-02 20:26 ` 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=m236e3uppo.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=38442@debbugs.gnu.org \
--cc=lekktu@gmail.com \
--cc=ola.nilsson@gmail.com \
/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.