Proposal to let Emacs to properly capture $PATH on macOS .

Proposal to let Emacs to properly capture $PATH on macOS .

[slb zetrov]

[-- Attachment #1: Type: text/html, Size: 2447 bytes --]

Re: Proposal to let Emacs to properly capture $PATH on macOS .

[Stefan Monnier]

> The current solution for Emacs users is to install a completely avoidable and unnecessary package
> (exec-path-from-shell) https://github.com/purcell/exec-path-from-shell/

Side note: this same problem also affects Emacs launched from the
desktop environment on GNU/Linux, and an approach like
`exec-path-from-shell` can also be used to work around the problem.


        Stefan

Re: Proposal to let Emacs to properly capture $PATH on macOS .

[Richard Stallman]

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

There is legitimate support for Emacs on MacOS, so you're welcome to report
problems and support fixes in that case.

The one thing you should not do is advocate implementing any Emacs
feature for MacOS (or Windows) if Emacs doesn't have an equivalent
feature on GNU/Linux.  Our motto is, "It runs best on GNU/Linux",
and we have to make sure that is true.

-- 
Dr Richard Stallman
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)

Re: Proposal to let Emacs to properly capture $PATH on macOS .

[Vasilij Schneidermann]

[-- Attachment #1: Type: text/plain, Size: 647 bytes --]

> The current solution for Emacs users is to install a completely
> avoidable and unnecessary package (exec-path-from-shell)
> https://github.com/purcell/exec-path-from-shell/

The parsenv package [1] provides a simpler approach to solve this problem,
instead of launching a process from the user's shell or parsing their shell
configuration files, programs parse a so-called dotenv file which just contains
environment variable mappings.  This is done by a multitude of software
already, mostly to simplify deployment tasks where configuration is commonly
performed via environment variables.

Vasilij

[1]: https://github.com/articuluxe/parsenv

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: Proposal to let Emacs to properly capture $PATH on macOS .

[Alan Third]

On Fri, May 22, 2020 at 10:20:12AM +0200, Vasilij Schneidermann wrote:
> > The current solution for Emacs users is to install a completely
> > avoidable and unnecessary package (exec-path-from-shell)
> > https://github.com/purcell/exec-path-from-shell/
> 
> The parsenv package [1] provides a simpler approach to solve this problem,
> instead of launching a process from the user's shell or parsing their shell
> configuration files, programs parse a so-called dotenv file which just contains
> environment variable mappings.  This is done by a multitude of software
> already, mostly to simplify deployment tasks where configuration is commonly
> performed via environment variables.

macOS already provides a similar set up, but it's barely configurable.
For example:

breton:/Users/alan>/usr/libexec/path_helper
PATH="/usr/local/bin:/usr/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Users/alan/.local/bin";
export PATH;

It builds the path from /etc/paths and the files in /etc/paths.d, and
anything else that's already in the environment.

It insists on setting its own order, though. It's a massive pain, but
that's how all the shells on macOS build their initial $PATH.
-- 
Alan Third