From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Robert Pluim <rpluim@gmail.com>,
ola.nilsson@gmail.com, 38442@debbugs.gnu.org
Subject: bug#38442: 27.0.50; segmentation fault switching to cairo
Date: Mon, 2 Dec 2019 13:57:42 +0100 [thread overview]
Message-ID: <CAAeL0SQ=UU97xs6MixHv8qEK1QWwtzUpC7YyOsP7UmDhW_BOnQ@mail.gmail.com> (raw)
In-Reply-To: <22778C0D-D396-45A2-8D53-2D24795A59D3@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 492 bytes --]
On Mon, Dec 2, 2019 at 9:36 AM Eli Zaretskii <eliz@gnu.org> wrote:
> If the frame's font requires that, the new session will use that same
backend anyway.
Is that so? I thought there could be problems with some fonts that Emacs
wouldn't know to
solve. Or do you mean that the user will have set the font backend in
default-frame-alist?
> IOW, we might be over-engineering here, and just filtering it out should
do the job.
Well, that's a one-line change (plus rebuilding the autoloads).
[-- Attachment #2: Type: text/html, Size: 1036 bytes --]
next prev parent reply other threads:[~2019-12-02 12:57 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
2019-12-02 8:08 ` Juanma Barranquero
2019-12-02 8:36 ` Eli Zaretskii
2019-12-02 12:57 ` Juanma Barranquero [this message]
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='CAAeL0SQ=UU97xs6MixHv8qEK1QWwtzUpC7YyOsP7UmDhW_BOnQ@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=38442@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ola.nilsson@gmail.com \
--cc=rpluim@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.