How to get recursive load level?

How to get recursive load level?

[Michael Heerdegen]

Hello,

I want to show a tree of recently loaded elisp files in a log buffer.
The tree structure should show which file was loaded by another one.
For this purpose, it is sufficient to know the recursive load level of
each file (and the loading order, which is trivial).  Is there any mean
to get that information more or less directly?

I have a working, but ugly solution: to `after-load-functions' I add a
function like

(lambda (file)
  (push (cons load-file-name file) temp-load-hist))

When the hook is run, `file' is bound to the file that was loaded, and
`load-file-name' to the file that loaded it, or nil when it was loaded
directly.  Afterwards, I scan `temp-load-hist' and reconstruct the load
tree.  This is very fragile - can it be done better?  Please also
answer when you think "no".

Second question: is there a mean to run a function directly before a
file is loaded?  I don't want to advice `load', and there is no hook.
Because I would want to write

  Loading ...

rather than afterwards

  Loaded ...

in my log buffer.


Thanks,

Michael.

Re: How to get recursive load level?

[Stefan Monnier]

> I have a working, but ugly solution: to `after-load-functions' I add a
> function like
> (lambda (file)
>   (push (cons load-file-name file) temp-load-hist))
[...]
> tree.  This is very fragile - can it be done better?  Please also

That sounds like a reasonable solution.
There are other hacks possible, such as advising load, of course, or
using backtrace-frame (see code around macroexp--trim-backtrace-frame).


        Stefan

Re: How to get recursive load level?

[Michael Heerdegen]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> > I have a working, but ugly solution: to `after-load-functions' I add a
> > function like
> > (lambda (file)
> >   (push (cons load-file-name file) temp-load-hist))
> [...]
> > tree.  This is very fragile - can it be done better?  Please also
>
> That sounds like a reasonable solution.
> There are other hacks possible, such as advising load, of course, or
> using backtrace-frame (see code around macroexp--trim-backtrace-frame).

Ok, thanks.  I think I'll keep what I have, since the other hacks are
even hackier.


Regards,

Michael.