From: Jean-Christophe Helary <brandelune@gmail.com>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>
Subject: Re: running my elisp step by step ?
Date: Fri, 7 Dec 2018 22:25:40 +0900 [thread overview]
Message-ID: <DDB1FFB2-77C8-4311-9696-17AF491B1212@gmail.com> (raw)
In-Reply-To: <87muphua6x.fsf@ada>
> On Dec 7, 2018, at 15:23, Alexis <flexibeast@gmail.com> wrote:
>
> Jean-Christophe Helary <brandelune@gmail.com> writes:
>
>> 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 ?
>
> Edebug:
>
> https://www.gnu.org/software/emacs/manual/html_node/elisp/Edebug.html
Thank you. I had read about it and probably missed something because I could not make it work at my first attempt. Hence my question.
Thank you *so* much. It took me just 1 minute to find a silly bug I had introduced in my code.
Jean-Christophe Helary
-----------------------------------------------
http://mac4translators.blogspot.com @brandelune
next prev parent reply other threads:[~2018-12-07 13:25 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 [this message]
2018-12-07 14:21 ` Drew Adams
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=DDB1FFB2-77C8-4311-9696-17AF491B1212@gmail.com \
--to=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).