From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
To: Emacs-Devel devel <emacs-devel@gnu.org>
Subject: debugging elisp ?
Date: Sun, 9 Jul 2017 17:03:04 +0900 [thread overview]
Message-ID: <E38B67AA-64E0-4995-A29D-E353AE143FEB@gmail.com> (raw)
Is there a way to run a given package/file step by step and see how variables etc. evolve ?
Practically speaking I'm running package.el and I'd like to have a separate buffer where I see how things move under the hood.
Jean-Christophe
next reply other threads:[~2017-07-09 8:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-09 8:03 Jean-Christophe Helary [this message]
2017-07-09 9:44 ` debugging elisp ? Marcin Borkowski
2017-07-09 10:49 ` Jean-Christophe Helary
2017-07-09 11:48 ` Noam Postavsky
2017-07-09 11:58 ` Jean-Christophe Helary
2017-07-09 11:59 ` Marcin Borkowski
2017-07-09 12:13 ` Noam Postavsky
2017-07-09 13:54 ` Jean-Christophe Helary
2017-07-10 13:31 ` Michael Heerdegen
2017-07-11 1:06 ` Jean-Christophe Helary
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=E38B67AA-64E0-4995-A29D-E353AE143FEB@gmail.com \
--to=jean.christophe.helary@gmail.com \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).