home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.vms
- Path: sparky!uunet!cis.ohio-state.edu!pacific.mps.ohio-state.edu!pacific.mps.ohio-state.edu!davis
- From: davis@pacific.mps.ohio-state.edu ("John E. Davis")
- Subject: Re: EMACS as default mail editor?
- In-Reply-To: louis@BARRA.COM's message of 7 Nov 92 22:50:40 GMT
- Message-ID: <DAVIS.92Nov7203733@pacific.mps.ohio-state.edu>
- Sender: news@pacific.mps.ohio-state.edu
- Nntp-Posting-Host: pacific.mps.ohio-state.edu
- Reply-To: davis@pacific.mps.ohio-state.edu (John E. Davis)
- Organization: "Dept. of Physics, The Ohio State University"
- References: <9211072250.AA13539@hermann.barra.COM>
- Date: Sun, 8 Nov 1992 01:37:33 GMT
- Lines: 26
-
- In article <9211072250.AA13539@hermann.barra.COM> louis@BARRA.COM (Louis
- Dunne) writes:
-
- BUT, in reality most editors you will use will have been written using
- TPU, your version of EMACS included. Usually you will have (or you can
- [...]
- So, the bottom line is:
- 1) If you don't mind the overhead, use the MAIL$EDIT
- approach.
-
- Perhaps his version of EMACS is written in TPU but I find it hard to believe
- since it would hardly be EMACS.
-
- JED uses the MAIL$EDIT approach. However, the editor is not spawned in the
- command file--- rather the command file attaches itself to JED setting a
- logical to instruct JED to reattach back to the command procedure rather than
- the process which called it.
-
- --
- _____________
- #___/John E. Davis\_________________________________________________________
- #
- # internet: davis@amy.tch.harvard.edu
- # bitnet: davis@ohstpy
- # office: 617-735-6746
- #
-