unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Jean-Christophe Helary <brandelune@gmail.com>,
	help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: RE: running my elisp step by step ?
Date: Fri, 7 Dec 2018 06:21:12 -0800 (PST)	[thread overview]
Message-ID: <9bf2a063-9987-459e-8db0-fe88f599e4fe@default> (raw)
In-Reply-To: <4624C4B0-4DA1-457A-9F6B-3A7F9AE4FE63@gmail.com>

> Is there a way to run my elisp step by step and to see how all the
> variables are changing as I step through the code ?

`M-x debug-on-entry SOME-FUNCTION'

Or insert calls to `debug' anywhere in source code,
to enter the code there.  This is helpful, for
example, to debug what happens in an `interactive'
spec (since `debug-on-entry' kicks in only after
the `interactive' spec has done its thing).

See (elisp) `Invoking the Debugger':

https://www.gnu.org/software/emacs/manual/html_node/elisp/Invoking-the-Debugger.html



      parent reply	other threads:[~2018-12-07 14:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-07  5:43 running my elisp step by step ? Jean-Christophe Helary
2018-12-07  6:23 ` Alexis
2018-12-07 13:25   ` Jean-Christophe Helary
2018-12-07 14:21 ` Drew Adams [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=9bf2a063-9987-459e-8db0-fe88f599e4fe@default \
    --to=drew.adams@oracle.com \
    --cc=brandelune@gmail.com \
    --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).