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 violates the principle of least surprise.
Without a transport name, display specifiers are expected to connect to whatever the best available transport is. Historically this means magic local tranports if any, followed by unix sockets, followed by TCP. So DISPLAY=:0 should connect to TCP if the unix socket doesn't work. - ajax
signature.asc
Description: This is a digitally signed message part
_______________________________________________ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
