Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site utcsrgv.UUCP
Path: utzoo!utcsrgv!dave
From: dave@utcsrgv.UUCP (Dave Sherman)
Newsgroups: net.unix-wizards
Subject: Re: BSD job control
Message-ID: <3657@utcsrgv.UUCP>
Date: Fri, 30-Mar-84 10:54:45 EST
Article-I.D.: utcsrgv.3657
Posted: Fri Mar 30 10:54:45 1984
Date-Received: Fri, 30-Mar-84 11:58:49 EST
References: <319@ccieng5.UUCP>
Organization: The Law Society of Upper Canada, Toronto
Lines: 23

~|  From: jbf@ccieng5.UUCP (Jens Bernhard Fiederer)
~|  I regard job control as the single most important extension I have come
~|  across.  It has made my work considerably simpler.  Want to test your
~|  record locking algorithms for conflict resolution?  No need to get two
~|  terminals (or a blit)!  Want to edit several files at once?
~|
~|  How anybody can flame at this facility is beyond me.

I rarely need to test record locking. But I do edit several files at
once. Using job control for this is the wrong approach, since you
don't have the right co-ordination between all the files you're working
on. (I use qed all the time on multiple files, on an 11/23 as well as
a VAX.)

Anyway, you can always escape from any editor to invoke another instance
of it.

I don't deny that job control has its uses. But editing multiple files
sure isn't a justification.

Dave Sherman
-- 
 {allegra,cornell,decvax,ihnp4,linus,utzoo}!utcsrgv!dave