Path: utzoo!attcan!uunet!husc6!cs.utexas.edu!sm.unisys.com!ism780c!mikep
From: mikep@ism780c.isc.com (Michael A. Petonic)
Newsgroups: comp.unix.wizards
Subject: Re: Character echo at read time
Keywords: echo tty device driver line discipline
Message-ID: <15104@ism780c.isc.com>
Date: 5 Sep 88 08:42:38 GMT
References: <347@spies.UUCP> <670025@hpclscu.HP.COM> <24355@bu-cs.BU.EDU> <4477@mtgzz.att.com> <371@polyof.UUCP> <8418@smoke.ARPA> <397@marob.MASA.COM> <8425@smoke.ARPA> <4659@cbmvax.UUCP>
Reply-To: mikep@ism780c.UUCP (Michael A. Petonic)
Organization: Interactive Systems Corp., Santa Monica CA
Lines: 21

In article <4659@cbmvax.UUCP> ditto@cbmvax.UUCP (Michael "Ford" Ditto) writes:
 >In article <8418@smoke.ARPA> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
 >>In a UNIX implementation of deferred echo, presumably one would
 >>type ^R to check his most recent input line while there is still
 >>time to edit it (before typing a newline).
 >No, no, no... part of the beauty of doing echo the non-unix way is that you
 >don't need to ^R to see what you typed.  It's unix-echo that causes your
 >input line to get screwed up so you have to type ^R.

Following the thread, I think Doug was saying that if an O.S. used
MS-DOS echo and if you wanted to check what you typed (while another
command is running), you could type ^R to see it.  This would
be desirable since the MS-DOS way doesn't echo out until it reads
the input and those of us less gifted would have a way of visually 
scanning the line to make sure it's correct.

-MikeP
-- 
Michael A. Petonic				mikep@ism780c.isc.com

	       ``Have a heart... But don't take mine.''