The launchd approach turns a two-step process into a one-step
process.
Or, apparently, into a many-step process :-). Though, even when it
works properly, isn't it "start the app I wanted to start, then close
the random xterm that pops up"? Isn't that two-step? Clearly the
default app should be xlsfonts or xdpyinfo or some such, and the
xterms or whatever should be launched by the xinitrc.
When I click on my NEdit wrapper or my mrxvt wrapper I don't get an
xterm popping up. The only time I get an xterm is when I launch
X11.app explicitly by clicking on the launcher-app, but I've already
removed that from my dock so that never happens.
But, really, what's the *problem* that the launchd approach solves?
Having DISPLAY set correctly in every environment, all the time, and
ensuring the X server is launched on demand.
It also *vastly* simplifies things for people trying to wrap X11 apps
for use in OS X.
"Vastly"? Really? How so?
By having DISPLAY set correctly in every environment, all the time,
and relieving the wrapper of having to make sure X is running.
But I'm guessing that's small minority of standard X11 use on OS X.
I'm betting most people use it to display apps from other (Linux)
machines.
I'd guess that there are more users of Gimp.app and Inkscape.app than
people using OS X to display remote Linux apps, but I don't see what
difference it makes. Either case should just work, and does just work
in my experience. I had to make sure to remove all the cruft from the
pre-launchd days, but once I did it all just worked beautifully.
_______________________________________________
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
