<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Oct 13, 2014 at 9:34 AM, Chris Jones <span dir="ltr"><<a href="mailto:jonesc@hep.phy.cam.ac.uk" target="_blank">jonesc@hep.phy.cam.ac.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">My argument is not based on what some standard says about what DISPLAY should or should look like, but the basic premise that extracting information from $DISPLAY is just a bad idea and should be avoided.</blockquote></div><br>Note that p5-x11-protocol has legitimate reason to do so: it is not a binding to a C library, but a native "XPB" (compare XCB, XHB among others) so must indeed determine transport information from $DISPLAY itself.</div><div class="gmail_extra"><br></div><div class="gmail_extra">That said, I will note that the X11 handbook is completely ignoring things like unix/hostname:dispno (i.e. the original AF_UNIX transport description, plus an indication of *how you explicitly identify a transport mechanism*), does not mention legacy transports like DECnet, etc. It is not comprehensive, it implies that historical usages were never valid, etc. Do not read too much into it, most certainly do not treat it as a standards document.<br clear="all"><div><br></div>-- <br><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div><div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div>
</div></div>