And I actually want to take that idea a step further and make /A/U/ X11.app/C/M/X11 the *real* server which simply executes app_to_run when executed straight and starts the server when launched by launchd. The user would have a defaults option to cause it to have the tiger behavior of starting DISPLAY=:0 if they want to get rid of launchd support. Such a change is a bit too deep to make right now. I think we should keep 2.1.x as close as possible to the Official Leopard model and look at 2.2.x (xorg-server-1.4-apple) and 2.3.x (master / 1.5-branch) for more involved changes like this... especially since we're pretty close to having a working 1.4 based xserver. We just need to cleanup event handling there a bit to get it on the same level as corg-server-1.2- apple. --Jeremy On Dec 2, 2007, at 06:41, Ben Byer wrote:
On Dec 1, 2007, at 10:16 PM, John Davidorff Pell wrote:
I don't think this is what should be done. I think that X11 should switch back to the XDarwinApp model (where /u/X/X11.app/C/M/X11 is the *actual* X server), and then people who want to pass special commands can just be told to run it with an absolute path.
Or, better yet, put in a dummy xinit which asks launchd to start X11!
That's actually what we tried first, but ran into some bizarre Dock behavior (yes, even worse than current behavior) where it caused the icon to disappear entirely. -- Ben Byer CoreOS / BSD Technology Group, XDarwin maintainer
_______________________________________________ Xquartz-dev mailing list Xquartz-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/xquartz-dev