Closed belak closed 7 years ago
On a related note, do you think it would be useful to export a function called exec-path-from-shell-maybe-initialize
(or something similar) that automatically performs this check?
Maybe, but that makes me responsible for deciding whose system to run it on, so I've been hesitant to codify these choices: I'd rather the user know what the package does and why they're installing it... I guess the only downside to unnecessarily running the core code is a second or two extra at startup. I'll have a think about it.
Hm good point, maybe it would make more sense if we stuck a "you don't need this if you only use Windows" warning in the readme. I haven't used Linux in a while but I believe gdm is still common at least in older Linuxes, so I would guess most Linux users would still find this useful.
Most display managers don't run in a user shell, as far as I'm aware... so most modern distros should run into this as well. The only time environment variables would be set properly is if you're running startx (or presumably whatever the wayland equivalent is).
Personally I think it's simple enough to do the check myself in my init.el... it's also much more flexible. :)
In an X windows environment (and probably eventually Wayland) you often run into the same problems as on OS X.
Also, I fixed a small typo about "Emacssenvironment" which was more involved than it should be... See https://lists.gnu.org/archive/html/emacs-devel/2012-02/msg00695.html and other messages in that thread. Also, all the documentation appears to use "Emacs's" even though "Emacs'" might seem more logical, so I went with that.