Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!samsung!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!netnews.upenn.edu!msuinfo!convex.cl.msu.edu!jap
From: jap@convex.cl.msu.edu (Joe Porkka)
Newsgroups: comp.sys.amiga.misc
Subject: Re: TYpeahead implementations (Re: How do we change the scheduler? (Was Re: Multitasking at home...))
Message-ID: <1991Jan21.191728.27166@msuinfo.cl.msu.edu>
Date: 21 Jan 91 19:17:28 GMT
References: <17210@cbmvax.commodore. <yorkw.663963975@stable.ecn.purdue.edu> <7536@sugar.hackercorp.com> <42121@nigel.ee.udel.edu> <7552@sugar.hackercorp.com>
Sender: news@msuinfo.cl.msu.edu
Organization: Michigan State University
Lines: 23

peter@sugar.hackercorp.com (Peter da Silva) writes:

>In article <42121@nigel.ee.udel.edu> new@ee.udel.edu (Darren New) writes:
>> I prefer the method used in CP-V, namely that the input you type ahead
>> does not echo until it is read.

>Most systems in fact do it this way. I don't like it because I find it
>easy and convenient to do a lot of typeahead, and I like to get immediate
>feedback of what I type. Cuts down on typos.

I only worked with one for a couple of minutes, but...
The Appolo workstations console windows had a seperation box
taking up the entire last line (sizeable perhaps?) of the console
window for type ahead. Thus you get feedback, and don't interfere
with normal text output.

Personally I *REALLY* like the Amigas CON: behavior. 

The one thing missing is a way to cancel input, after hittin
return, but before the shell (or whatever) reads it in.

The worst is MSDOS, which ignores ctrl-s if you have typed any
other characters ahead of it.