Path: utzoo!attcan!uunet!husc6!rice!titan!phil
From: phil@titan.rice.edu (William LeFebvre)
Newsgroups: comp.sys.amiga
Subject: Re: Job Control not needed(indeed?)
Message-ID: <2408@kalliope.rice.edu>
Date: 28 Dec 88 19:10:31 GMT
References: <3881@pt.cs.cmu.edu>
Sender: usenet@rice.edu
Reply-To: phil@Rice.edu (William LeFebvre)
Organization: Rice University, Houston
Lines: 26

In article <3881@pt.cs.cmu.edu> mjw@f.gp.cs.cmu.edu (Michael Witbrock) writes:
>ditto@cbmvax
>>Of course, AmigaDos doesn't have job control, either, and people
>>get along fine without it there....
>
>...It'd also be nice to be able to put things into the 
>background after you start them.

So start up another shell-in-a-window.  There should be a very easy way to
open another shell/CLI (via a hot key or menu item).  That way the old
window with the running program stays intact and input and output for the
old program don't get mixed up with new stuff.  This avoids alot of the
problems inherent in the BSD-style cshell job control paradigm.  "Now
which program did that output come from?  Darn, I forgot to set "tostop"!
Oh I need to put this one in the background so I can bring that other one
in the foreground to type my next line of input....let's see, that's "^Z",
"bg", "fg"---oops, wrong one---"^Z", "bg"---now which job was that?---
"jobs", "fg %4"; there we go.

Don't get me wrong:  I like job control.  But I like controlling multiple
processes via a mouse and windows better.

			William LeFebvre
			Department of Computer Science
			Rice University
			<phil@Rice.edu>