From: Eli Zaretskii <eliz@gnu.org>
To: npostavs@users.sourceforge.net
Cc: 25860@debbugs.gnu.org, eggert@cs.ucla.edu,
tino.calancha@gmail.com, jwiegley@gmail.com,
wasserwerk.studio@googlemail.com, schwab@linux-m68k.org
Subject: bug#25860: 25.1; Double macro execution
Date: Mon, 27 Feb 2017 17:57:59 +0200 [thread overview]
Message-ID: <83o9xnpqwo.fsf@gnu.org> (raw)
In-Reply-To: <87varxdjon.fsf@users.sourceforge.net> (npostavs@users.sourceforge.net)
> From: npostavs@users.sourceforge.net
> Cc: 25860@debbugs.gnu.org, eggert@cs.ucla.edu, tino.calancha@gmail.com, jwiegley@gmail.com, wasserwerk.studio@googlemail.com, schwab@linux-m68k.org
> Date: Sun, 26 Feb 2017 11:02:32 -0500
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I admit that I don't see myself as an expert on all the complexity
> > that goes on in keyboard.c and friends. With this change,
> > kmacro-tests.el still passes, but I'm not sure that's good enough
> > (e.g., can a macro define another macro when it runs? if so, this
> > change will get in the way).
>
> AFAICT, you can't define a macro from a macro:
>
> DEFUN ("start-kbd-macro", Fstart_kbd_macro, Sstart_kbd_macro, 1, 2, "P",
> ...
> {
> if (!NILP (KVAR (current_kboard, defining_kbd_macro)))
> error ("Already defining kbd macro");
Yes, but that's not the scenario I had in mind. What I had in mind is
a macro that, when run, will call start-kbd-macro etc. It's clear
that such a macro cannot be easily defined using F3 and F4, but
perhaps some ingenious method with using some Lisp data in the
macro...
Anyway, if no objections come up in a few days, I will push this.
Thanks for the feedback.
next prev parent reply other threads:[~2017-02-27 15:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 9:23 bug#25860: 25.1; Double macro execution Marek Twardochlib
2017-02-24 14:10 ` Andreas Schwab
2017-02-25 5:41 ` Tino Calancha
2017-02-25 10:10 ` Tino Calancha
2017-02-25 13:27 ` npostavs
2017-02-25 14:48 ` Tino Calancha
2017-02-25 15:26 ` Marek Twardochlib
2017-02-26 5:04 ` Tino Calancha
2017-02-26 7:12 ` npostavs
2017-02-26 15:33 ` Eli Zaretskii
2017-02-26 16:02 ` npostavs
2017-02-27 15:57 ` Eli Zaretskii [this message]
2017-02-27 17:18 ` Noam Postavsky
2017-03-03 14:21 ` Eli Zaretskii
2017-09-29 10:29 ` Marek Twardochlib
2017-09-29 11:41 ` Tino Calancha
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=83o9xnpqwo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25860@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=jwiegley@gmail.com \
--cc=npostavs@users.sourceforge.net \
--cc=schwab@linux-m68k.org \
--cc=tino.calancha@gmail.com \
--cc=wasserwerk.studio@googlemail.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).