From 995c07fce05ce39adaba3498ce45cd86a0a300a0 Mon Sep 17 00:00:00 2001 From: Glenn Morris Date: Mon, 6 Jul 2009 00:45:33 +0000 Subject: [PATCH] (eval-after-load): Doc fix. --- lisp/ChangeLog | 4 ++++ lisp/subr.el | 6 +++++- 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/lisp/ChangeLog b/lisp/ChangeLog index 1589dae7ce8..5d64c6c6443 100644 --- a/lisp/ChangeLog +++ b/lisp/ChangeLog @@ -1,3 +1,7 @@ +2009-07-06 Glenn Morris + + * subr.el (eval-after-load): Doc fix. + 2009-07-05 Stefan Monnier * files.el (find-alternate-file-other-window, find-alternate-file): diff --git a/lisp/subr.el b/lisp/subr.el index 6ca2284f405..6d81f1ccfde 100644 --- 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. -- 2.39.2