Path: utzoo!attcan!uunet!husc6!bloom-beacon!tut.cis.ohio-state.edu!cwjcc!gatech!rutgers!cmcl2!lanl!unm-la!unmvax!nmtsun!warner@hydrovax.nmt.edu
From: warner@hydrovax.nmt.edu (M. Warner Losh)
Newsgroups: comp.unix.wizards
Subject: Re: Character echo at read time
Message-ID: <1059@nmtsun.nmt.edu>
Date: 5 Sep 88 06:13:47 GMT
Sender: news@nmtsun.nmt.edu
Organization: New Mexico Tech Hydrology Program
Lines: 27

In article <371@polyof.UUCP>, john@polyof.UUCP ( John Buck ) writes...
>I'm curious to know: do you folks who tolerate "invisible" type-ahead
>ever make mistakes in typing commands (ahead)?  If so, when do you detect
>the mistakes?  Before it's too late?

This tends to be less of a problem than you might think.  "Type behind"
as one person called it is great.  It allows you to do things like have
a smart terminal driver that remembers the last thing you typed so you can
go back and edit it (not like that !$ stuff in csh, but less powerful).

I make mistakes with the invisible type ahead.  Many times I do catch it
before it's too late.  With VMS you can do a ^X anytime the terminal is
not in "raw" mode and clear the current type ahead buffer.  How does one
do this under unix?  (Really, I'd like to know, but I don't think it can
be done if you have entered several commands...)

>   How do you see what you are correcting?

How do you see what you are correcting when you type the password to your
system.  It's the same sort of deal.

> 
>polyof!john
--
Warner Losh
warner@hydrovax.nmt.edu		...!unmvax!nmtsun!warner%hydrovax
My spelling and views are my own.  Only the letters have been changed...