unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Gemini Lasswell <gazally@runbox.com>, 26847@debbugs.gnu.org
Subject: bug#26847: 26.0.50; Using edebug-step-in on a macro switches to go-mode
Date: Wed, 10 May 2017 01:23:39 +0300	[thread overview]
Message-ID: <3aa02b7a-3031-73f3-a344-3a10f95d0171@yandex.ru> (raw)
In-Reply-To: <87vapb12k2.fsf@chinook>

On 09.05.2017 0:06, Gemini Lasswell wrote:

> Stepping into macros would have made sense before eager
> macro-expansion, but now by the time Edebug instruments the code the
> macro has already run. Probably the simplest thing to do here is to
> have edebug-step-in signal an error if asked to step into a macro. The
> documentation for edebug-step-in also should be updated to remove
> mention of stepping into macros.

Since nobody has complained about this problem by now, it's probably the 
easiest solution indeed.

However, I wonder if we could inhibit eager macro-expansion when a 
function is being instrumented by edebug. Its definition is being 
re-evaluated at that time, right?

I don't know if we have a good way to do that, though. Or if adding one 
ends up being easy to maintain.





  reply	other threads:[~2017-05-09 22:23 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 [this message]
2019-10-20 21:41 ` Lars Ingebrigtsen
2019-10-21  5:18   ` Gemini Lasswell
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=3aa02b7a-3031-73f3-a344-3a10f95d0171@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=26847@debbugs.gnu.org \
    --cc=gazally@runbox.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).