Newsgroups: comp.os.minix
Path: utzoo!henry
From: henry@utzoo.uucp (Henry Spencer)
Subject: Re: job control is a bug, not a feature
Message-ID: <1989Jun21.165326.1650@utzoo.uucp>
Organization: U of Toronto Zoology
References: <1989Jun19.204430.6371@utzoo.uucp> <15868@vail.ICO.ISC.COM>
Date: Wed, 21 Jun 89 16:53:26 GMT

In article <15868@vail.ICO.ISC.COM> scottw@ico.ISC.COM (Scott Wiesner) writes:
>This is all just too much.  Job control with or without a windowing
>system is a useful tool.  Just yesterday, I was doing a large build
>on my system, when I decided I wanted to run a timing test on something
>else.  If I had had job control, this would have been a simple matter
>of doing a ^Z, running my test, and continuing the build...

Nobody, including me -- please *read* my postings, especially the long
one -- is arguing that the ability to suspend jobs is not useful.  But
that is about 2% of job control.  The trouble comes when you stir that
together with screen updating and multiplexing, yielding a big mess.
-- 
NASA is to spaceflight as the  |     Henry Spencer at U of Toronto Zoology
US government is to freedom.   | uunet!attcan!utzoo!henry henry@zoo.toronto.edu
