From: Eli Zaretskii <eliz@gnu.org>
To: Jean-Christophe Helary <lists@traduction-libre.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs development...
Date: Sat, 21 Aug 2021 11:10:10 +0300 [thread overview]
Message-ID: <83k0kfz09p.fsf@gnu.org> (raw)
In-Reply-To: <F137D66F-9CA8-490A-9295-1903698A9CA8@traduction-libre.org> (message from Jean-Christophe Helary on Sat, 21 Aug 2021 16:08:54 +0900)
> From: Jean-Christophe Helary <lists@traduction-libre.org>
> Date: Sat, 21 Aug 2021 16:08:54 +0900
> Cc: emacs-devel@gnu.org
>
> But when I run package.el to test it, I'd like to have a way to examine the values of variables as they evolve. Right now I use message and check the *Messages* buffer... It is not ideal.
>
> And there are probably a few other things that would make work easier but that I am not aware of because I am not a developer.
The other alternative is Edebug, I think. You instrument the function
where the variables in which you are interested live, then evaluate
their values while stepping through that function (if Edebug didn't
evaluate them automatically for you).
next prev parent reply other threads:[~2021-08-21 8:10 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-21 5:07 Emacs development Jean-Christophe Helary
2021-08-21 6:46 ` Eli Zaretskii
2021-08-21 7:08 ` Jean-Christophe Helary
2021-08-21 7:16 ` Tassilo Horn
2021-08-21 7:50 ` Jean-Christophe Helary
2021-08-21 7:54 ` Tassilo Horn
2021-08-21 8:12 ` Eli Zaretskii
2021-08-21 13:51 ` Arthur Miller
2021-08-21 22:00 ` [External] : " Drew Adams
2021-08-21 8:08 ` Stephen Berman
2021-08-21 12:05 ` Konstantin Kharlamov
2021-08-21 12:28 ` Jean-Christophe Helary
2021-08-21 14:08 ` Tim Cross
2021-08-21 15:00 ` Jean-Christophe Helary
2021-08-21 23:09 ` Tim Cross
2021-08-22 1:26 ` Jean-Christophe Helary
2021-08-22 2:25 ` Tim Cross
2021-08-22 2:15 ` Arthur Miller
2021-08-22 2:48 ` Tim Cross
2021-08-22 7:47 ` Arthur Miller
2021-08-22 8:11 ` Tim Cross
2021-08-22 13:54 ` T.V Raman
2021-08-22 16:04 ` Eric Abrahamsen
2021-08-22 16:19 ` Jean-Christophe Helary
2021-08-22 16:23 ` Eric Abrahamsen
2021-08-22 16:25 ` Arthur Miller
2021-08-22 16:43 ` Jean-Christophe Helary
2021-08-22 16:29 ` Arthur Miller
2021-08-22 17:08 ` T.V Raman
2021-08-22 17:44 ` Arthur Miller
2021-08-22 18:34 ` Stephen Berman
2021-08-22 23:12 ` Arthur Miller
2021-08-23 9:17 ` Arthur Miller
2021-08-22 14:41 ` Arthur Miller
2021-08-21 14:07 ` Arthur Miller
2021-08-21 8:10 ` Eli Zaretskii [this message]
2021-08-21 8:36 ` Alfred M. Szmidt
-- strict thread matches above, loose matches on Subject: below --
2015-02-21 2:36 Sam Auciello
2015-02-21 3:52 ` Alexis
2015-02-21 8:56 ` Eli Zaretskii
2015-02-21 10:07 ` Adam Sjøgren
2015-02-21 11:28 ` Eric Abrahamsen
2015-02-21 11:44 ` Eli Zaretskii
2015-02-21 12:24 ` Thien-Thi Nguyen
2015-02-21 12:27 ` Eli Zaretskii
2015-02-21 14:22 ` Thien-Thi Nguyen
2015-02-21 18:43 ` Eli Zaretskii
2015-02-22 17:17 ` Thien-Thi Nguyen
2015-02-21 12:45 ` Eric Abrahamsen
2015-02-24 10:58 ` Filipp Gunbin
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=83k0kfz09p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lists@traduction-libre.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).