Re: X11 in Leopard: xterm on start-up
Re: X11 in Leopard: xterm on start-up
- Subject: Re: X11 in Leopard: xterm on start-up
- From: Dave Williss <email@hidden>
- Date: Tue, 30 Oct 2007 09:09:59 -0500
Rich Cook wrote:
Oh, but please be careful!
AIR, there is a persnickety difference between "localhost:0" and ":0",
I believe, someone correct me if I'm wrong: "localhost:0" hits the
NIC and ":0" is direct rendering. Perhaps you are wondering why you'd
ever want to use the network when you can just set it to :0, and the
answer is: if you are testing software, sometimes you want to test
GLX vs. GL... I hope I'm remembering this correctly.
What I'm saying is, please don't change the usage to be what you think
is the "right" way, i.e., a peculiar Apple-only way, rather do it the
way everyone else does it, or it will actually be harder for a bunch
of us that use multiple platforms to figure out what you thought was
super cool compared to what RHEL does, etc.
On Oct 29, 2007, at 5:58 PM, Mark J. Reed wrote:
On 10/29/07, Ben Byer <email@hidden> wrote:
If I understand what you're suggesting, that is in fact what we're
already doing. We modified libX11.dylib to detect the special launchd
DISPLAY format, and to handle that correctly.
But that's not what Dave was suggesting, IIUC. He was suggesting
that, as a special case, the Apple version of libX11 treat ":0.0" and
other DISPLAY values that normally mean "the local console display"
*as if* they were set to the special launchd format. Assuming it
could figure out where the launchd socket is....
That's almost what I meant. If DISPLAY is set, it should try whatever
it would
do normally and then, *only if that failed* and it was set to :0 (or
unix:0 which
I believe maps to the same thing), try the launchd socket. Again, it
has to be
able to tell what it was first.
That way, it would work even if the user had set DISPLAY to unix:0 or :0 in
their .profile or wherever. You would *not* want to just treat all DISPLAY
strings that map to a local connection as the launchd socket because
that would
preclude somebody trying to run a *different* X server.
Somebody also pointed out that localhost:0 means the local display but using
TCP/IP protocol instead of Unix sockets. If X11 is already running, then
attempting to connect to localhost:0 would just work. If it's not
running, that
would fail (probably after a few seconds timeout on the socket connection).
In that case, libX11 could connect once through the launchd socket to
get X11
up and then try localhost:0 again for the "real" connection. This would
make
your client take longer to launch using "localhost:0" if X11 isn't
running than it
would using ":0", but if you're just using "localhost:0" to test GL vs
GLX, you
probably fall under the category of people who keep X11 running all the time
anyway and would never notice :-)
Dave Williss
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden