all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Reuben Thomas <rrt@sc3d.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: 7986@debbugs.gnu.org
Subject: bug#7986: 23.2.91; Remove unwise advice from manual
Date: Fri, 4 Feb 2011 23:59:59 +0000	[thread overview]
Message-ID: <AANLkTi=pOpFqN2F4Z-w8E_Uh4Ns2ZgAdk3NCn1fTT-2b@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimso0qhMafK5SeZn6bcLnerySEtOxn7gueaQRSH@mail.gmail.com>

On 4 February 2011 23:57, Lennart Borgman <lennart.borgman@gmail.com> wrote:
> On Sat, Feb 5, 2011 at 12:26 AM, Reuben Thomas <rrt@sc3d.org> wrote:
>>
>>   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::).
>
> You can't do that. Just imagine you write a library with one single
> purpose: doing something after another library is loaded.

I don't think that is at odds with the advice "Normally, well-designed
Lisp programs should not use `eval-after-load'." But if it is, then
the manual should be corrected.

However, that does not affect my suggestion that the advice about
writing code for "personal customizations" be removed.

-- 
http://rrt.sc3d.org





  reply	other threads:[~2011-02-04 23:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04 23:26 bug#7986: 23.2.91; Remove unwise advice from manual Reuben Thomas
2011-02-04 23:57 ` Lennart Borgman
2011-02-04 23:59   ` Reuben Thomas [this message]
2011-02-09  0:28 ` Chong Yidong

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=pOpFqN2F4Z-w8E_Uh4Ns2ZgAdk3NCn1fTT-2b@mail.gmail.com' \
    --to=rrt@sc3d.org \
    --cc=7986@debbugs.gnu.org \
    --cc=lennart.borgman@gmail.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.