unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Sebastian Miele <iota@whxvd.name>
To: Heime <heimeborgia@protonmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Printing code made by a macro
Date: Sun, 06 Aug 2023 08:22:06 +0200	[thread overview]
Message-ID: <87tttcvg51.fsf@whxvd.name> (raw)
In-Reply-To: <wSmn3q-fbkGyNWfOw3e7k5-PD0edgsH1BHirJllkxYeSJVfS6PSt52AhNpIpb9U8DJ0Q9MNRFPK8McdRWHiC3_VmBX2Ric-UTwfYPIZu1As=@protonmail.com>

> From: Heime <heimeborgia@protonmail.com>
> Date: Sat, 2023-08-05 23:42 +0000
>
> Is there a proper way to display the code produced by a macro?

https://github.com/emacsorphanage/macrostep can do that in an
interactive way.  From its README:

  macrostep is an Emacs minor mode for interactively stepping through
  the expansion of macros in Emacs Lisp source code.  It lets you see
  exactly what happens at each step of the expansion process by
  pretty-printing the expanded forms inline in the source buffer, which
  is temporarily read-only while macro expansions are visible.



  parent reply	other threads:[~2023-08-06  6:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-05 23:42 Printing code made by a macro Heime
2023-08-06  0:31 ` Eduardo Ochs
2023-08-06  0:44   ` Heime
2023-08-06  0:50     ` Eduardo Ochs
2023-08-06  1:15       ` Heime
2023-08-06  2:16         ` Heime
2023-08-06  2:54           ` Eduardo Ochs
2023-08-06  3:36             ` Heime
2023-08-06 17:23             ` Heime
2023-08-06 20:36               ` Eduardo Ochs
2023-08-06 22:45                 ` Heime
2023-08-06 23:11                   ` Emanuel Berg
2023-08-06 18:10       ` Heime
2023-08-06  5:04 ` Eli Zaretskii
2023-08-06  6:22 ` Sebastian Miele [this message]
2023-08-07 19:54 ` Pierre Rouleau

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=87tttcvg51.fsf@whxvd.name \
    --to=iota@whxvd.name \
    --cc=heimeborgia@protonmail.com \
    --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).