Xref: utzoo comp.unix.questions:30524 comp.sys.apollo:8802
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!gatech!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!edcastle!aiai!richard
From: richard@aiai.ed.ac.uk (Richard Tobin)
Newsgroups: comp.unix.questions,comp.sys.apollo
Subject: Re: Type-ahead in unix
Message-ID: <4497@skye.ed.ac.uk>
Date: 17 Apr 91 12:01:37 GMT
References: <1991Apr10.141518.2135@software.org> <+G-_A&=@warwick.ac.uk> <50ed9956.cb12@dabo.citi.umich.edu> <-Q=_Y$_@warwick.ac.uk>
Reply-To: richard@aiai.UUCP (Richard Tobin)
Organization: AIAI, University of Edinburgh, Scotland
Lines: 17

In article <-Q=_Y$_@warwick.ac.uk> cudcv@warwick.ac.uk (Rob McMahon) writes:
>On a constructive note, I used to quite like the Burroughs MCP/CANDE approach
>of holding up output while you were half-way through an input line, allowing
>you to see and edit the line you were typing, and then releasing it when you
>hit return, until you had typed the first character of the next line.

This can be a pain if you've inadvertently typed something - you're
left wondering where the output's gone.  It's particularly annoying
if you make the mistake RSX-11 made and don't release the output if
the user deletes the input.  It would also be good to have a way of
releasing the output without hitting return or losing the input.

-- Richard
-- 
Richard Tobin,                       JANET: R.Tobin@uk.ac.ed             
AI Applications Institute,           ARPA:  R.Tobin%uk.ac.ed@nsfnet-relay.ac.uk
Edinburgh University.                UUCP:  ...!ukc!ed.ac.uk!R.Tobin