Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site watmath.UUCP
Path: utzoo!watmath!idallen
From: idallen@watmath.UUCP
Newsgroups: net.bugs.4bsd
Subject: Re: CSH -- stopping job in SOURCE'd file; ^Z and type-ahead
Message-ID: <10045@watmath.UUCP>
Date: Wed, 28-Nov-84 17:49:57 EST
Article-I.D.: watmath.10045
Posted: Wed Nov 28 17:49:57 1984
Date-Received: Thu, 29-Nov-84 02:24:21 EST
References: <286@hwcs.UUCP> <5814@brl-tgr.ARPA> <9899@watmath.UUCP>, <4067@elsie.UUCP>
Organization: U of Waterloo, Ontario
Lines: 13

> From mark@elsie.UUCP (Mark J. Miller) Tue Nov 20 13:33:08 1984
> > 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!
> 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.
The fix to the shell doesn't affect behaviour with type-ahead.  How could it --
the shell hasn't even read the type-ahead!  ^Z still flushes it.
-- 
        -IAN!  (Ian! D. Allen)      University of Waterloo