Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/17/84; site elsie.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!godot!harvard!seismo!umcp-cs!cvl!elsie!mark
From: mark@elsie.UUCP (Mark J. Miller)
Newsgroups: net.bugs.4bsd
Subject: Re: CSH -- stopping job in SOURCE'd file
Message-ID: <4067@elsie.UUCP>
Date: Tue, 20-Nov-84 13:33:08 EST
Article-I.D.: elsie.4067
Posted: Tue Nov 20 13:33:08 1984
Date-Received: Thu, 22-Nov-84 06:02:26 EST
References: <286@hwcs.UUCP> <9821@watmath.UUCP>, <5814@brl-tgr.ARPA> <9899@watmath.UUCP>
Organization: NIH-LEC, Bethesda, MD
Lines: 20

> 
> It doesn't have to.  I fixed it.  Stopping a job in a SOURCE'd file
> just stops the job.  The shell continues with the next command in the
> file.  My fix also means " a ; b ; c " behaves as documented; stopping
> process B lets process C start.
> -- 
>         -IAN!  (Ian! D. Allen)      University of Waterloo

That's a fix I don't want. I've often used ^Z to zap a series of type-ahead
jobs, when that was what I wanted it to do. Especially useful if one of those
jobs contains an error. You can use ^Z; fg to erase and start over again.
That's the trouble, isn't it. One persons bug is another's feature.

					--elsie!mark

-- 
Mark J. Miller
NIH/NCI/DCE/LEC
UUCP:	decvax!harpo!seismo!elsie!mark
Phone:	(301) 496-5688