From: "Vinicius José Latorre" <viniciusjl@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 39865@debbugs.gnu.org
Subject: bug#39865: 28.0.50; Emacs crash
Date: Fri, 6 Mar 2020 14:20:42 -0300 [thread overview]
Message-ID: <CAEt1T7dF_=aPWQrryWUMJRbsOVxscuOb6fC-QudTwxGmWGNWRg@mail.gmail.com> (raw)
In-Reply-To: <837dzyuf20.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
> OK, then the crash is a known problem: you cannot change the font
> backend once the session started, you can only do that in X resources.
> Previously, XFT was your original backend, but now it's HarfBuzz.
I think that emacs should be more robust about this and do not crash for
any bad value.
> Why are you doing this? What happens/doesn't work if you remove this
> line?
Well, I use emacs since 1992, I don't remember why I set this.
Removing this line all works like a charming.
On Fri, Mar 6, 2020 at 4:18 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Vinicius José Latorre <viniciusjl@gmail.com>
> > Date: Thu, 5 Mar 2020 19:21:22 -0300
> > Cc: 39865@debbugs.gnu.org
> >
> > I found this line in my ~/.emacs that causes the crash:
> >
> > (push '(font-backend xft x) default-frame-alist)
>
> OK, then the crash is a known problem: you cannot change the font
> backend once the session started, you can only do that in X resources.
> Previously, XFT was your original backend, but now it's HarfBuzz.
>
> Why are you doing this? What happens/doesn't work if you remove this
> line?
>
[-- Attachment #2: Type: text/html, Size: 1681 bytes --]
next prev parent reply other threads:[~2020-03-06 17:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 1:39 bug#39865: 28.0.50; Emacs crash Vinicius José Latorre
2020-03-02 8:11 ` Eli Zaretskii
2020-03-05 1:03 ` Vinicius José Latorre
2020-03-05 22:21 ` Vinicius José Latorre
2020-03-06 7:18 ` Eli Zaretskii
2020-03-06 17:20 ` Vinicius José Latorre [this message]
2020-03-06 17:24 ` Vinicius José Latorre
2020-03-06 17:53 ` Eli Zaretskii
2020-03-10 14:29 ` Robert Pluim
2020-03-10 14:52 ` Eli Zaretskii
2020-03-10 14:54 ` Vinicius José Latorre
2020-03-10 15:20 ` Robert Pluim
2020-03-10 19:03 ` Vinicius José Latorre
2020-03-11 7:33 ` Robert Pluim
2020-03-11 20:45 ` Vinicius José Latorre
2020-03-12 9:39 ` Robert Pluim
2020-03-10 15:15 ` Robert Pluim
2020-03-11 16:58 ` Eli Zaretskii
2020-03-12 9:33 ` Robert Pluim
2020-03-12 10:25 ` Robert Pluim
2020-03-13 0:44 ` Vinicius José Latorre
2020-03-13 9:35 ` Robert Pluim
2020-03-13 14:09 ` Eli Zaretskii
2020-03-13 15:09 ` Robert Pluim
2020-03-17 10:16 ` Robert Pluim
2020-03-17 15:15 ` Eli Zaretskii
2020-03-17 16:06 ` Robert Pluim
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='CAEt1T7dF_=aPWQrryWUMJRbsOVxscuOb6fC-QudTwxGmWGNWRg@mail.gmail.com' \
--to=viniciusjl@gmail.com \
--cc=39865@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).