From: Gemini Lasswell <gazally@runbox.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 26847@debbugs.gnu.org
Subject: bug#26847: 26.0.50; Using edebug-step-in on a macro switches to go-mode
Date: Sun, 20 Oct 2019 22:18:54 -0700 [thread overview]
Message-ID: <8736fmd6bl.fsf@runbox.com> (raw)
In-Reply-To: <87sgnnccy8.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 20 Oct 2019 23:41:03 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> I'm unable to reproduce this in Emacs 27. When I hit `i', I'm then
> edebugging the `push' macro, and then I can step through it, and then
> I'm back to stepping through my-try-thing.
>
> Are you still seeing this bug in Emacs 27?
In Emacs 26, eager macro expansion happened when instrumenting code for
Edebug using eval-defun. In current master, it's not getting done.
Looking at (symbol-function 'my-try-thing) in both versions will show
you the difference.
The lack of macroexpansion doesn't only happen when instrumenting for
Edebug. If you evaluate a function definition with eval-buffer or
eval-last-sexp then macroexpansion is done, but if you evaluate it with
eval-defun with or without the universal argument, then no
macroexpansion happens. This is a change from Emacs 26, and is masking
the original bug.
If you use these steps to reproduce, with the same sample code:
M-x edebug-all-defs RET
M-x eval-buffer RET
M-: (my-try-thing 'a) RET
i
then the original bug still occurs.
next prev parent reply other threads:[~2019-10-21 5:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 21:06 bug#26847: 26.0.50; Using edebug-step-in on a macro switches to go-mode Gemini Lasswell
2017-05-09 22:23 ` Dmitry Gutov
2019-10-20 21:41 ` Lars Ingebrigtsen
2019-10-21 5:18 ` Gemini Lasswell [this message]
2019-10-21 19:35 ` 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
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=8736fmd6bl.fsf@runbox.com \
--to=gazally@runbox.com \
--cc=26847@debbugs.gnu.org \
--cc=larsi@gnus.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.
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).