Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site pyuxss.UUCP
Path: utzoo!linus!decvax!harpo!eagle!mhuxi!mhuxl!mhuxm!pyuxi!pyuxss!aaw
From: aaw@pyuxss.UUCP
Newsgroups: net.unix-wizards
Subject: Re: Job Control Wishlist
Message-ID: <181@pyuxss.UUCP>
Date: Tue, 25-Oct-83 15:46:59 EDT
Article-I.D.: pyuxss.181
Posted: Tue Oct 25 15:46:59 1983
Date-Received: Wed, 26-Oct-83 07:23:15 EDT
References: <12703@sri-arpa.UUCP>
Organization: Bell Labs, Piscataway
Lines: 17

I have had the same problem and considered the sandwich technique of
implementing it. That is:

	inputControl | theCommand | outputControl

inputControl and outputControl would of course have to be a
replacement shell, to limit proliferation of processes and
interprocess chatter. Consider the consequences: you could have
several 'background' processes requesting I/O and the shell
(=inputControl) should be able to sort it out, e.g. prompt

theCommand: >

to say 'theCommand' wants input. Also the major plus is it would allow
windowing with several forground processes, due to the shells sorting
out the /dev/tty reads/writes
				Aaron Werman pyuxss!aaw