Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!rochester!pt.cs.cmu.edu!andrew.cmu.edu!bader+
From: bader+@andrew.cmu.edu (Miles Bader)
Newsgroups: comp.sys.amiga
Subject: Re: Job Control not needed(indeed?)
Message-ID: <AXixloy00UkaQhRTJL@andrew.cmu.edu>
Date: 30 Dec 88 19:43:48 GMT
References: <3881@pt.cs.cmu.edu>,
	<2408@kalliope.rice.edu>
Organization: Carnegie Mellon
Lines: 21
In-Reply-To: <2408@kalliope.rice.edu>

phil@titan.rice.edu (William LeFebvre) writes:
> >...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.

The time that I want job-control the most is when I *forget* to RUN a
program that opens its own window (and so does NO i/o to the original
cli window), but doesn't fork.  Even if I could start up a new cli
with a keystroke, I don't want to leave a cli window sitting around
doing nothing [and the orig cli has useful state, like conman command
history].  Often I realize my mistake after being in the program for a
while; it's usually a pain to exit and restart using RUN (and
sometimes, I run a program that CAN'T be stopped... Reboot time!).  It
would be MOST convenient to be able to put these things into the
background after-the-fact-- JOB CONTROL!

-Miles