unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: "3466@debbugs.gnu.org" <3466@debbugs.gnu.org>
Subject: bug#3466: [External] : Re: bug#3466: 23.0.94; have `d' in debugger treat macro expansion like `c' does
Date: Fri, 04 Jun 2021 11:22:51 +0200	[thread overview]
Message-ID: <87h7ie0ys4.fsf@gnus.org> (raw)
In-Reply-To: <SA2PR10MB44741D30AEE83B6ECF9FE357F33C9@SA2PR10MB4474.namprd10.prod.outlook.com> (Drew Adams's message of "Thu, 3 Jun 2021 15:01:04 +0000")

Drew Adams <drew.adams@oracle.com> writes:

> You hit `d' once, to get into the macro, then `c' to get
> the macro expansion (then d d d... to go on after the
> expansion).
>
> The point was only that at some point you need to hit `c'
> if you don't want to do the macro expansion itself step
> by step.

Hm.  I'm not all that familiar with this debugging interface -- I
usually use edebug, so I'm not quite sure what people expect from this
thing.

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.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-06-04  9:22 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 [this message]
2022-10-20  2:04       ` Michael Heerdegen
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=87h7ie0ys4.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=3466@debbugs.gnu.org \
    --cc=drew.adams@oracle.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).