CSH -- stopping job in SOURCE'd file

[idallen at watmath.UUCP]

> From ron at brl-tgr.ARPA (Ron Natalie <ron>) Thu Nov 15 20:06:27 1984
> > Not only will C be thrown away if you stop B in the following:
> > 
> >     a ; b ; c
> > 
> > ...but if you stop a job executing from in a SOURCE'd file, the rest
> > of the file gets thrown away too.  This can be really annoying if
> > you read your mail or news in your .login, and stop either...
> >         -IAN!  (Ian! D. Allen)      University of Waterloo
> It is totally understandable that this happens.  If you think about it,
> it has to.  Berkeley Job control doesn't provide for the switching of
> input streams.
> If you need a method of thinking about it, just remember that shell
> input is dealt with upon a stop as if an "interrupt" had occured.

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