Re: No Terminal Opening
Re: No Terminal Opening
- Subject: Re: No Terminal Opening
- From: Jeremy Huddleston <email@hidden>
- Date: Sat, 28 Jun 2008 11:50:35 -0700
On Jun 28, 2008, at 10:52, Bill Janssen wrote:
If <protocol> is not specified,
the / separating <protocol> and <hostname> must also not be
specified.''
News to me, and not very constraining -- the text says "can be", not
"must be"
It looks to me like it says "must" ...
-- but it suggests that a DISPLAY value which starts with a
'/' might cause problems with some existing libraries.
which is why we had to patch Xlib and xcb to work right.
Apparently an
appropriate value for Apple's scheme should be something more like
'local//tmp/launch-XXXXX/:0' or even 'apple//tmp/launch-XXXXX/:0'.
True.
I'd say your version of Xlib is seeing the leading '/', and wondering
where the 'protocol' is. That suggests you're not picking up the OS X
system version of Xlib.
Any recent Xlib should work whether it's the system version or not.
The latest release of xtrans has support for it (notice that the
source code is actually in xtrans which is used to build libX11 where
the binary code lives.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden