From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>,Robert Pluim <rpluim@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 10:36:52 +0200 [thread overview]
Message-ID: <22778C0D-D396-45A2-8D53-2D24795A59D3@gnu.org> (raw)
In-Reply-To: <CAAeL0STMvEZTkexqHbXvhB+2hEJbkg5WbQEHHCONEB3NDnJWvw@mail.gmail.com>
On December 2, 2019 10:08:04 AM GMT+02:00, Juanma Barranquero <lekktu@gmail.com> wrote:
> On Mon, Dec 2, 2019 at 8:55 AM Robert Pluim <rpluim@gmail.com> wrote:
>
> > The latter makes sense.
>
> Agreed.
>
> > No, but we could add one,
>
> I think that would be best.
We could do that, but can we first try to envision what would be the use case for keeping a non-default font backend from the previous session? If the frame's font requires that, the new session will use that same backend anyway. I have difficulty imagining any other use case.
IOW, we might be over-engineering here, and just filtering it out should do the job.
next prev parent reply other threads:[~2019-12-02 8:36 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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22778C0D-D396-45A2-8D53-2D24795A59D3@gnu.org \
--to=eliz@gnu.org \
--cc=38442@debbugs.gnu.org \
--cc=lekktu@gmail.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).