unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: wgreenhouse-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org (W. Greenhouse)
To: help-gnu-emacs-mXXj517/zsQ@public.gmane.org
Subject: Re: log full path of magically loaded files?
Date: Tue, 26 Mar 2013 14:48:27 +0000	[thread overview]
Message-ID: <87fvzib4jo.fsf@riseup.net> (raw)
In-Reply-To: 06d6bc48-a54e-4e08-a2e5-9a2d6a840eef@googlegroups.com

Dan,

danmbox-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org writes:

> I suspect emacs is loading the wrong version of some file (an
> autoloaded major mode). However, I see no relevant trace in *Messages*
> when opening a file that triggers the autoload.
>
> If I (require 'some-mode) (from the *scratch* buffer), still nothing
> appears in *Messages*. If I (load "some-mode"), I finally get the
> useless
>
> Loading some-mode... done.
>
> (useless because I want the full path). Is there a way to enable more
> extensive logging of implicit emacs actions?

The `load-history' variable documents every `load' and `require' event
(and a lot else besides), with full paths, back to the initialization of
Emacs.

Since that's probably *too much* information, a quicker path to the
problem you're actually trying to tackle with relation to major modes is
M-x list-load-path-shadows, which shows you when the same library was
eligible to be loaded from more than one directory and some versions are
now being ignored due to the load-path setting (i.e. "shadowed").

Best,
Will

-- 
BOFH excuse #378:

Operators killed by year 2000 bug bite.




      parent reply	other threads:[~2013-03-26 14:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25 16:49 log full path of magically loaded files? danmbox
2013-03-25 17:10 ` Alan Mackenzie
2013-03-25 19:42   ` danmbox
2013-03-25 19:56     ` Alan Mackenzie
2013-03-25 20:50       ` danmbox
2013-03-26  3:35         ` Barry Margolin
2013-03-26 14:48 ` W. Greenhouse [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=87fvzib4jo.fsf@riseup.net \
    --to=wgreenhouse-sgozh3hwpm2stnjn9+bgxg@public.gmane.org \
    --cc=help-gnu-emacs-mXXj517/zsQ@public.gmane.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).