unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "3466@debbugs.gnu.org" <3466@debbugs.gnu.org>,
	Drew Adams <drew.adams@oracle.com>
Subject: bug#3466: 23.0.94; have `d' in debugger treat macro expansion like `c' does
Date: Thu, 20 Oct 2022 04:04:44 +0200	[thread overview]
Message-ID: <87h6zz2qtf.fsf_-_@web.de> (raw)
In-Reply-To: <87h7ie0ys4.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 04 Jun 2021 11:22:51 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> So here's my test case:
>
> (defun foo ()
>   (dotimes (i 2)
>     (message "foo")))
>
> and `M-x debug-on-entry' on foo, `M-: (foo)', just hitting `d' a lot
> does what I'd expect -- stepping through all the code.  It does not seem
> to step the through the macro expansion itself.  (At least not in Emacs
> 27.1 or 28.)

I also don't understand what Drew writes.  Especially why c would do
something that a repeated d would not get you to, sooner or later.

Drew, did you bind c to something else?  Or had your code been loaded
under some special conditions?  Normally what the debugger steps through
doesn't contain macro calls - even for uncompiled code and even for the
dynamically binding dialect.  So unless you were debugging quoted
lambdas, I'm ... confused.

Michael.





  reply	other threads:[~2022-10-20  2:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-03 21:44 bug#3466: 23.0.94; have `d' in debugger treat macro expansion like `c' does Drew Adams
2021-06-03 10:04 ` Lars Ingebrigtsen
2021-06-03 15:01   ` bug#3466: [External] : " Drew Adams
2021-06-04  9:22     ` Lars Ingebrigtsen
2022-10-20  2:04       ` Michael Heerdegen [this message]
2022-10-20 16:04         ` Drew Adams
2022-10-20 20:38           ` 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=87h6zz2qtf.fsf_-_@web.de \
    --to=michael_heerdegen@web.de \
    --cc=3466@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --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).