From: Marc Tfardy <m-t-o@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Tool for ELISP code analysis
Date: Tue, 06 Mar 2007 23:30:39 +0100 [thread overview]
Message-ID: <5567ttF22o99fU1@mid.individual.net> (raw)
In-Reply-To: <yoijabyr436x.fsf@gamma02.me.chalmers.se>
Johan Bockgård wrote:
> Marc Tfardy <m-t-o___CUT__IT___@web.de> writes:
>
>> I try to understand some (complicated) ELISP code with many lines of
>> code and many functions. It is not easy to keep overview of the
>> function calls and dependecies between functions/variables. Is there
>> maybe a Emacs tool for ELISP code analysis?
>
>
> ,----[ C-h v byte-compile-generate-call-tree RET ]
> | byte-compile-generate-call-tree is a variable defined in `bytecomp.el'.
> | Its value is nil
> [...]
>
> Also http://whome.phys.au.dk/~harder/who-calls.el
Thanks a lot! It's incredible, that so many things exists ready
to use out of the box. It is nearly exactly what I need!
regards
Marc
prev parent reply other threads:[~2007-03-06 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 12:21 Tool for ELISP code analysis Marc Tfardy
2007-03-06 0:37 ` Johan Bockgård
2007-03-06 22:30 ` Marc Tfardy [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=5567ttF22o99fU1@mid.individual.net \
--to=m-t-o@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).