From: Lars Ingebrigtsen <larsi@gnus.org>
To: Nathan Trapuzzano <nbtrap@nbtrap.com>
Cc: 15843@debbugs.gnu.org
Subject: bug#15843: 24.3.50; Edebug feature request
Date: Sun, 20 Oct 2019 11:30:38 +0200 [thread overview]
Message-ID: <87zhhvhigx.fsf@gnus.org> (raw)
In-Reply-To: <87r237epz9.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 20 Oct 2019 11:16:42 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> I think we basically have to go through all the symbols and see whether
> any of those are edebugged, and if so, call `edebug-unwrap*' on them and
> set the function definition to that?
I wrote a function like that just to test, and to my surprise, it seems
to work in the test cases I had, so I installed it.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-10-20 9:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 21:41 bug#15843: 24.3.50; Edebug feature request Nathan Trapuzzano
2013-11-11 4:58 ` Stefan Monnier
2013-11-11 11:02 ` Nathan Trapuzzano
2013-11-11 13:37 ` Stefan Monnier
2013-11-11 13:41 ` Nathan Trapuzzano
2019-10-20 9:16 ` Lars Ingebrigtsen
2019-10-20 9:30 ` Lars Ingebrigtsen [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=87zhhvhigx.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=15843@debbugs.gnu.org \
--cc=nbtrap@nbtrap.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.
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).