Xref: utzoo comp.unix.wizards:18655 comp.sys.hp:3155 comp.lang.c:22752
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!apple!oliveb!tymix!cirrusl!sun505!dhesi
From: dhesi@sun505.UUCP (Rahul Dhesi)
Newsgroups: comp.unix.wizards,comp.sys.hp,comp.lang.c
Subject: Re: Job Control (a la csh/ksh) from within C
Message-ID: <966@cirrusl.UUCP>
Date: 12 Oct 89 19:57:44 GMT
References: <1719@zen.co.uk> <1989Oct3.153120.4750@utzoo.uucp> <320@sopwith.UUCP> <1989Oct6.164830.5856@utzoo.uucp> <2491@ibmpa.UUCP> <1989Oct12.022407.7989@utzoo.uucp>
Sender: news@cirrusl.UUCP
Reply-To: dhesi%cirrusl@oliveb.ATC.olivetti.com (Rahul Dhesi)
Organization: Cirrus Logic Inc.
Lines: 15

In article <1989Oct12.022407.7989@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:
>Well, if you *insist* on having them all on the screen at a time, of
>course they will.  Particularly on a 24x80 terminal, you wouldn't.
>Call them up when you need them.

Drat!  Got to get that 9600 bps modem fixed.

Oops...you need *two* of them!

Actually it turns out that job control is useful even in a windowing
environment.  With multiple windows, you can use job control in many
places instead of only one.

Rahul Dhesi <dhesi%cirrusl@oliveb.ATC.olivetti.com>
UUCP:  oliveb!cirrusl!dhesi