[Xquartz-dev] I am having problems with 2.7.5_rc3 and _rc4 (rc2 & before were ok)

[Peter Dyballa]

Am 12.11.2013 um 01:56 schrieb Jeremy Huddleston Sequoia:

> That's perfectly fine, and many people do use X11 fullscreen, but that doesn't explain at all why you're avoiding using the launchd socket and setting DISPLAY manually yourself.

I am not setting DISPLAY manually. A 'grep DISPLAY ~/.*' reveals:

	.login:#if (! $?DISPLAY) then
	.login:#        setenv DISPLAY `ps -wwwe -p $PID | grep DISPLAY | sed -e 's/^.*DISPLAY=\([^ ]*\) .*$/\1/'`
	.login:#        setenv DISPLAY :${Anzahl}
	.login:#alias updisp	'setenv DISPLAY `defaults read "${HOME}/.MacOSX/environment" DISPLAY`'
	.login:#setenv DISPLAY :0
	.xinitrc-orig:defaults write ${HOME}/.MacOSX/environment "DISPLAY" $DISPLAY
	.xinitrc-orig:defaults delete ${HOME}/.MacOSX/environment "DISPLAY"

*I* have no idea where I might manually set it. ~/.MacOSX/environment.plist does not contain DISPLAY:

	pete 84 /\ defaults read ~/.MacOSX/environment DISPLAY
	2013-11-12 11:34:17.776 defaults[921:903] 
	The domain/default pair of (/Users/pete/.MacOSX/environment, DISPLAY) does not exist


> 
> What makes it "awkward" to you?  You shouldn't ever need to think about it.  launchd sets the environment variable for you, and you should never need to bother with it.

I don't like that another X server migt be launched when I by accident launch an X client somewhere. This does not belong into the world of my Look & Feel. What happens when I want to launch an X client from AppKit Emacs, NS Emacs, or Terminal, all "Aqua clients"? Their environment has for example 'DISPLAY=/tmp/launch-90gGwj/org.macosforge.xquartz:0'. To launch the X client from these applications I can use ":0" instead of a cryptic and lengthy text.

--
Greetings

  Pete

We are usually convinced more easily by reasons we have found ourselves than by those which have occurred to others.
				– Blaise Pascal