From: Kristjon Ciko <kristjoc@ifi.uio.no>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
"66637@debbugs.gnu.org" <66637@debbugs.gnu.org>
Subject: bug#66637: 29.1; Emacs crashes with activating tree-sitter modes
Date: Fri, 20 Oct 2023 11:42:40 +0000 [thread overview]
Message-ID: <4be2a824bf7e4a5dbfe0ae67979168f5@ifi.uio.no> (raw)
In-Reply-To: <m2fs25sf3t.fsf@Pro.fritz.box>
Yeah, I do use exec-path-from-shell in my config. The problem went away with the binary from https://emacsforosx.com/
________________________________________
From: Gerd Möllmann <gerd.moellmann@gmail.com>
Sent: Friday, October 20, 2023 1:33 PM
To: Kristjon Ciko
Cc: Eli Zaretskii; 66637@debbugs.gnu.org
Subject: Re: bug#66637: 29.1; Emacs crashes with activating tree-sitter modes
Kristjon Ciko <kristjoc@ifi.uio.no> writes:
> It seems like this is a MacOS-specific issue; more precisely, a MacOS Sonoma-specific since I did not have this problem before the upgrade.
>
> I reinstalled Emacs using `sudo port install emacs-app` and I found
> out that the issue occurs **ONLY** when Emacs (vanilla Emacs, no
> config files involved) is launched from the Spotlight search, which
> points to /Applications/MacPorts/Emacs.app. Everything works just
> fine if I run emacs from the terminal (`which emacs` =>
> /Applications/MacPorts/Emacs.app/Contents/MacOS/emacs)
>
> Same case with my own config; launching it from terminal seems the way to go.
Have you make sure that Emacs, when started via Spotlight for instance,
has the same environment variables that you have in the shell (PATH for
example)? It doesn't if you don't do something, like using the
exec-path-from-shell package.
prev parent reply other threads:[~2023-10-20 11:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 9:17 bug#66637: 29.1; Emacs crashes with activating tree-sitter modes Kristjon Ciko
2023-10-19 12:57 ` Eli Zaretskii
2023-10-20 11:09 ` Kristjon Ciko
2023-10-20 11:33 ` Gerd Möllmann
2023-10-20 11:42 ` Kristjon Ciko [this message]
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=4be2a824bf7e4a5dbfe0ae67979168f5@ifi.uio.no \
--to=kristjoc@ifi.uio.no \
--cc=66637@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gerd.moellmann@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.