(eval-after-load): Doc fix.

diff --git a/lisp/ChangeLog b/lisp/ChangeLog
index 1589dae7ce84401b501677e7c5cb459e12fa2bf6..5d64c6c6443fb5df971eff71b26eae98cdea7488 100644 (file)
--- a/lisp/ChangeLog
+++ b/lisp/ChangeLog
@@ -1,3 +1,7 @@
+2009-07-06  Glenn Morris  <rgm@gnu.org>
+
+       * subr.el (eval-after-load): Doc fix.
+
 2009-07-05  Stefan Monnier  <monnier@iro.umontreal.ca>
 
        * files.el (find-alternate-file-other-window, find-alternate-file):

diff --git a/lisp/subr.el b/lisp/subr.el
index 6ca2284f4057c2cd348442b33a710311a7a2f67e..6d81f1ccfde51421aed3023a719378233d3a158b 100644 (file)
--- a/lisp/subr.el
+++ b/lisp/subr.el
@@ -1615,7 +1615,11 @@ extension for a compressed format \(e.g. \".gz\") on FILE will not affect
 this name matching.
 
 Alternatively, FILE can be a feature (i.e. a symbol), in which case FORM
-is evaluated whenever that feature is `provide'd.
+is evaluated whenever that feature is `provide'd.  Note that although
+provide statements are usually at the end of files, this is not always
+the case (e.g., sometimes they are at the start to avoid a recursive
+load error).  If your FORM should not be evaluated until the code in
+FILE has been, do not use the symbol form for FILE in such cases.
 
 Usually FILE is just a library name like \"font-lock\" or a feature name
 like 'font-lock.