all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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:16:42 +0200	[thread overview]
Message-ID: <87r237epz9.fsf@gnus.org> (raw)
In-Reply-To: <87ob5tckwv.fsf@nbtrap.com> (Nathan Trapuzzano's message of "Sat,  09 Nov 2013 16:41:52 -0500")

Nathan Trapuzzano <nbtrap@nbtrap.com> writes:

> Edebug would benefit from something like debug.el's
> `cancel-debug-on-entry'.  Especially after stepping through large
> functions and into other functions therefrom, it's annoying to have to
> manually re-eval them to remove the extra forms added by Edebug.

I think this sounds like a useful command -- I often find myself having
edebug-instrumented a whole bunch of functions, and having to manually
re-eval all of them is tedious.

So a command like `edebug-cancel-all-functions' would be nice, and I
looked into the bowels of edebug.el to see whether that would be
easy...  and...  I think so?

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?

Or is there a better way?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2019-10-20  9:16 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 [this message]
2019-10-20  9:30   ` Lars Ingebrigtsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r237epz9.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.