Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!gatech!rutgers!cbmvax!uunet!frksyv!frk From: frk@frksyv.UUCP (Frank Korzeniewski) Newsgroups: comp.emacs Subject: Re: compiling emacs Message-ID: <388@frksyv.UUCP> Date: 14 Feb 89 10:19:41 GMT References: <1034@sdcc15.ucsd.edu> <631@wpi.WPI.EDU> <385@frksyv.UUCP> Reply-To: frk@frksyv.UUCP (Frank Korzeniewski) Distribution: usa Organization: Frank Korzeniewski, Consulting Lines: 34 In article karl@triceratops.cis.ohio-state.edu (Karl Kleinpaste) writes: |frk@frksyv.UUCP (Frank Korzeniewski) writes: | >[Karl said:] | >Not quite true; Rel2.2 [on 3b20s] took care of [termio] problems. GNU | >Emacs has been compiling routinely on such machines since about 18.36. | >No workarounds weirder than usual for SysV were necessary. | | [ I described problem with emacs 18.52 and control-g ] | |The problem is not at all a bug in how termio operates, but rather in |unreliable SysVRel2 signals in combination with your PC's slow disc. | |Hence, the problem is that you can type ^Gs faster than your disc can |page in. | |Now, that speaks volumes, yes? Maybe I am missing something here. Please correct me if so. I am running Microport SYS V/386 Rel3.0 on a PRIAM 330 MB drive with a 16 ms access time. I am the only user on this system. Given these circumstances it would appear to me that anyone running emacs on SYSV is susceptible to having it killed accidentily. I agree that the problem is the poor semantics associated with the 'signal' call. However, there exist better signal handling capabilities with the 'sigset' et al routines. These should probably be used by emacs. The intent of my posting was not to imply that there was a bug in the 'termio' facilities. I am sorry about the ambiguity in my prior posting. Frank -- ______________________________________________________________________________ || Frank Korzeniewski, Consulting Suite 137 || || Phone: (415) 799-1819 1564-A Fitzgerald Drive || || UUCP: uunet!frksyv!frk Pinole, CA 94564 ||