From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: How to tell which *.el file loaded?
Date: Wed, 26 May 2004 11:43:16 +0200 [thread overview]
Message-ID: <86y8nfikwb.fsf@rumba.de.uu.net> (raw)
In-Reply-To: c91mju$i11$1@reader2.panix.com
bill <please_post@nomail.edu> writes:
> Is there a simple way to confirm which of several possible foo.el
> files in the system was loaded by (require 'foo) ? (I'm thinking
> along the lines of something I can stick in the desired foo.el that
> will confirm to me that it was it that was loaded by (require 'foo)
> .)
(message "Hi, I'm here.")
(sleep-for 3) ; 3 seconds
Please note that Emacs will load the *.elc file, if it exists. That
is, you may wish to re-byte-compile your foo.el, if it was
byte-compiled before.
Kai
next prev parent reply other threads:[~2004-05-26 9:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 9:05 How to tell which *.el file loaded? bill
2004-05-26 9:38 ` Lawrence Mitchell
2004-05-26 9:43 ` Kai Grossjohann [this message]
[not found] ` <mailman.7474.1085565100.1061.help-gnu-emacs@gnu.org>
2004-05-26 15:43 ` Kevin Rodgers
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=86y8nfikwb.fsf@rumba.de.uu.net \
--to=kai@emptydomain.de \
/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.
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).