>I don't see how an X client could cause the X server to bring all
>windows in front, which is what happens.
I tried to explain one possibility: the autolaunch feature which is one of the
functions of the 2 launchd plists.
With that, XQuartz will be launched when an X application reads the DISPLAY
variable. If XQuartz behaves like most other applications, it will be brought
to the front if it is already running when that event occurs. This would not be
not a bug in XQuartz itself, but in the way it's integrated.
Apparently this isn't the only cause for Cheng, but such a mechanism could
easily cause XQuartz to come to the front each time you even try to print
$DISPLAY in a shell. It could be prevented in launchd itself ("don't do
anything if you know XQuartz is already running") but I doubt XQuartz could be
made to ignore events that would bring it to the front. Doing that would
probably also make it ignore Command-Tab or activation via the Dock.
Does Chrome ever cause XQuartz to start unexpectedly? If so it, or one of its
extensions, attempts to read the value of $DISPLAY... which in itself should be
a perfectly safe operation.
R.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/x11-users/archive%40mail-archive.com
This email sent to [email protected]
