Path: utzoo!utgpu!watmath!iuvax!bsu-cs!dhesi
From: dhesi@bsu-cs.bsu.edu (Rahul Dhesi)
Newsgroups: comp.os.minix
Subject: Re: job control is a bug, not a feature
Message-ID: <7652@bsu-cs.bsu.edu>
Date: 8 Jun 89 23:18:47 GMT
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>
Reply-To: dhesi@bsu-cs.bsu.edu (Rahul Dhesi)
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 18

Henry Spencer's article contains some explicit and implicit assumptions
that I will counter briefly:

1.   Job control versus multiple windows is a false dichotomy.
2.   Each and every program does not need special code to deal with
     job control.  Only programs that change terminal settings,
     and privileged programs that should not be interrupted by
     unprivileged users, need such code.
3.   Multiple windows are useless at 1200 bps.
4.   Multiple windows are useless on a hardcopy terminal.

The best solution is to allow multiple windows, and job control within
each.  This lets the user decide which to use:  multiple windows only,
or job control only, or a combination of both.
-- 
Rahul Dhesi <dhesi@bsu-cs.bsu.edu>
UUCP:    ...!{iuvax,pur-ee}!bsu-cs!dhesi
Career change search is on -- ask me for my resume