Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!husc6!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.wizards
Subject: Re: Character echo at read time
Keywords: echo tty device driver line discipline
Message-ID: <8432@smoke.ARPA>
Date: 4 Sep 88 08:16:36 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: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 9

In article <4659@cbmvax.UUCP> ditto@cbmvax.UUCP (Michael "Ford" Ditto) writes:
>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.

So how the hell can you see what you typed so far without having
to wait until the matching input operation is initiated?

I have used deferred-echo systems and one DOES need ^R.