Newsgroups: gnu.emacs.bug Path: utzoo!utgpu!jarvis.csri.toronto.edu!snow.white.toronto.edu!cks From: cks@white.toronto.edu (Chris Siebenmann) Subject: Re: X11 hanging behavior with uvaxes, 18.51 Message-ID: <89Feb14.164056est.15497@snow.white.toronto.edu> Reply-To: cks@white.toronto.edu (Chris Siebenmann) Organization: Ziebmef home away from home References: <27941@ucbvax.BERKELEY.EDU> <89Feb13.161804est.15497@snow.white.toronto.edu> Distribution: gnu Date: Tue, 14 Feb 89 16:40:42 EST In article <89Feb13.161804est.15497@snow.white.toronto.edu> cks@white.toronto.edu (Chris Siebenmann) writes: >[problem with Emacs 18.51 and X11, where Emacs comes up and just sits there.] > > This is apparently a problem with SIGIO on Unix domain sockets in >Ultrix. You can cure the problem by remaking Emacs using s-bsd4-3.h >instead of s-bsd4-2.h. RMS pointed out a problem with this in email; if you make this change, you will loose the ability to C-g ELisp code when Emacs is using its own window. You can still interrupt it with a control-C from the shell you started it in, or send it a SIGINTR signal; C-g also works fine when it doesn't open up its own window (ie when started with -nw or on an ordinary terminal). I should also have mentioned that this is on Ultrix 2.2; I would assume it is true for at least 2.0 and 2.1 as well (and maybe 2.3). -- "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