On Dec 25, 2010, at 2:09 AM, Peter Dyballa wrote: > Am 24.12.2010 um 23:49 schrieb Jeremy Huddleston: > >> Ok, but that has nothing to do with what you set $DISPLAY to and your >> disabling launchd support (which was my question) > > I think I started to set DISPLAY because Terminal's shell has no knowledge of > it. So I can't launch an X client off it.
If you let launchd set DISPLAY, then Terminal's shell will have knowledge of it, and you will be able to launch an X client from it. If X11/Xquartz is not already running, it will be started automatically. > Of course when I want to launch an X client I don't want to switch to Finder, > make it open a new window I would have to close later, then find my way > through the file system hierarchy to the directory with the X clients and > then search among them some time for the one I want to launch. And I also > don't want to search in the Finder window for my favourite X clients place > and neither do I want to switch to X11, open its Programmes menu and then > hopefully find after some time in a large list what I want to launch. None of that is necessary. > Why is the DISPLAY variable not communicated among all processes running at > the moment and launched afterwards, after DISPLAY's first setting or its > possible change? That is essentially what launchd does for you. _______________________________________________ Xquartz-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/xquartz-dev
