From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: How do I get edebug online?
Date: Tue, 18 Jan 2022 00:34:28 +0100 [thread overview]
Message-ID: <87v8yi9bsr.fsf@web.de> (raw)
In-Reply-To: 87fspmkmkm.fsf@ericabrahamsen.net
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> You don't insert an actual call to (edebug) in your code (I didn't
> actually know that was possible, and looking at the docstring it says it
> works more or less like `debug', which is why you got the backtrack you
> mention below).
Not quite, see (info "(elisp) Source Breakpoints"). That requires the
containing function to be instrumented (which was not the case for the
OP). In uninstrumented code it indeed just calls `debug'.
Michael.
next prev parent reply other threads:[~2022-01-17 23:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 22:28 How do I get edebug online? Davin Pearson
2022-01-17 22:46 ` Eric Abrahamsen
2022-01-17 23:34 ` Michael Heerdegen [this message]
2022-01-17 23:44 ` Eric Abrahamsen
2022-01-18 0:06 ` Michael Heerdegen
2022-01-18 0:10 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-18 3:43 ` Eric Abrahamsen
2022-01-17 23:55 ` Michael Heerdegen
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=87v8yi9bsr.fsf@web.de \
--to=michael_heerdegen@web.de \
--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).