Path: utzoo!utgpu!watmath!uunet!mcvax!hp4nl!ruuinf!piet
From: piet@ruuinf (Piet van Oostrum)
Newsgroups: gnu.emacs
Subject: Re: Multiple shells
Message-ID: <1202@ruuinf.UUCP>
Date: 17 Mar 89 07:58:08 GMT
References: <8903160713.AA03138@la.tis.com>
Sender: piet@ruuinf.UUCP
Reply-To: piet@ruuinf (Piet van Oostrum)
Distribution: gnu
Organization: Dept of Computer Science, University of Utrecht, Holland
Lines: 31
In-reply-to: ho@LA.TIS.COM (Hilarie K. Orman)

In article <8903160713.AA03138@la.tis.com>, ho@LA (Hilarie K. Orman) writes:
 `It is relatively easy to hack shell.el to allow multiple shell
 `processes, each in its own buffer.  This largely eliminates the need
 `for job control, and it is an excellent way of organizing one's work.
 `I normally work with 2-5 shells at a time.  Does anyone else work this
 `way? 

Yes, I have a command that spawns a (C-)shell and remembers the current
directory in the buffer name. So I usually have a shell running on each
directory where I am issueing commands.

(defun csh ()
  "Run an inferior c-shell.
The buffer is put in shell-mode, giving commands for sending input
and controlling the subjobs of the shell.  See shell-mode.
See also variable shell-prompt-pattern.
Note that many people's .cshrc files unconditionally clear the prompt.
If yours does, you will probably want to change it."
  (interactive)
  (require 'shell)
  (switch-to-buffer
   (let ((name "csh"))
     (make-shell (concat name "-" default-directory)
		 name
		 (if (file-exists-p (concat "~/.emacs_" name))
		     (concat "~/.emacs_" name))
		 "-i"))))
-- 
Piet van Oostrum, Dept of Computer Science, University of Utrecht
Padualaan 14, P.O. Box 80.089, 3508 TB Utrecht, The Netherlands
Telephone: +31-30-531806. piet@cs.ruu.nl (mcvax!hp4nl!ruuinf!piet)