On Feb 1, 2011, at 02:48, Peter Dyballa wrote:
>
> Am 01.02.2011 um 01:07 schrieb Jeremy Huddleston:
>
>>> Why did it work before, one week ago, to supply all X clients with a proper
>>> environment?
>>
>> Probably because a week ago you weren't launching X11.app from launchd. You
>> probably launched it yourself.
>
> I am clicking on the X11 icon in Dock. Is this by myself and without launchd?
Clicking on the X11 icon in Dock *will* get you your environment.plist settings.
Launcing 'xterm' from Terminal.app *won't*.
>>> Why is the situation of Mac OS X 10.4, Tiger, back?
>>
>> This is a really general question. What about Tiger is back?
>
> In Tiger, X11 either did not inherit or did not pass (or did both) the
> environment set by ~/.MacOSX/environment.plist.
Huh... odd.
>>> How can I make launchd supply a reasonable environment to its "clients"?
>>
>> You can't get it to use environment.plist. You probably want to set stuff
>> up in ~/.profile
>
> There I have:
>
> PATH=`defaults read "${HOME}/.MacOSX/environment" PATH`
> MANPATH=`defaults read "${HOME}/.MacOSX/environment" MANPATH`
> INFOPATH=`defaults read "${HOME}/.MacOSX/environment" INFOPATH`
> export INFOPATH MANPATH PATH
>
> I don't see for example INFOPATH not at all...
>
>>
>>> Or do I need to augment each of the ~/.xinitrc.d/* scripts with environment
>>> settings?
>>
>> That would work too.
>>
>>> How would XQuartz know to lookup X clients in /opt/local/bin when the
>>> MacPorts installer put the statement to augment PATH in my unused ~/.cshrc?
>>
>> You probably want to put it in ~/.login (rather than ~/.profile) since
>> you're using csh.
>
> Ah, that would explain the missing INFOPATH! (Well, missing since last week.
> Before, last year for example, I was not missing this.)
That may have been before we fixed X11 to use the login environment.
--Jeremy
_______________________________________________
Xquartz-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev