From: Robert Pluim <rpluim@gmail.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Calling macro by name while defining another macro
Date: Thu, 22 Mar 2018 16:56:34 +0100 [thread overview]
Message-ID: <874ll8m7d9.fsf@gmail.com> (raw)
In-Reply-To: <jwvy3ikt8o3.fsf-monnier+Inbox@gnu.org> (Stefan Monnier's message of "Thu, 22 Mar 2018 11:47:25 -0400")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>> How so? The macro is faithfully recording all the keystrokes, which is
>> both literally 'M-x some-macro' and the keystrokes output by running
>> that macro.
>
> The keystrokes output by running the macro shouldn't be recorded.
D'oh. Of course. The *user* didn't type those.
next prev parent reply other threads:[~2018-03-22 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 22:35 Calling macro by name while defining another macro John Shahid
2018-03-22 13:53 ` Stefan Monnier
2018-03-22 15:12 ` Robert Pluim
2018-03-22 15:47 ` Stefan Monnier
2018-03-22 15:56 ` Eli Zaretskii
2018-03-22 15:56 ` Robert Pluim [this message]
2018-03-22 15:00 ` Eli Zaretskii
2018-03-22 15:52 ` John Shahid
2018-03-22 15:59 ` Stefan Monnier
2018-03-22 17:47 ` John Shahid
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=874ll8m7d9.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).