jbf@ccieng5.UUCP (Jens Bernhard Fiederer) (03/29/84)
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. Azhrarn -- Reachable as ....allegra![rayssd,rlgvax]!ccieng5!jbf Or just address to 'native of the night' and trust in the forces of evil.
dave@utcsrgv.UUCP (Dave Sherman) (03/30/84)
~| 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!davegrunwald@uiuccsb.UUCP (04/01/84)
#R:ccieng5:-31900:uiuccsb:14900008:000:760 uiuccsb!grunwald Mar 31 12:32:00 1984 Horse hocky -- multi-edits is a great reason for job control. Consider using VI -- you may want to look at /usr/include/something.h while editing. Writing and escaping costs a lot, and you lose your place in your file. Hitting ^Z and then doing a more on the include file is a lot faster FOR ME, the user. Also, once you start having a network and you're logged into 3 or 4 machines at once, and you need to move between them quickly, you'll soon begin to appreciate job control. Having to logout of a rlogin session each time you want to hop to another machine for a quick peek at something would cost so much time and CPU power that you would never do it. dirk "I live my BSD" grunwald University of Illinois ihnp4!uiucdcs!grunwald grunwald.uiuc@CSNET
cowan@Udel-Relay.ARPA (04/03/84)
From: Ken Cowan <cowan@Udel-Relay.ARPA> I'll have to agree with JBF that job control is the greatest thing since the wheel. I don't think I ever sit down in front of my terminal without having multiple processes running. The biggest win is for program development. I always have the editor fired up on one job (where I switch between files, btw), and fire up make (often in backgroud) and still have my shell available for random things (mail and the like). I thought the references to blits were interesting. But seriously, can you imagine a university going that direction? It looks like this one is going the route of cheap terminals (Z19's, ADM5's). Ken