Xref: utzoo gnu.emacs.bug:122 comp.emacs:4474
Path: utzoo!attcan!uunet!mcvax!unido!ztivax!tumuc!lan!schoett
From: schoett@lan.informatik.tu-muenchen.dbp.de (Oliver Schoett)
Newsgroups: gnu.emacs.bug,comp.emacs
Subject: Re: 18.52 and X11
Summary: More information on the bug
Message-ID: <358@infovax.lan.informatik.tu-muenchen.dbp.de>
Date: 17 Oct 88 18:48:06 GMT
References: <4933@garfield.MUN.EDU>
Reply-To: schoett@lan.informatik.tu-muenchen.dbp.de (Oliver Schoett)
Organization: Inst. fuer Informatik, Technische Univ. Muenchen, West Germany
Lines: 23

In article <4933@garfield.MUN.EDU> jeff1@garfield.mun.edu (Jeff
Sparkes) writes: 

> Emacs 18.52 doesn't work properly under X11 on Ultrix 2.0.  When I
> start up emacs from an xterm, it doesn't receive input properly.  I
> can type into the emacs window, but it doesn't get any input until I
> hit return in the xterm window that I started emacs in.  It seems to
> be still trying to get input from the original window.

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).

I've circumvented the bug with a little shell script wrapped around
emacs that resets the DISPLAY variable when it is "unix:0", but I'd
like to have a real fix to the problem, too.

Oliver Schoett	   Inst. f\"ur Informatik, Technische Univ. M\"unchen,
		   Postfach 20 24 20, 8000 M\"unchen 2, West Germany
schoett@lan.informatik.tu-muenchen.dbp.de	      +49 89 2105 2390
schoett%lan.informatik.tu-muenchen.dbp.de@ {relay.cs.net, unido.uucp}