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: Lars Ingebrigtsen <larsi@gnus.org>,
48585@debbugs.gnu.org, Philipp <p.stephani2@gmail.com>
Subject: bug#48585: 28.0.50; Missing Edebug instrumentation for some 'if-let' variants
Date: Sat, 16 Jul 2022 22:04:51 -0400 [thread overview]
Message-ID: <jwvo7xopkar.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87mtd8ed0e.fsf@web.de> (Michael Heerdegen's message of "Sun, 17 Jul 2022 03:36:33 +0200")
Michael Heerdegen [2022-07-17 03:36:33] wrote:
> Michael Heerdegen <michael_heerdegen@web.de> writes:
>> Then I guess we could use this `&interpose' Edebug spec but it's
>> undocumented and not really trivial to understand.
> But seems the return value is an Edebug spec again. This would not help
> in this case then.
No, the problem can't be fixed in the edebug-spec. Either we live with
the current behavior (perfectly acceptable if you ask me), or you need
to change the definition of the macro so it explicitly strips the Edebug
instrumentation (if present) at those places where it's not desired.
Stefan
next prev parent reply other threads:[~2022-07-17 2:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 11:37 bug#48585: 28.0.50; Missing Edebug instrumentation for some 'if-let' variants Philipp
2022-07-15 10:16 ` Lars Ingebrigtsen
2022-07-16 22:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-17 0:13 ` Michael Heerdegen
2022-07-17 1:36 ` Michael Heerdegen
2022-07-17 2:04 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-07-17 15:45 ` Michael Heerdegen
2022-07-15 23:15 ` 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=jwvo7xopkar.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=48585@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@iro.umontreal.ca \
--cc=p.stephani2@gmail.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).