Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!hc!lll-winken!uunet!yale!Ram-Ashwin
From: Ram-Ashwin@cs.yale.edu (Ashwin Ram)
Newsgroups: comp.emacs
Subject: Re: Query: Interesting Applications of Emacs
Summary: Job control -- obsolete?
Keywords: job control
Message-ID: <53831@yale-celray.yale.UUCP>
Date: 16 Mar 89 14:52:23 GMT
References: <1908@randvax.UUCP> <1296@cunixc.cc.columbia.edu>
Sender: root@yale.UUCP
Reply-To: Ram-Ashwin@cs.yale.edu (Ashwin Ram)
Organization: Computer Science, Yale University, New Haven, CT 06520-2158
Lines: 21
In-reply-to: sethr@cunixc.cc.columbia.edu (Seth Robertson)

In article <1296@cunixc.cc.columbia.edu>, sethr@cunixc.cc.columbia.edu (Seth Robertson) writes:
> In article <1908@randvax.UUCP> salzman@rand.org (Isaac Salzman) writes:
> >Hello netland! Does anyone really use Emacs as a login shell?
> 
> If it wern't for ksh, I might actually do that IF emacs had job
> control!!  When you can't suspend or background or even cancel(!) a
> job, the shell mode isn't really usuable.
> 
> Of course if I just havn't RTFM (I have, though) and there is a way to
> use job control, then please tell me.

GNU Emacs does allow job control in a shell, but I'm curious why this is
needed at all.  Job control, as far as I can see, is a hangover from the days
of one-window terminals.  Since Emacs gives you multiple windows, it's just
as easy, and far more natural, to use different windows for different jobs
you want running at the same time.  These jobs can be run as processes in
individual windows, or you can just start up a new shell and run each job in
its own shell with its own window.  I've never felt the need to do
complicated job management within a single shell window.

-- Ashwin.