🚀 go-pugleaf

A couple of weeks ago I reported a problem which I was having with
Emacs running on a remote machine not being able to open my display.
A number of people suggested that I xhost, but that was primarily
because I neglected to mention explicitly that the remote machine was
xhosted.  

Thanks to some some help from Chris Welty, we found out the problem.
He discovered that emacs -d {IP numeric address here}:0 would get the
window up fine, but that using the hostname would not.  Seems as
though gethostbyname was bombing somewhere along the way.  Well, we
had just upgrade from SunOS 3.5 (which X11 was built under) to SunOS
4.0.1.  Any new X applications which tried to be built with the pre
OS-upgrade libraries had the same problems which Emacs was having.
Missing /etc/resolv.conf for a little while (when one of the libraries
was built?) also might have had a hand in it.

The result of all of this (with some speculation) was that we rebuilt
X and then rebuilt Emacs with the new libraries.  Works as it should
now.  Hoorah.

(Oh, but in the process I managed to get us up to 18.53.4 when I've
only applied two patches ... not that it really matters, but how did
it get up there?  I tried removing any hints if earlier versions from
the directories and grep'ed the {etc,src}/* files for the 18.53 string
but couldn't find where Emacs was keeping track of the patch level.
How does temacs inc_version (or whatever) know what level it is to?)

YAD (Yet Another Dave)
--
      tale@rpitsmts.bitnet, tale%mts@itsgw.rpi.edu, tale@pawl.rpi.edu