On 26 Mar 2018, at 20:16, René J.V. Bertin wrote:
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.
Not so. There is no such thing as ‘_the_ DISPLAY variable’. Every
process is given a ‘Environment’ when it starts. This is inherited
from the parent that forks to produce it. It includes any variables that
were a part of the parent’s environment. Every process that has a
variable called DISPLAY in its environment has its own copy - as
inherited or as set by the process. Their values are independent. For a
program to take some action when a variable is read it would have to use
some convention for variable reading, and that could be by-passed.
David
_______________________________________________
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]
