Gnu-Emacs behavior revisited

Article View: comp.windows.x

Article #25343

#25343

From: rlk
Date: Tue, 07 Apr 1987 19:52

13 lines
1205 bytes

The operating system DOES affect the behavior because of bugs in
4.2BSD.  Specifically, SIGIO doesn't work properly on sockets, so
asynchronous I/O gets blown out of the water.

This isn't a problem if you start emacs from a remote machine,
assuming the remote machine is running 4.3 or 4.2 with fixed socket
code.  It also won't be a problem if you're running it inside an
xterm, because SIGIO works properly for terminals (see the fcntl(2)
man page for this nonsense).  However, an emacs started from a 4.2
machine with broken socket code will have these problems, as I know
from experience.

Robert^Z

Technical Details

Message-ID: <8704071952.AA27832@PRIAM.MIT.EDU>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!ATHENA.MIT.EDU!rlk

References: <8704060332.AA11628@anubis.UChicago.EDU>

Show Full Headers

Complete Article Headers

Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!ATHENA.MIT.EDU!rlk
From: rlk@ATHENA.MIT.EDU.UUCP
Newsgroups: comp.windows.x
Subject: Gnu-Emacs behavior revisited
Message-ID: <8704071952.AA27832@PRIAM.MIT.EDU>
Date: Tue, 7-Apr-87 14:52:04 EST
Article-I.D.: PRIAM.8704071952.AA27832
Posted: Tue Apr  7 14:52:04 1987
Date-Received: Fri, 10-Apr-87 06:02:56 EST
References: <8704060332.AA11628@anubis.UChicago.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 13

Reply to Parent Message