Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!SUN.COM!swoodhead From: swoodhead@SUN.COM (Simon Woodhead) Newsgroups: comp.windows.x Subject: echoing in terminal windows Message-ID: <8907171113.AA01717@sunaus.sun.oz> Date: 18 Jul 89 02:12:30 GMT Sender: daemon@bloom-beacon.MIT.EDU Organization: The Internet Lines: 40 Please reply direct to Bob Smart at the address below, or to the comp.windows.x newsgroup / xpert mailing list. ----- Begin Included Message ----- From acsnet@sunaus Fri Jul 14 23:53:11 1989 Path: sunaus!metro!basser!munnari.oz.au!murtoa.cs.mu.oz.au!ditmela!smart Newsgroups: comp.windows.x Subject: echoing in terminal windows Reply-To: smart@ditmela.oz.au (Robert Smart) Organization: C.S.I.R.O. Division of Information Technology, Melbourne. Lines: 24 I mostly prefer the VMS echoing style: characters are not echoed until some program reads the characters. So your terminal session looks the same whether you typeahead or not. However sometimes it is useful to see your typeahead. It seems that terminal windows provide an opportunity for the best of both worlds. I would like to see typeahead appear in its own little window extension at the bottom of the screen [in a moderately raw form with carriage returns appearing as ^M, etc]. As the characters are read they would be echoed on the main part of the terminal emulation and disappear from the typeahead section. This would allow some subtleties that are missing at the moment: for example if you type a rub-out char does it get added to the typeahead, or delete the last character typed- ahead? With the proposed scheme it could do either depending on whether the main or typeahead window is active [as a result of mouse movements, etc]. Any comments. Presumably this needs a new terminal driver to interface intelligently to the window system. Bob Smart ~ ~ ~ ~ ~ ~ ----- End Included Message -----