diff options
| author | Karl Heuer <kwzh@gnu.org> | 1996-02-20 19:13:05 +0000 |
|---|---|---|
| committer | Karl Heuer <kwzh@gnu.org> | 1996-02-20 19:13:05 +0000 |
| commit | d0e1859d717b5c63f124c74720117892a6a2507f (patch) | |
| tree | e31b57a0a45c3efb493ec619edf256b4588b634c | |
| parent | dc1a3a24fb99b4e808848323e9cc3118a87ffc15 (diff) | |
| download | emacs-d0e1859d717b5c63f124c74720117892a6a2507f.tar.gz | |
Clarify info about MS-DOS path handling.
| -rw-r--r-- | INSTALL | 8 |
1 files changed, 7 insertions, 1 deletions
@@ -538,7 +538,13 @@ problem too late to include a more convenient fix--sorry. To save disk space, Emacs is built with the idea that you will execute it from the same place in the file system where you built it. As the /usr/local/ subtree does not exist on most MSDOG systems, the -executables are placed in /emacs/bin/. +executables might be placed in /emacs/bin/, for instance, in which +case there should also be /emacs/lisp, /emacs/info and /emacs/etc +directories. In general, with the default path handling, the etc/, +info/ and lisp/ directories are expected to exist in ../ relative to +the directory containing the executing binary. This behaviour can be +overridden by setting the HOME environment variable to the directory +containing lisp/ etc. MSDOG is a not a multitasking operating system, so Emacs features such as asynchronous subprocesses that depend on multitasking will not |