From: Alan Third <alan@idiocy.org>
To: Michael Dixon <dixius99@gmail.com>
Cc: 38031@debbugs.gnu.org
Subject: bug#38031: 26.3; Trying to invoke the macOS File Open window causes Emacs to crash on macOS Catalina
Date: Mon, 4 Nov 2019 20:06:38 +0000 [thread overview]
Message-ID: <20191104200638.GA38578@breton.holly.idiocy.org> (raw)
In-Reply-To: <435F198B-3771-4E70-9A5F-F263AC34B2A0@gmail.com>
On Sun, Nov 03, 2019 at 04:02:39PM -0500, Michael Dixon wrote:
> Thanks Alan. I might be a little over my head here, as I’m not sure
> how to apply a patch. I presume I would have to build from source...
Yes, you would. It’s not very hard if you’ve got git installed. I can
talk you through it. Alternatively we can try to find someone else
running Catalina, there should be a few Emacs devs/users who’ve
upgraded around here somewhere.
--
Alan Third
next prev parent reply other threads:[~2019-11-04 20:06 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191104200638.GA38578@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=38031@debbugs.gnu.org \
--cc=dixius99@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 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.