unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: yzhh <yezonghui@gmail.com>
To: emacs-devel@gnu.org
Subject: Is there a plan to record kbd macro as elisp code?
Date: Sat, 27 Oct 2007 09:28:17 +0000 (UTC)	[thread overview]
Message-ID: <loom.20071027T084301-605@post.gmane.org> (raw)

Hi,

Recording kbd macro as elisp code can be useful. The following are some 
benefits:
1. Editing elisp code is more clear than editing key sequences, and supports 
complex controlstructures. 
2. elisp code is more portable than key sequences. Sharing with others who 
have different key bindings is ok for elisp, but not for key sequences.
3. It can be used as a means ot learn emacs commands in elisp form.

I tried to build a modified emacs that stores every command sent to 
'execute-command' into a list, when 'defining-kbd-macro' is on. But the 
result is a list that still leaves out things like horizontal movements. 
And isearch is not recorded right (one search recorded as many isearch 
commands, without information of what's being searched).

So I know the modification required is not simple, far beyond a quick and 
dirty patch.

Out of curiosity I want to know whether there is a plan for this feature in 
the future.

             reply	other threads:[~2007-10-27  9:28 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-27  9:28 yzhh [this message]
2007-10-27 15:48 ` Is there a plan to record kbd macro as elisp code? 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
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=loom.20071027T084301-605@post.gmane.org \
    --to=yezonghui@gmail.com \
    --cc=emacs-devel@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.
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).