(No subject)

[slb zetrov <zetrov.slb@yandex.com>]

Hi,

tl;dr: By actually trying to implement the idea, I just realized that the idea
is flawed, and ‘exec-path-from-shell’ is necessary.

---

Thanks for pointing out ‘exec-path-from-shell’ can work on other situations and
‘parsenv’ to sync two versions of paths.

Problem is that users might have a lot of staffs inside ‘.bashrc’
‘.bash_profile’ and ‘.zshrc’, as a result, an embedded script just cannot be
simply imported to a shell session to figure the PATH.

The only way to properly get the PATH is to let the shell print the PATH and
read the results which is exactly what ‘exec-path-from-shell’ do.

---

Technically, Emacs.app and command-line Emacs "lives" in two different worlds.
Command-line Emacs lives in at a Unix environment. Emacs.app lives in macOS's
‘launchd‘ environment which is part of the desktop environment and it has a
specific set of env variables.

I guess the reason why some Linux desktop environments didn't provide right
PATH is they override the env variables or use a different technique to launch
applications. It might not be a bug but a feature.

---

Thanks!