Xref: utzoo comp.emacs:5596 gnu.emacs:603
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ukma!nrl-cmf!ames!think!barmar
From: barmar@think.COM (Barry Margolin)
Newsgroups: comp.emacs,gnu.emacs
Subject: Re: Query: Interesting Applications of Emacs
Message-ID: <37506@think.UUCP>
Date: 14 Mar 89 20:44:22 GMT
References: <1908@randvax.UUCP> <1296@cunixc.cc.columbia.edu>
Sender: news@think.UUCP
Reply-To: barmar@brigit.think.com.UUCP (Barry Margolin)
Organization: Thinking Machines Corporation, Cambridge, MA
Lines: 17

In article <1296@cunixc.cc.columbia.edu> seth@ctr.columbia.edu (Seth Robertson) writes:
>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.

All the special shell-mode commands are listed by C-h m (the command
to describe the current major mode) while in shell mode.  C-c C-c
kills the current job, C-c C-z suspends it, etc.  The standard
definitions of these have trouble when the jobs are setuid, though,
since they work by actually sending a signal.  I've got modified
versions that simply shove a C-c or C-z through the pty.

Barry Margolin
Thinking Machines Corp.

barmar@think.com
{uunet,harvard}!think!barmar