Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ncr-tp.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!decvax!ittvax!dcdwest!sdcsvax!sdcc3!sdcc6!ncr-tp!greg
From: greg@ncr-tp.UUCP (Greg Noel)
Newsgroups: net.unix-wizards,net.bugs.4bsd
Subject: Bug in csh? (exec v. job control)
Message-ID: <160@ncr-tp.UUCP>
Date: Wed, 3-Apr-85 17:19:31 EST
Article-I.D.: ncr-tp.160
Posted: Wed Apr  3 17:19:31 1985
Date-Received: Sat, 6-Apr-85 01:46:40 EST
Reply-To: greg@ncr-tp.UUCP (Greg Noel)
Organization: NCR Corporation, Torrey Pines
Lines: 12
Xref: watmath net.unix-wizards:12710 net.bugs.4bsd:1443

There seems to be a bug in the way the C shell's exec function interacts
with job control.  The quickest way to show it:
	-  Run the C shell and make sure that the SHELL environment variable
	   is set to /bin/csh.
	-  type "vi garbage-file" to get a program that will create a shell.
	-  type ":sh" to get a shell.  The C shell should prompt you.
	-  type "exec echo foo" -- actually, exec any program.  In theory,
	   this should run the specified program and then return to the editor.

Now tell me, why was the editor stopped with a "tty output"?
-- 
-- Greg Noel, NCR Torrey Pines       Greg@ncr-tp.UUCP or Greg@nosc.ARPA