exec-path-from-shell VS compat

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.

With the Compat library you can use define-keymap right away in your packages. See also my post about Compat.

Exactly, I think printing a loud warning is a perfectly acceptable solution. The note should ideally tell the user to ensure that dependencies are met. It makes sense to teach users a little better about the limitations of Straight or Elpaca with respect to dependency handling since I've seen many reports across the ecosystem where people didn't properly update dependencies. I usually bump dependencies when I really need new functionality. In particular with our Compat package, versions are meaningful and should be respected.

Compat co-maintainer here. Thank you for writing this post! One minor correction: Compat supports Emacs 24.4 and newer. Please link to the upstream repository at https://github.com/emacs-compat/compat instead of the Straight mirror, since the mirror does not preserve the Git history.

As /u/usaoc said, ensure-list can be used for this purpose - I use it all the time in my packages. I recommend to take advantage of the Compat package from GNU ELPA, such that you can use all new Emacs APIs even in packages targeting older Emacs versions. I am the maintainer of Compat. See also https://www.reddit.com/r/emacs/comments/10iep0o/compat_29130/ for more background.

I released version 29.1.3.0 of Compat, the Elisp forwards-compatibility library on GNU ELPA. This library may be interesting for you, if you want to use newer Emacs developments in your packages without breaking backward compatibility with older Emacs versions.

I updated some packages which included updating the dependency compat.el to 28.1.2.0