all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Perry Smith <pedzsan@icloud.com>
To: emacs-devel@gnu.org
Subject: Emacs on macOS
Date: Thu, 31 Mar 2022 17:52:01 -0500	[thread overview]
Message-ID: <0CBBB7FB-1D2A-46C7-90C2-8664913B0E29@icloud.com> (raw)

I’m not sure if this is the best list for this:

I have an M1 Max (arm based / Apple Silicon) MacBook Pro with the latest macOS of 12.3.  I also have Homebrew installed with about 27 items installed.  I have not installed any libraries just to have the libraries but have only installed commands.

In any case, building emacs was the usual drop dead easy: ./configure; make ; make install

The one tiny hiccup is you need to do:

sudo xattr -rds com.apple.quarantine Emacs.app

to get the Emacs.app to launch.  The GNU Emacs web site points users to EmacsForMacOSX.  EmacsForMacOSX has problems opening files in ~/Desktop, ~/Downloads, and ~/Documents if the user is using Apple’s cloud solution.  My belief is that these problems come up because the EmacsForMacOSX starts with a ruby script which eventually launches the emacs binary.  I believe macOS at that point no longer trusts the executable — which seems totally reasonable.

Now… for my question:

When emacs dies on a Mac (as with any application), a GUI window pops up with a place to enter some text and a button that says “Report”.  When the button is hit, something sends something somewhere but I doubt if anything is sent to the emacs-bug list.  The window appears to have some pretty useful information like stack trace for each thread, etc.

The flip side is, report-emacs-bug also has a lot of useful information.  My question is what is the preferred or most effective way to combine these two sources of information?  One choice is to copy what is in the macOS window and paste it into the email that report-emacs-bug creates.  Another choice might be to attach a file that macOS creates when an application dies but I don’t know where that file lives.

Thank you for your time
Perry




             reply	other threads:[~2022-03-31 22:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 22:52 Perry Smith [this message]
2022-04-01  7:55 ` Emacs on macOS Po Lu
2022-04-01 10:47   ` Eli Zaretskii
2022-04-03  7:04 ` [Add xattr to the INSTALLATION file?] (was: Emacs on macOS) Uwe Brauer
2022-04-03 13:45 ` Emacs on macOS Alan Third
2022-04-03 17:20 ` [script vs ICon: latex binaries not found] (was: Emacs on macOS) Uwe Brauer
     [not found] ` <m2k0c6ozgm.fsf@mat.ucm.es>
2022-04-04  3:05   ` chad
2022-04-04  8:38     ` Tim Cross
2022-04-04 20:06       ` [script vs ICon: latex binaries not found] Uwe Brauer
2022-04-04 20:03     ` Uwe Brauer

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=0CBBB7FB-1D2A-46C7-90C2-8664913B0E29@icloud.com \
    --to=pedzsan@icloud.com \
    --cc=emacs-devel@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 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.