Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site psivax.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!hplabs!sdcrdcf!psivax!friesen
From: friesen@psivax.UUCP (Stanley Friesen)
Newsgroups: net.unix-wizards
Subject: Re: Job control
Message-ID: <1107@psivax.UUCP>
Date: Fri, 18-Apr-86 13:59:40 EST
Article-I.D.: psivax.1107
Posted: Fri Apr 18 13:59:40 1986
Date-Received: Mon, 21-Apr-86 04:20:43 EST
References: <2113@dutoit.UUCP>
Reply-To: friesen@psivax.UUCP (Stanley Friesen)
Organization: Pacesetter Systems Inc., Sylmar, CA
Lines: 22

In article <2113@dutoit.UUCP> dmr@dutoit.UUCP writes:
>
>  In none of these is a special
>shell needed.  The virtual terminal seen by each job has its own
>instance of the tty driver; for example, you can turn off echo in one
>job (or window) without affecting another.  Of course, neither shl, nor
>BSD job control, knows anything about the real terminal: what is on
>the screen or any special modes the terminal itself might be in.

	Is there only one shell running per login session, rather than
one per window? If the former, how does it manage selecting/deselecting
windows without special code? If the latter, I consider this a very
inefficient implementation. My ideal would be a system with a single
instance of the shell per login session which creates the windows and
handles the switching operation in a manner that is fully integrated
with the command line parsing operation.
-- 

				Sarima (Stanley Friesen)

UUCP: {ttidca|ihnp4|sdcrdcf|quad1|nrcvax|bellcore|logico}!psivax!friesen
ARPA: ttidca!psivax!friesen@rand-unix.arpa