From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 20038@debbugs.gnu.org
Subject: bug#20038: 25.0.50; (elisp) `Hooks for Loading' not updated correctly
Date: Sat, 30 Apr 2016 19:19:23 +0200 [thread overview]
Message-ID: <87lh3vf204.fsf@gnus.org> (raw)
In-Reply-To: <fc26180c-c947-413d-a596-5da5b9d95f44@default> (Drew Adams's message of "Sun, 8 Mar 2015 09:27:48 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
> 1. All doc describing `eval-after-load' was removed from the Elisp
> manual. And doc for `with-eval-after-load' was added (OK).
>
> Unfortunately this paragraph was not updated or removed. It presumably
> applies equally to `with-eval-afer-load':
>
> Normally, well-designed Lisp programs should not use
> `eval-after-load'. If you need to examine and set the variables
> defined in another library (those meant for outside use), you can do it
> immediately--there is no need to wait until the library is loaded. If
> you need to call functions defined by that library, you should load the
> library, preferably with `require' (*note Named Features::).
I've now updated this.
> 2. Although the doc describing `eval-after-load' was removed, and
> `eval-after-load' was removed from the index, there remain mentions of
> `eval-after-load' in the manual, with cross-references to the node that
> *used to* describe it, so you can find out more about it (but you
> cannot). Node `Named Features', for example. And node `Coding
> Conventions'.
I've now replaced virtually all mentions of `eval-after-load' with
`with-eval-after-load' in the manual.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2016-04-30 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 16:27 bug#20038: 25.0.50; (elisp) `Hooks for Loading' not updated correctly Drew Adams
2016-04-30 17:19 ` Lars Ingebrigtsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lh3vf204.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=20038@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).