Thanks, Merle. It's either I do not understand your answer or I was not clear in my question.
What I was trying to ask is why the DISPLAY variable value that launchd assigns needs to be so obscurely complicated (
e.g. /tmp/launch-0l2xbx/:0) when setting it to standard ':0' seems to work as well.
After X11 starts, I can execute in xterm 'setenv DISPLAY :0' (csh) and pop new X windows as well as with the '/tmp/launch-0l2xbx/:0' that launchd assigned. Hence what do we gain from the '/tmp/launch-0l2xbx' prefix?
On Dec 15, 2007 3:24 PM, Merle Reinhart <email@hidden> wrote:
The advantage is that it eliminates the extra manual step of having to start the X11 server prior to executing a command or app that uses X11 for its display.
On Dec 15, 2007, at 5:59 PM, John Koren wrote:
> I also wanted to ask, what is the benefit of the obscure DISPLAY > variables such as 'DISPLAY=/tmp/launch-0l2xbx/:0' that the new > 'lauchd' sets? When I reset the DISPLAY to a simple ':0' it still
> seems to work perfectly. I am just curious.
> _______________________________________________ > Do not post admin requests to the list. They will be ignored. > X11-users mailing list (
email@hidden) > Help/Unsubscribe/Update your Subscription: http://lists.apple.com/ > mailman/options/x11-users/email@hidden
> > This email sent to email@hidden
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden