GNU bug report logs - #10982
documentation bug eval-after-load

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 10982 in the body.
You can then email your comments to 10982 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Le Wang <l26wang <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: documentation bug eval-after-load
Date: Sat, 10 Mar 2012 01:33:30 +0800

[Message part 1 (text/plain, inline)]

Hi on this page:

http://www.gnu.org/software/emacs/manual/html_node/elisp/Hooks-for-Loading.html#Hooks-for-Loading

> library can also be a feature (i.e. a symbol), in which case form is
evaluated when (provide library) is called.

Then on this page
http://www.gnu.org/software/emacs/manual/html_node/elisp/Named-Features.html

> This function announces that feature is now loaded, or being loaded, into
the current Emacs session. This means that the facilities associated with
feature are or will be available for other Lisp programs.

So two issue come up:  should symbol even be supported by `eval-after-load`
if the feature might not be finished loading?  If it has to be kept for
backward compatibility, documentation should explicitly say don't use
symbol because the feature might not be finished loading.

-- 
Le

[Message part 2 (text/html, inline)]

Message #8 received at 10982 <at> debbugs.gnu.org (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: Le Wang <l26wang <at> gmail.com>
Cc: 10982 <at> debbugs.gnu.org
Subject: Re: bug#10982: documentation bug eval-after-load
Date: Fri, 09 Mar 2012 12:40:50 -0500

Le Wang wrote:

> So two issue come up:  should symbol even be supported by `eval-after-load`
> if the feature might not be finished loading?  If it has to be kept for
> backward compatibility, documentation should explicitly say don't use
> symbol because the feature might not be finished loading.

The version of eval-after-load in the trunk handles this better, so that
even if provide is not at the end of the file, the eval-after-load forms
do not run until the file has finished loading.

What is the second issue?

Message #11 received at 10982 <at> debbugs.gnu.org (full text, mbox):

From: Le Wang <l26wang <at> gmail.com>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 10982 <at> debbugs.gnu.org
Subject: Re: bug#10982: documentation bug eval-after-load
Date: Sat, 10 Mar 2012 02:01:02 +0800

[Message part 1 (text/plain, inline)]

On Sat, Mar 10, 2012 at 1:40 AM, Glenn Morris <rgm <at> gnu.org> wrote:

> Le Wang wrote:
>
> > So two issue come up:  should symbol even be supported by
> `eval-after-load`
> > if the feature might not be finished loading?  If it has to be kept for
> > backward compatibility, documentation should explicitly say don't use
> > symbol because the feature might not be finished loading.
>
> The version of eval-after-load in the trunk handles this better, so that
> even if provide is not at the end of the file, the eval-after-load forms
> do not run until the file has finished loading.
>
> What is the second issue?
>

Sorry, the two issues are documentation and implementation. Clearly the
implementation has been fixed, I just checked that the documentation is
also correct.  Please close this bug.

-- 
Le

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.