From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Tracing what is loading
Date: Mon, 08 Dec 2008 19:21:03 +0100 [thread overview]
Message-ID: <vs7vdtuedf4.fsf@ppc228.mipool.uni-jena.de> (raw)
In-Reply-To: mailman.2193.1228712089.26697.help-gnu-emacs@gnu.org
Please note that there already _is_ a message for every file loaded. But
because the *Messages* buffer only shows the last 50 (or so) messages,
you can't see them because starting up causes quite more messages.
Indeed all you need is `load-history'. Due to the internal structure of
lists, the last item belongs to the first load file and vice versa, so you
must read it bottom up.
I have written a command which only shows the files, in the right order:
(defun list-load-files () (interactive)
(with-current-buffer
(get-buffer-create "*Load History*")
(erase-buffer)
(insert (format "%s" "Load History\n============\n\n"))
(mapc
(lambda (x) (insert (format "%s\n" (car x))))
(reverse load-history))
(pop-to-buffer (current-buffer))))
You can eval it with M-:. Call it with M-x list-load-files.
The listing should cover all lisp files ever loaded after startup.
next prev parent reply other threads:[~2008-12-08 18:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2095.1228610078.26697.help-gnu-emacs@gnu.org>
2008-12-07 10:01 ` Tracing what is loading Dmitry Dzhus
2008-12-07 13:10 ` Michael Heerdegen
2008-12-08 4:54 ` Harry Putnam
[not found] ` <mailman.2193.1228712089.26697.help-gnu-emacs@gnu.org>
2008-12-08 18:21 ` Michael Heerdegen [this message]
2008-12-08 20:09 ` Harry Putnam
2008-12-09 6:30 ` Harry Putnam
2008-12-10 2:56 ` Kevin Rodgers
2008-12-10 8:47 ` Harry Putnam
[not found] ` <mailman.2437.1228898847.26697.help-gnu-emacs@gnu.org>
2008-12-10 19:14 ` Michael Heerdegen
2008-12-11 1:46 ` Harry Putnam
2008-12-07 0:34 Harry Putnam
2008-12-07 9:58 ` Juanma Barranquero
2008-12-07 23:09 ` Harry Putnam
2008-12-08 0:41 ` Juanma Barranquero
2008-12-08 4:46 ` Harry Putnam
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=vs7vdtuedf4.fsf@ppc228.mipool.uni-jena.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@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.
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).