Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ki4pv.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!houxm!mtuxo!mtunh!mtung!mtunf!ariel!vax135!petsd!peora!ucf-cs!ki4pv!tanner
From: tanner@ki4pv.UUCP (Tanner Andrews)
Newsgroups: net.emacs
Subject: EMACS with Flow Control
Message-ID: <347@ki4pv.UUCP>
Date: Wed, 10-Jul-85 15:05:01 EDT
Article-I.D.: ki4pv.347
Posted: Wed Jul 10 15:05:01 1985
Date-Received: Sun, 14-Jul-85 08:48:12 EDT
Organization: CompuData South, DeLand
Lines: 23
Keywords: brain_damage, dinosaur_eggs, dec_(tm), xon_xoff, eia-20

While this has not yet been needed on this system, and so I haven't
implemented it, I have had to do this on many systems before.  At
times it is not a pain in the sensitive locations.

Many terminals and people can't process chars fast enough, &c., &c.
There was invented, therefore, flow control.  In the case of people,
this flow control is done by mashing some key (such as ^S).  In the
case of terminals, you frequently find them pretending to mash the
same key.

Most modern terminals, however, have another way to shut up the computer
or whatever they are talking to:  they wiggle an rs232 signal (such as
the one on pin 20).  Printers do the same thing, by the way.  If the
computer watches for this, and shuts up when the terminal says "not
ready", then you can pass all chars straight through to the application.

If your network or computer supports "hardware" flow control, sometimes
called "dtr" (among other things), throw the proper switches.  Your op
sys probably can handle ^S/^Q when applications are not running in "raw"
mode.
-- 
	   Tanner Andrews, KI4PV
uucp:					...!decvax!ucf-cs!ki4pv!tanner