Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!bbn!gateway!dsys.icst.nbs.GOV!rbj
From: rbj@dsys.icst.nbs.GOV (Root Boy Jim)
Newsgroups: comp.emacs
Subject: Query: Interesting Applications of Emacs
Message-ID: <8904122051.AA25371@dsys.icst.nbs.gov>
Date: 12 Apr 89 20:51:48 GMT
Sender: news@bbn.COM
Organization: National Institute of Standards and Technology
	formerly National Bureau of Standards
Lines: 22

? From: Ashwin Ram <Ram-Ashwin@yale.arpa>

? 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.

As someone (Elz?) has already explained, job control is a useful feature
even in the presence of multiple windows. Consider a tar extract that is
running close to using all the available file space. You suspend it,
remove some files to free up space, and then resume it. I often run
multiple jobs that spit output to the shell, suspending each one
while starting up the next, then background them all.

	Root Boy Jim is what I am
	Are you what you are or what?