home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.vms
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!caen!nic.umass.edu!news.amherst.edu!twpierce
- From: twpierce@unix.amherst.edu (Tim Pierce)
- Subject: Re: What should be in login.com?
- Message-ID: <BzJKMu.Iq7@unix.amherst.edu>
- Organization: Elitist Usenet Administrators, Turkey Division
- References: <1992Dec16.104051.333@csghsg5a.bitnet> <1992Dec18.105507.7408@cronkite.ocis.temple.edu> <1992Dec18.230714.19508@chpc.utexas.edu>
- Date: Sun, 20 Dec 1992 05:01:42 GMT
- Lines: 19
-
- In article <1992Dec18.230714.19508@chpc.utexas.edu> michael@chpc.utexas.edu (Michael Lemke) writes:
-
- >In article <1992Dec18.105507.7408@cronkite.ocis.temple.edu> linnoise@bigboy (LN) writes:
- >
- >>Anything you want. I have mine set up logicals and symbols to access dirs
- >>that have very long names, prompt me for various things like enabling OPCOM
- >>(check for interactive mode before prompting!), setting up mail to use EVE,
- > ^^^^^^^^^^^^^^^^^^^^^^^^^^
- >Why do you do this in LOGIN.COM? SET EDITOR TPU in *MAIL* exactly once
- >is all you need. It is remembered "for ever".
-
- Unless you want to use customized section files or the like. The only
- way I've found to do this (to enable quoting, signature files, and the
- like) is with the logical MAIL$EDIT.
-
- --
- ____ Tim Pierce /
- \ / twpierce@unix.amherst.edu / Rocks say goodbye.
- \/ (BITnet: TWPIERCE@AMHERST) /
-