From: Juri Linkov <juri@jurta.org>
To: yzhh <yezonghui@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Is there a plan to record kbd macro as elisp code?
Date: Sun, 28 Oct 2007 12:54:46 +0200 [thread overview]
Message-ID: <87r6jfecmx.fsf@jurta.org> (raw)
In-Reply-To: <loom.20071028T062307-553@post.gmane.org> (yzhh's message of "Sun\, 28 Oct 2007 06\:49\:13 +0000 \(UTC\)")
> Basically, I did these:
> Add a variable (V)kbd-macro-command-history, insert commands into it on ervey
> ocurrence of possible insertion into command-history (that's guarded by
> record_flag), when defining-kbd-macro is on. So it's not complete. You have to
> M-x eval-expression kbd-macro-command-history to see the recorded thing, in
> reverse order. And its length is guarded by history-length.
Thanks for your code! I see you collect executed commands together
with their arguments into a new list of commands. This is fine.
But I think it's better to add a new variable `this-command-args'
that contains the arguments of the current command because this variable
could be useful for other purposes as well, and it allows collecting
commands with their arguments in Lisp that improves the flexibility of
this approach.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2007-10-28 10:54 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-27 9:28 Is there a plan to record kbd macro as elisp code? yzhh
2007-10-27 15:48 ` Robert J. Chassell
2007-10-27 17:30 ` yzhh
2007-10-27 18:01 ` Drew Adams
2007-10-28 13:50 ` Richard Stallman
2007-10-27 20:04 ` Stefan Monnier
2007-10-27 21:22 ` Kim F. Storm
2007-10-28 13:50 ` Richard Stallman
2007-10-28 22:00 ` Kim F. Storm
2007-10-29 5:20 ` yzhh
2007-10-29 9:22 ` Richard Stallman
2007-10-29 9:22 ` Richard Stallman
2007-10-27 21:45 ` Juri Linkov
2007-10-28 1:14 ` Stefan Monnier
2007-10-28 1:34 ` Juri Linkov
2007-10-29 0:11 ` Richard Stallman
2007-10-28 6:49 ` yzhh
2007-10-28 7:13 ` yzhh
2007-10-28 10:54 ` Juri Linkov [this message]
2007-10-28 13:50 ` Richard Stallman
2007-10-28 15:09 ` Juri Linkov
2007-10-29 9:21 ` Richard Stallman
2007-10-28 16:13 ` yzhh
2007-10-28 16:48 ` Juri Linkov
2007-10-29 9:21 ` Richard Stallman
2007-10-30 14:14 ` Juri Linkov
2007-10-31 7:46 ` Richard Stallman
2007-10-27 19:26 ` Jay Belanger
2007-10-27 16:20 ` Drew Adams
2007-10-27 17:13 ` yzhh
2007-10-27 17:40 ` Drew Adams
2007-10-27 18:05 ` yzhh
2007-10-27 19:22 ` Robert J. Chassell
2007-10-27 20:11 ` Drew Adams
2007-10-28 13:50 ` Richard Stallman
2007-10-28 16:45 ` Juri Linkov
2007-10-29 6:41 ` Klaus Zeitler
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=87r6jfecmx.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=yezonghui@gmail.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).