This distribution was built from GNU Emacs versiopn 18.41 with modifications. These modifications will probably show up in a later release of GNU Emacs as they get merged back into the new distributions from the Free Software Foundation This distribution tape is one backup saveset "emacs.bck". It was recorded at 1600 BPI. The saveset contains objects, but no executables. The objects were compiled on VMS 4.5, but with VMS4_0 defined. To get Emacs going you should: 1. Restore the save set back to disk. The saveset contains about 22,000 blocks. All of the Emacs files must be on the same directory tree. The distribution was created on a version 4.5 system. If you don't have enough room for all of the saveset copy at least: [distrib_gnuemacs.etc]*.* [distrib_gnuemacs.lisp]*.* [distrib_gnuemacs.src]*.* Once the saveset has been copied, you can probably safely delete the files in [.gdb] (GNU debugger), [.cpp] (C pre-processor), and [.shortnames] (programs for short names). Additionally, you might delete the files in [.man] if you don't have TeX. These are the sources for the manual. 2. Edit the file emacs.com in the top Emacs directory. It contains a "define" command to define the rooted directory "emacs_library". You should make this point to wherever Emacs has been copied to. Execute this command file. 3. If you are running on VMS 4.4 or later, then execute the file "rename.com" in the top level Emacs directory. This renames certain files that have "_" in their names to have "-" in their names instead. 4. Link the executables in [.etc]. The command file "link.com" should do this for you. If you have the VAX C compiler, then you can recompile the programs using "complink.com". Then run the file "makedoc.com" to create the doc files. 5. If you have the C compiler, edit "s_vms.h" in [.src] to indicate which version of VMS you are running on. Symbols of the form "VMS4_X" (where "X" is "0", "2", or "4") indicate which version of vms you are running. Again, if you have the C compiler, delete the objects and run the file "compile.com" to compile the source. You will get lots of compiler warnings for truncated symbols. Ignore them. 6. Create temacs.exe. Do this by executing the command file "link.com" in [.src]. You will see many warnings due to compilation warnings, ignore them. 7. Create temacs.dump. Do this by running "build.com". 8. Test emacs by first running "testemacs.com" (to set up a symbol). Actually start up the test version of emacs with "$ runtemacs". 9. Once you are sure that things are working,rename temacs.exe to [-]emacs.exe and temacs.dump to [-]emacs.dump. If you want to use pseudo terminals rather than mailboxes to talk to subprocesses, follow the directions in emacs_library:[ptydriver] to build and install the pseudo terminal drivers. Then define the variable "use-ptycom" to non-NIL. When you start up a subprocess you will then be using a pseudo terminal rather than a mailbox. It is important that you use the ptydriver in this directory. Earlier versions of the ptydriver would sometimes crash the system. Questions, suggestions and bug reports are welcome. If you are on a network send EMAIL, otherwise U.S. Mail, or a phone call are fine. My address is: Marty Sasaki Ziff Davis Technical Information Company 80 Blanchard Road Burlington, Massachusetts 01803 617-273-5500 sasaki@harvard.harvard.edu (arpa) ...harvard!sasaki (uucp) sasaki@harvunxh (bitnet) There are several mailing lists that deal with GNU Emacs, and GNU in general. To get on a mailing list send a request to the mailing list name with a "-request" added to the end of the name. To get on the vms-gnu-emacs mailing list (vms-gnu-emacs@harvard.harvard.edu), send a request to "vms-gnu-emacs-request@harvard.harvard.edu". Be sure to include in the text of your note the address that you want the postings to be sent to. Don't depend on your return address being correct, mailers sometimes hopelessly destroy return addresses. o info-gnu-emacs@prep.ai.mit.edu. This list talks about general things with GNU Emacs (all flavors), and announcements. This list is not for bug reports. o bug-gnu-emacs@prep.ai.mit.edu. Bugs and bug fixes are to be found on this list. Generally speaking, if you aren't interested in hacking on Emacs you shouldn't be on this list. o vms-gnu-emacs@harvard.harvard.edu. Talk about bugs and fixes that are specific to the VMS version. Cheers!