unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Heime <heimeborgia@protonmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Graph of elisp function calls
Date: Tue, 29 Aug 2023 08:13:15 +0000	[thread overview]
Message-ID: <KCBf-7CfAOWbFAQhCg7NqQz5z640aQB_tNGQrDRfiFFu-w2Z5PbwNm0sK4mOVRRFDLO1w_m1vCrJtDGsnKPtQ0K6m_lO4KU7npcRl4zF7y8=@protonmail.com> (raw)
In-Reply-To: <87ttsiy4x7.fsf@web.de>






Sent with Proton Mail secure email.

------- Original Message -------
On Tuesday, August 29th, 2023 at 2:10 PM, Michael Heerdegen <michael_heerdegen@web.de> wrote:


> Heime heimeborgia@protonmail.com writes:
> 
> > I understand now. The biggest question for me is what I need to do exactly.
> > Suppose I have some files in a directory, what do I need to do ?
> 
> 
> What do you want - what kind of information do you need?
> 
> Michael.

You mentioned byte compiling and the variable byte-compile-generate-call-tree

If I have a directory with elisp files in it, what would I have to do to
make to view the call tree graphically ?



  reply	other threads:[~2023-08-29  8:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-28 19:14 Graph of elisp function calls uzibalqa
2023-08-28 21:34 ` Rodrigo Morales
2023-08-28 23:25 ` Michael Heerdegen
2023-08-29  1:13   ` Heime
2023-08-29  1:50     ` Michael Heerdegen
2023-08-29  2:05       ` Heime
2023-08-29  2:10         ` Michael Heerdegen
2023-08-29  8:13           ` Heime [this message]
2023-08-30  0:45             ` Michael Heerdegen

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='KCBf-7CfAOWbFAQhCg7NqQz5z640aQB_tNGQrDRfiFFu-w2Z5PbwNm0sK4mOVRRFDLO1w_m1vCrJtDGsnKPtQ0K6m_lO4KU7npcRl4zF7y8=@protonmail.com' \
    --to=heimeborgia@protonmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.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).