From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: pegzmasta@member.fsf.org, 35725@debbugs.gnu.org
Subject: bug#35725: 26.2; Fatal error 11: Segmentation fault; Crash on: (find-file "any.svg")
Date: Tue, 14 May 2019 09:16:43 -0700 [thread overview]
Message-ID: <25f88d44-9211-8d48-7b01-28c6ccfba88a@cs.ucla.edu> (raw)
In-Reply-To: <83ftph9g4r.fsf@gnu.org>
On 5/14/19 9:04 AM, Eli Zaretskii wrote:
>> From: Lars Ingebrigtsen <larsi@gnus.org>
>> Date: Tue, 14 May 2019 03:58:04 -0400
>> Cc: 35725@debbugs.gnu.org, Paul Eggert <eggert@cs.ucla.edu>
>>
>> But didn't Emacs get native scaling support recently?
> Yes, you can see that in Emacs 27.
Yes, just to make it clear, I don't recommend backporting the
no-ImageMagick-by-default patch to Emacs 26 since it lacks native scaling.
Lars, if barracudacentral.org is blacklisting you then there's a good
chance other people aren't getting your email either. You can request
removal by visiting here:
http://www.barracudacentral.org/rbl/removal-request
In the meantime you may be able to work around the problem by sending
email to eggert@gnu.org.
next prev parent reply other threads:[~2019-05-14 16:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 22:40 bug#35725: 26.2; Fatal error 11: Segmentation fault; Crash on: (find-file "any.svg") Michael Pagan
2019-05-14 1:04 ` Paul Eggert
2019-05-14 1:21 ` Glenn Morris
2019-05-14 3:59 ` Michael Pagan
2019-05-14 7:58 ` Lars Ingebrigtsen
2019-05-14 8:00 ` Lars Ingebrigtsen
2019-05-14 16:04 ` Eli Zaretskii
2019-05-14 16:16 ` Paul Eggert [this message]
2019-05-15 0:49 ` Lars Ingebrigtsen
2019-05-15 18:45 ` Alan Third
2019-05-16 3:47 ` Lars Ingebrigtsen
2019-05-14 6:08 ` Paul Eggert
2019-05-15 0:42 ` Glenn Morris
2019-05-18 17:12 ` Paul Eggert
2019-05-15 4:07 ` Michael Pagan
2019-05-15 4:22 ` Lars Ingebrigtsen
2019-05-14 1:16 ` Noam Postavsky
2019-05-14 15:25 ` 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=25f88d44-9211-8d48-7b01-28c6ccfba88a@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=35725@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=pegzmasta@member.fsf.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 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.