unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Michael Dixon <dixius99@gmail.com>
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: Sat, 18 Jan 2020 20:50:24 +0000	[thread overview]
Message-ID: <20200118205024.GA68412@breton.holly.idiocy.org> (raw)
In-Reply-To: <5A27AE46-34F1-4D41-A61E-5B75AA2917A5@gmail.com>

On Sat, Jan 18, 2020 at 11:39:02AM -0500, Michael Dixon wrote:
> Good news:
> 
> I grepped the source tree, and I noticed EmacsSavePanel mentioned in
> what I believe were leftovers from previous builds. Files with names
> like emacs-27.0.60.1, emacs-27.0.60.2, etc., all with modify dates
> that seemed to align up with dates I would have done a make install.
> I tried cleaning them up manually (e.g. deleting them), and I was
> left with the only mentions of EmacsSavePanel being in the change
> log.
> 
> I rebuilt again and this time Save As no longer causes a crash.
> 
> I’m sorry Alan for making this such a fiasco.

Not a problem, I’m just happy it was an easy fix. :)

I’ll wait for a bit to see if anyone pipes up with opinions on whether
it’s worth keeping these classes on systems where they might work.

Thanks!
-- 
Alan Third





  reply	other threads:[~2020-01-18 20:50 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 [this message]
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=20200118205024.GA68412@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=38031@debbugs.gnu.org \
    --cc=dixius99@gmail.com \
    --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).