unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Dixon <dixius99@gmail.com>
To: 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: Thu, 5 Dec 2019 20:57:49 -0500	[thread overview]
Message-ID: <4D9D1D29-90AD-4A5C-BC4F-47474B5E110D@gmail.com> (raw)
In-Reply-To: <57FFA40D-A752-445B-8DC1-809F81366255@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 919 bytes --]



> On Dec 5, 2019, at 6:20 AM, Michael Dixon <dixius99@gmail.com> wrote:
> 
> Some more info on this one.
> 
> I’m built my own Emacs from the latest source, and get the same issue.
> 
> One potential problem I’ve read is that having my Documents folder on iCloud could cause a problem, but I don’t do that either.
> 
> I also tried Emacs Mac Port ( https://lists.gnu.org/archive/html/emacs-devel/2019-12/msg00104.html <https://lists.gnu.org/archive/html/emacs-devel/2019-12/msg00104.html>) and got an interesting result:
> 
> File > Open and the toolbar do not cause a crash, however, clicking on the “open a file” link in the splash screen causes a Mac beach ball that I can only solve by forcing a quit.

And adding even more context: I trie downgrading to Mojave, and had no issues with it at all, related to clicking on the Toolbar, File > Open, or the Open a File link on the splash page.

[-- Attachment #2: Type: text/html, Size: 2113 bytes --]

  reply	other threads:[~2019-12-06  1:57 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
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 [this message]
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=4D9D1D29-90AD-4A5C-BC4F-47474B5E110D@gmail.com \
    --to=dixius99@gmail.com \
    --cc=38031@debbugs.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).