Rainer M Krug <rai...@krugs.de> writes: > Nick Dokos <ndo...@gmail.com> writes: > >> Rainer M Krug <rai...@krugs.de> writes: >> >>> Fatma Başak Aydemir <aydemi...@gmail.com> writes: >>> >>>> I do not know the reasons but I had the same problem in the past on OS X. >>> >>> In from Yosemite onwards, programs started from the finder / spotlight / >>> gui (however you call this) do *not* inherit from the .bashrc >>> anymore. This caused many problems. >> >> I can understand not inheriting from .bashrc: shells should only use >> that for interactive initializations (aliases and such). > > Right. > >> >> $HOME/.profile however is another matter: it is read by a login shell >> (in a non-graphical or console environment) and so its settings are >> inherited by everybody started from that login shell: that's where env >> variables are supposed to be defined and exported. Desktop environments >> have to go to some lengths to read it and initialize things but as I >> mentioned in my previous message, they *do* do that (on Linux - although >> the mechanism varies by distro, hence the "mess" comment). >> >> If OS X does not use $HOME/.profile to initialize the environment of programs >> (even in the graphical enviroment), that seems to me to be a serious >> bug. > > Aparently it is not. >
They do things differently at Apple: http://stackoverflow.com/questions/135688/setting-environment-variables-in-os-x has some answers: imo, the launchd.conf method should be avoided (it applies to every user), but the environment.plist method (whatever that is) seems to be the right solution - and although it did not work for Spotlight-launched applications (whatever Spotlight is) in 10.5, it apparently works in 10.6 or later. As you can imagine, all my knowledge comes from that article and references therein: take it with the appropriate grain of salt. Anyway, this is very far from org-mode, so maybe it should be pursued in a different forum. -- Nick
