From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: unconditionally loading help-fns.el
Date: Tue, 25 Oct 2005 03:25:49 -0400 [thread overview]
Message-ID: <87oe5egisn.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87br1e2k6l.fsf@pacem.orebokech.com> (Romain Francoise's message of "Tue, 25 Oct 2005 08:18:58 +0200")
>> And since leim-list.el uses eval-after-load very early during startup,
>> it means that help-fns.el gets unconditionally loaded during startup
>> (before we even read .emacs).
> Hmm... perhaps we should move this function to subr.el?
I guess so. But I'm also wondering whether it's right for leim-list.el to
use eval-after-load.
Stefan
next prev parent reply other threads:[~2005-10-25 7:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 4:29 unconditionally loading help-fns.el Stefan Monnier
2005-10-25 6:18 ` Romain Francoise
2005-10-25 7:25 ` Stefan Monnier [this message]
2005-10-25 20:28 ` Richard M. Stallman
2005-10-28 17:15 ` Romain Francoise
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=87oe5egisn.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
/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).