build-emacs-macos VS exec-path-from-shell

Though I don't love Ventura, running Emacs on MacOS has never really been a problem for me. It's also very easy to build Emacs. You can use this shell script if you like: https://github.com/mclear-tools/build-emacs-macos. I also list there a bunch of other build scripts from other users. Just as easy as homebrew really, with a lot more control (e.g. you can build whatever version of Emacs you like, at least back to 22).

You might find this shell script for building emacs useful. https://github.com/mclear-tools/build-emacs-macos

I build emacs myself from the master branch on an M1 and Monterey and don't see this issue. So it might be something either with your config or with that specific build setup.

Here's the build script that I use. It is pretty dead simple. https://github.com/mclear-tools/build-emacs-macos

Hi all -- I've put a repo on github for building emacs on macos. There are several other such scripts available, but I've tried to make mine as simple to understand (I'm not a programmer) as possible (or as possible for me...). It currently works well for me but YMMV. Of course, I realize that there are a million ways to shave this yak, so I'd be curious if anyone has suggestions for improvement (though I'm also looking to keep things as simple as possible). I hope this might be of some use to people.

I'm not a Mac user, but FWIW from what I've seen over time https://github.com/purcell/exec-path-from-shell is a must when using Emacs on a Mac. I don't know why this is, but I'm guessing there's something unusually difficult about setting up the desktop session environment when using OSX, and users end up needing to resort to this. Hopefully that helps if you run into environment issues.

Check out the package exec-path-from-shell

This package may help: https://github.com/purcell/exec-path-from-shell

All my path related problems with emacs were solved with the package: https://github.com/purcell/exec-path-from-shell

For one, do you use the exec-path-from-shell package? That should do the trick for path issues when using Emacs vterm. It's likely when emacs is loading it's not correctly loading in the $PATH values from your system. You can check the path values in emacs by checking the value of exec-path.

I would like to use SPC p p RET to switch projects, change working directories to trigger exec-path-from-shell, and open Treemacs with the only active project being the selected one.

I suspect the Emacs.app package has some misconfigured paths that are unable to find my libgccjit library, which I've installed via homebrew. I've tried experimenting with exec-path-from-shell to ensure Emacs is aware of my shell paths, but to no avail.