unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: "Vinicius José Latorre" <viniciusjl@gmail.com>
Cc: 39865@debbugs.gnu.org
Subject: bug#39865: 28.0.50; Emacs crash
Date: Wed, 11 Mar 2020 08:33:58 +0100	[thread overview]
Message-ID: <m28sk7cpll.fsf@gmail.com> (raw)
In-Reply-To: <CAEt1T7cjicCgi58XR5PA7BGQBNU-cRRm_Qj4idkR3BNH67JCRQ@mail.gmail.com> ("Vinicius José Latorre"'s message of "Tue, 10 Mar 2020 16:03:12 -0300")

>>>>> On Tue, 10 Mar 2020 16:03:12 -0300, Vinicius José Latorre <viniciusjl@gmail.com> said:

    >> I donʼt remember seeing: was your emacs built with cairo or with xft?
    >> With or without HarfBuzz? Because I canʼt get an xft+hb build to
    >> crash when switching the font-backend to 'xft'.

    Vinicius> The line below in my ~/.emacs was crashing emacs at start time.

    Vinicius> (push '(font-backend xft x) default-frame-alist)

    Vinicius> Without the line above, all works right.

    Vinicius> If emacs is started with -Q and then loading ~/.emacs with the line above
    Vinicius> also works right, the problem is at starting time with that line.

This we knew, the question is about how your emacs was built. Could
you show us your value of 'system-configuration-features', that will
tell us all we need to know about HarfBuzz etc.

Thanks

Robert





  reply	other threads:[~2020-03-11  7:33 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
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 [this message]
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=m28sk7cpll.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=39865@debbugs.gnu.org \
    --cc=viniciusjl@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).