unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Joel Reicher <joel.reicher@gmail.com>
To: Lewis Creary via Users list for the GNU Emacs text editor
	<help-gnu-emacs@gnu.org>
Cc: Lewis Creary <lewcreary@cs.com>
Subject: Re: Learning Edebug
Date: Sat, 21 Dec 2024 17:17:07 +1100	[thread overview]
Message-ID: <86frmhk1b0.fsf@gmail.com> (raw)
In-Reply-To: <130443705.1910512.1734664285448@mail.yahoo.com> (Lewis Creary via Users list for the's message of "Fri, 20 Dec 2024 03:11:25 +0000 (UTC)")

Lewis Creary via Users list for the GNU Emacs text editor 
<help-gnu-emacs@gnu.org> writes:

> I'm trying to learn how to use the Emacs lisp function Edebug, 
> but so far am not having any success.  The documentation says 
> that I need to "instrument" the function that I want to debug, 
> and I'm even having trouble with that.
> I've been programming in Emacs Lisp for over a decade, and have 
> always found that print statements were sufficient for debugging 
> my programs.

I think the other replies have good practical info, but just in 
case some conceptual info is useful, instrumenting code is 
basically what you've been doing with print statements. When 
edebug instruments the code and inserts its own debugging 
snippets, you can execute the code normally and the 
instrumentation that edebug inserted will call the edebug 
functionality.

The built-in lisp debugger works the "other" way; it affects the 
evaluation machinery rather than the code being evaluated.

Regards,

        - Joel



      parent reply	other threads:[~2024-12-21  6:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <130443705.1910512.1734664285448.ref@mail.yahoo.com>
2024-12-20  3:11 ` Learning Edebug Lewis Creary via Users list for the GNU Emacs text editor
2024-12-20  6:23   ` mbork
2024-12-20  7:18   ` Eduardo Ochs
2024-12-20  8:11   ` Joost Kremers
2024-12-20 11:36   ` Michael Heerdegen via Users list for the GNU Emacs text editor
2024-12-20 15:37     ` [External] : " Drew Adams
2024-12-20 22:46   ` tpeplt
2024-12-21  2:41     ` Eduardo Ochs
2024-12-21  6:17   ` Joel Reicher [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=86frmhk1b0.fsf@gmail.com \
    --to=joel.reicher@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=lewcreary@cs.com \
    /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).