From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: A more specific/targeted version of macroexpand-all?
Date: Thu, 09 Jun 2022 12:47:17 +0200 [thread overview]
Message-ID: <875yla866i.fsf@web.de> (raw)
In-Reply-To: 2515e8cf-c3cd-2322-2acd-f7e8144b95c2@protonmail.com
Okamsn <okamsn@protonmail.com> writes:
> I have been able to explicitly prevent expansion of macros by including
> them in the second argument of `macroexpand-all`, such as in
>
> (macroexpand-all my-code `((cl-block) (cl-return-from) ,@my-macros))
I didn't know that nil-valued bindings work there.
> but that still leaves the possibility of other, unknown macros expanding
> incorrectly.
Why would they expand incorrectly? Not sure I understand what you want.
Michael.
prev parent reply other threads:[~2022-06-09 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 1:31 A more specific/targeted version of macroexpand-all? Okamsn
2022-06-09 1:36 ` Emanuel Berg
2022-06-09 1:40 ` cl-loop and collect (was: Re: A more specific/targeted version of macroexpand-all?) Emanuel Berg
2022-06-09 1:48 ` Emanuel Berg
2022-06-09 10:47 ` Michael Heerdegen [this message]
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=875yla866i.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@gnu.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.
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).