On Thu, 2010-04-29 at 13:56 -0700, Josh Triplett wrote:
On Thu, Apr 29, 2010 at 01:05:48PM -0700, Jeremy Huddleston wrote:
Yeah, I agree... but this fallback already exists in the wild.
I find it quite dubious that real applications expect DISPLAY=:0 to
connect to TCP. It certainly
On Thu, Apr 29, 2010 at 01:05:48PM -0700, Jeremy Huddleston wrote:
On Apr 29, 2010, at 12:39, Jamey Sharp wrote:
I don't think it makes sense to do it in libX11; we'd have to do
DISPLAY-string mangling there, which seems silly.
I don't think we'd have to mangle DISPLAY; just pass
Josh Triplett wrote:
I find it quite dubious that real applications expect DISPLAY=:0 to
connect to TCP. It certainly violates the principle of least surprise.
But it's what the Xlib standard spec has always required. When no hostname
or transport protocol is provided, Xlib is supposed to
On Thu, Apr 29, 2010 at 03:12:43PM -0700, Alan Coopersmith wrote:
Josh Triplett wrote:
I find it quite dubious that real applications expect DISPLAY=:0 to
connect to TCP. It certainly violates the principle of least surprise.
But it's what the Xlib standard spec has always required. When
