Re: [Xquartz-dev] Environment passed to Applications-launched processes
In fact, at least for 2.3.0, my testing indicates that X doesn't even get the environment varables in ~/.MacOSX/environment.plist. It gets a default, vanilla environment. I tested this in the following way: 1) I created some environment variables in ~/.MacOSX/ environment.plist, logged out and back in. 2) I created an applescript containing 'do shell script "env > /tmp/ testenv1.txt; /usr/X11/bin/xterm"' and ran it. 3) I added an application "testenv" with the command "env > /tmp/ testenv2.txt" to the X Applications menu. and ran it. Sure enough, testenv1.txt contains the environment variables in environment.plist, but testenv2.txt does not. This is irritating, because it means I can't define XAPPLRESDIR to find a bunch of X resource files that aren't in the usual place. -G. -- Glenn Eychaner (geychaner@lco.cl) Telescope Systems Programmer, Las Campanas Observatory
Glenn Eychaner wrote:
In fact, at least for 2.3.0, my testing indicates that X doesn't even get the environment varables in ~/.MacOSX/environment.plist. It gets a default, vanilla environment. I tested this in the following way:
I just ran a test, too, and I do see the env vars from ~/.MacOSX/environment.plist transmitted to the commands run from the Applications menu. If X11.app is started from the Dock or by clicking on the icon in /Applications/Utilitities, these are the only env vars present. If it is started automatically by running an X client, it gets additionally the env vars defined by bash startup scripts. How did you start your X11.app? -- Martin
participants (2)
-
Glenn Eychaner
-
Martin Costabel