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: <1989Jun19.204430.6371@utzoo.uucp>
Organization: U of Toronto Zoology
References: <16497@louie.udel.EDU> <11989@bcsaic.UUCP> <2775@munnari.oz> <798@gara.une.oz> <8167@boring.cwi.nl> <1989Jun7.224933.700@utzoo.uucp> <1989Jun8.172420.27288@utzoo.uucp> <7652@bsu-cs.bsu.edu> <1989Jun10.063315.26085@utzoo.uucp> <7687@bsu-cs.bsu.edu>
Date: Mon, 19 Jun 89 20:44:30 GMT

In article <7687@bsu-cs.bsu.edu> dhesi@bsu-cs.bsu.edu (Rahul Dhesi) writes:
>Job control versus multiple windows is a false dichotomy because one
>does not exclude the other.

They merely duplicate each other.

>... If a program produces strictly sequential output, you only need to
>redraw it if it has scrolled off your screen or been overwritten by the
>output from some other screen-oriented program.  But this is not caused
>by job control, so job control should not be blamed for it.

Job control can quite fairly be blamed for failing to solve it, however.

>How do you make a log of everything you did in a terminal session in
>order while still using multiple windows?

How do you make such a log with ONE window if you're running screen-
oriented programs, like say a modern editor, whose i/o can't be logged
easily?  There just ain't no graceful way.
-- 
You *can* understand sendmail, |     Henry Spencer at U of Toronto Zoology
but it's not worth it. -Collyer| uunet!attcan!utzoo!henry henry@zoo.toronto.edu