From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Ag Ibragimov <agzam.ibragimov@gmail.com>, 70791@debbugs.gnu.org
Subject: bug#70791: 30.0.50; edebug-remove-instrumentation doesn't see instrumented functions
Date: Mon, 06 May 2024 19:22:55 -0400 [thread overview]
Message-ID: <jwvmsp2lebm.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <874jbarc6v.fsf@web.de> (Michael Heerdegen's message of "Mon, 06 May 2024 21:07:52 +0200")
>> Side note: as it is currently implemented,
>> `edebug-remove-instrumentation` cannot work reliably (and the way it
>> discovers the set of functions that can be un-instrumented is quite
>> wasteful, tho it seems it does the job), so I recommend you `C-M-x` to
>> redefine the function instead.
>
> One important use case is the ability to deinstrument all functions at
> once in a convenient way, so I think we at least want to keep some kind
> of deinstrumenting function.
But given that it's a "best effort" kind of work, I recommend to stay
away from it when possible (until a more reliable implementation is
provided, but that may be a long time, because it's not obvious to me
how to do it).
Stefan
next prev parent reply other threads:[~2024-05-06 23:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-05 19:12 bug#70791: 30.0.50; edebug-remove-instrumentation doesn't see instrumented functions Ag Ibragimov
2024-05-06 18:04 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06 18:38 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06 19:07 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-06 23:22 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-05-06 18:39 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=jwvmsp2lebm.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=70791@debbugs.gnu.org \
--cc=agzam.ibragimov@gmail.com \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
/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).