From: "Drew Adams" <drew.adams@oracle.com>
To: "'Ted Zlatanov'" <tzz@lifelogs.com>, <help-gnu-emacs@gnu.org>
Subject: RE: random predicate function
Date: Wed, 15 Dec 2010 10:04:24 -0800 [thread overview]
Message-ID: <A230EFAF22534356985AACE3E45EDB90@us.oracle.com> (raw)
In-Reply-To: <87bp4nx9y8.fsf@lifelogs.com>
> We're talking about GNU Emacs specifically. Have you debugged macros
> there? They are definitely not as intuitive as functions in
> the debugger.
Debug macros using `macroexpand', not the debugger. (Just a suggestion.)
In the Emacs debugger (`debug', not `edebug'), assuming that a macro does not
itself need to be debugged, I typically hit `c' (instead of `d') to skip over
the details of its expansion.
In fact, I would prefer it if `d' did the same thing as `c' for a macro, and a
new key were available to do what `d' does now for macros.
A typical example is `dolist' in the debugger. I hit `c' as soon as I see `#['
instead of a function name. For `dolist' you need to do that twice: once for
`dolist' and once for its `block'.
next prev parent reply other threads:[~2010-12-15 18:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1292251427.11097.help-gnu-emacs@gnu.org>
2010-12-13 15:26 ` random predicate function Pascal J. Bourguignon
2010-12-13 17:16 ` Ted Zlatanov
2010-12-13 17:48 ` Pascal J. Bourguignon
2010-12-15 14:51 ` Ted Zlatanov
2010-12-15 15:20 ` Pascal J. Bourguignon
2010-12-15 16:44 ` Ted Zlatanov
2010-12-15 17:28 ` Pascal J. Bourguignon
2010-12-15 18:39 ` Ted Zlatanov
2010-12-15 18:04 ` Drew Adams [this message]
2010-12-13 18:17 ` Tyler Smith
[not found] ` <mailman.2.1292264248.1009.help-gnu-emacs@gnu.org>
2010-12-13 18:38 ` Pascal J. Bourguignon
2010-12-13 19:05 ` Tyler Smith
2010-12-13 14:43 Tyler Smith
2010-12-13 15:37 ` Gary
2010-12-13 16:08 ` Tyler Smith
2010-12-13 16:16 ` Erik Iverson
2010-12-13 16:50 ` Tyler Smith
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A230EFAF22534356985AACE3E45EDB90@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tzz@lifelogs.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.