changeset 10659:a0efedb217ed

Explain load-path and dumping.
author Richard M. Stallman <rms@gnu.org>
date Sat, 04 Feb 1995 08:14:52 +0000
parents 1912b355d49c
children 0501556eef3a
files lispref/loading.texi
diffstat 1 files changed, 12 insertions(+), 0 deletions(-) [+]
line wrap: on
line diff
--- a/lispref/loading.texi	Sat Feb 04 02:08:29 1995 +0000
+++ b/lispref/loading.texi	Sat Feb 04 08:14:52 1995 +0000
@@ -172,6 +172,18 @@
 to the front of @code{load-path} so the file can be found there.  Newer
 Emacs versions also find such files in the current directory, but
 without altering @code{load-path}.
+
+Dumping Emacs uses a special value of @code{load-path}.  If the value of
+@code{load-path} at the end of dumping is unchanged (that is, still the
+same special value), the dumped Emacs switches to the ordinary
+@code{load-path} value when it starts up, as decribed above.  But if
+@code{load-path} has any other value at the end of dumping, that value
+is used for execution of the dumped Emacs also.
+
+Therefore, if you want to change @code{load-path} temporarily for
+loading a few libraries in @file{site-init.el} or @file{site-load.el},
+you should bind @code{load-path} locally with @code{let} around the
+calls to @code{load}.
 @end defopt
 
 @defvar load-in-progress