Xref: utzoo comp.emacs:4478 gnu.emacs.bug:123
Newsgroups: comp.emacs,gnu.emacs.bug
Path: utzoo!utgpu!jarvis.csri.toronto.edu!dopey.white.toronto.edu!cks
From: cks@white.toronto.edu (Chris Siebenmann)
Subject: Re: 18.52 and X11
Message-ID: <88Oct25.175431edt.40365@dopey.white.toronto.edu>
Reply-To: cks@white.toronto.edu (Chris Siebenmann)
Organization: Ziebmef home away from home
References: <4933@garfield.MUN.EDU> <358@infovax.lan.informatik.tu-muenchen.dbp.de>
Date: Tue, 25 Oct 88 17:54:01 EDT

In article <358@infovax.lan.informatik.tu-muenchen.dbp.de> schoett@lan.informatik.tu-muenchen.dbp.de (Oliver Schoett) writes:
..
>I've observed this bug with GNU Emacs 18.51 and 18.52 under Ultrix 2.2
>and X11R2.  It happens when the DISPLAY environment variable is set to
>"unix:0" (indicating a "Unix domain" connection) and goes away when
>DISPLAY is set to "hostname:0" (hostname=name of your or any other
>machine, indicating a TCP/IP connection).

 We had exactly the same problem running Emacs 18.51 under Ultrix 2.2
and X11R2. I counldn't find a consistent spot where it hung; checking
in the debugger seemed to show it spinning around deep in the
internals of the input code and the X11 input code. After reading a
comment on the Emacs-under-X11 mailing list I tried rebuilding Emacs
with s-bsd4-3.h instead of s-bsd4-2.h, and that got rid of the
problem.

 I suspect from some comments on the Emacs-under-X11 mailing list that
it may be a problem with the INTERRUPT_INPUT define, but I've never
been gung-ho enough to try and find out.

-- 
	"I shall clasp my hands together and bow to the corners of the world."
			Number Ten Ox, "Bridge of Birds"
Chris Siebenmann		...!utgpu!{ncrcan,ontmoh!moore}!ziebmef!cks
cks@white.toronto.edu	     or ...!utgpu!{,csri!}cks