Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!ceres.physics.uiowa.edu!news.iastate.edu!kickapoo.cs.iastate.edu!hamilton Newsgroups: comp.unix.questions Subject: Re: Type-ahead in unix Message-ID: From: hamilton@kickapoo.cs.iastate.edu (Jon Hamilton) Date: 9 Apr 91 00:25:10 GMT Sender: news@news.iastate.edu (USENET News System) References: <7297@utacfd.UUCP> <659@adpplz.UUCP> <15686@smoke.brl.mil> <659@rufus.UUCP> Organization: Iowa State University, Ames IA Lines: 25 drake@drake.almaden.ibm.com writes: >In article <15686@smoke.brl.mil> gwyn@smoke.brl.mil (Doug Gwyn) writes: >>UNIX has "always" supported type-ahead. >>I think what you are discussing is deferred echo. >>Why would you have to have that? >I think they are discussing deferred echo, too. As for why you have to have >it ... well, it would sure be nice to be able to type the next command >without ruining the appearance of the output of the current one! I've been waiting for someone to say this, but nobody has. tcsh does this just fine. No characters get echoed until after the ensuing prompt. This may not be true in all tcsh's, though - I've noticed that the tcsh I use under SunOS is considerably stupider than the one running under A/UX. >Sam Drake / IBM Almaden Research Center >Internet: drake@ibm.com BITNET: DRAKE at ALMADEN >Usenet: ...!uunet!ibmarc!drake Phone: (408) 927-1861 -- Jon Hamilton hamilton@kickapoo.cs.iastate.edu " I feel a lot more like I do now that I did before I got here " - can't remember who