From: Michael Dixon <dixius99@gmail.com>
To: Alan Third <alan@idiocy.org>
Cc: 38031@debbugs.gnu.org, Nathaniel Bass <nw3455@gmail.com>,
Stefan Kangas <stefan@marxist.se>
Subject: bug#38031: 26.3; Trying to invoke the macOS File Open window causes Emacs to crash on macOS Catalina
Date: Fri, 8 Nov 2019 18:17:30 -0500 [thread overview]
Message-ID: <6CCDA5A5-9265-41F1-A7DE-4E8CE0DD4431@gmail.com> (raw)
In-Reply-To: <20191108230811.GC42932@breton.holly.idiocy.org>
I tried a whole variety of distributions. I tried the brew cask (26.3), the emacs-plus formula used for spacemacs (26.3), the prebuilt Emacs for Mac OSX (26.3), homebrew-emacs-head (another brew formula, both 26.3 and 27.0.50), and now the one I just built (I tried both with and without your patch, both 27.0.5.0, since that’s what I get with master).
> On Nov 8, 2019, at 6:08 PM, Alan Third <alan@idiocy.org> wrote:
>
> On Fri, Nov 08, 2019 at 04:33:23PM -0500, Michael Dixon wrote:
>> Thanks so much everyone.
>>
>> I was able to build from source. I had the same libxml/tree.h error
>> as Nathaniel.
>>
>> The crash error I got was the same, but before I waste any more of
>> your time, I wanted to share that I set up a Catalina virtual
>> machine and installed via brew cask and did NOT get the crash, even
>> without providing full disk access to ruby, Emacs.app, etc.
>>
>> This leads me to believe it my problem isn’t specific to Emacs, but
>> rather something else unique to my environment, though I can’t think
>> of what that might be.
>
> Where did you get the original copy that did crash? Was that also a
> brew cask install?
>
> Are they both Emacs 26?
>
> --
> Alan Third
next prev parent reply other threads:[~2019-11-08 23:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-02 10:19 bug#38031: 26.3; Trying to invoke the macOS File Open window causes Emacs to crash on macOS Catalina Michael Dixon
2019-11-03 20:39 ` Alan Third
2019-11-03 21:02 ` Michael Dixon
2019-11-04 20:06 ` Alan Third
2019-11-08 0:39 ` Stefan Kangas
2019-11-08 5:06 ` Nathaniel Bass
2019-11-08 19:47 ` Alan Third
2019-11-08 21:33 ` Michael Dixon
2019-11-08 23:08 ` Alan Third
2019-11-08 23:17 ` Michael Dixon [this message]
2020-01-14 21:39 ` Alan Third
2020-01-15 3:00 ` Michael Dixon
2020-01-15 19:00 ` Alan Third
2020-01-15 21:48 ` Michael Dixon
2020-01-17 18:53 ` Alan Third
2020-01-17 23:49 ` Michael Dixon
2020-01-18 15:22 ` Alan Third
2020-01-18 16:39 ` Michael Dixon
2020-01-18 20:50 ` Alan Third
2020-01-24 10:00 ` Alan Third
2019-11-08 7:02 ` Andrii Kolomoiets
2019-12-05 11:20 ` Michael Dixon
2019-12-06 1:57 ` Michael Dixon
2019-12-19 7:37 ` bug#38031: Same error Lars Hovdan Molden via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=6CCDA5A5-9265-41F1-A7DE-4E8CE0DD4431@gmail.com \
--to=dixius99@gmail.com \
--cc=38031@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=nw3455@gmail.com \
--cc=stefan@marxist.se \
/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).