Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!tektronix!hplabs!hpda!hpisoa2!hpitg!amdahl!acs@amdahl
From: acs@amdahl
Newsgroups: net.micro.amiga
Subject: Re: Orphaned Response
Message-ID: <3064@amdahl>
Date: Fri, 25-Apr-86 01:38:00 EDT
Article-I.D.: amdahl.3064
Posted: Fri Apr 25 01:38:00 1986
Date-Received: Tue, 13-May-86 02:07:34 EDT
References: <494@isis>
Lines: 31

In article <4@intelca.UUCP> cem@intelca.UUCP (Chuck McManis) writes:

> 
> Datta T Miruke writes :
> > 
> >  1. the ^S feature to stop the flow does seem to work when 'typ'ing some file,
> >     but ^Q does not, rather it takes a return key to restart the flow. Is this
> >     consistent?
> 
> I haven't tried porting anything but I do know the answer to the first one :
> 
> Use the right (Menu) mouse button to stop output. (Press and hold to stop
> release to continue) It seems anything you type will stop the output but
> it also gets fed into the AmigaDOS typeahead buffer so after the file 
> prints you usually get a bunch of "Unknown Command" prompts.
> 
I don't know what the developer's *did* but this is how things appear (to
me) to operate in the CLI "window":
  *  Any keyboard activity will stop output.
  *  Any activity which would return the cursor to the left-most edge of
     the screen will resume output.
In other words, if you hit the space bar output will stop.  If you hit the
space bar 2 more times then a backspaces *or* a carriage-return *or* ^X
will resume output.  If you *don't* use the CR key, the CLI will not
remember ever seeing what you've typed (i.e. those spaces and their ^X or
backspaces will disappear).
-- 
Tony Sumrall                    ...!{ihnp4,hplabs,seismo,sun}!amdahl!acs

[ Opinions expressed herein are the author's and should not be construed
  to reflect the views of Amdahl Corp. ]