From: "Drew Adams" <drew.adams@oracle.com>
To: "yzhh" <yezonghui@gmail.com>, <emacs-devel@gnu.org>
Subject: RE: Is there a plan to record kbd macro as elisp code?
Date: Sat, 27 Oct 2007 10:40:55 -0700 [thread overview]
Message-ID: <BNELLINCGFJLDJIKDGACEECGCEAA.drew.adams@oracle.com> (raw)
In-Reply-To: <loom.20071027T165412-973@post.gmane.org>
> I'm sorry I didn't mention the path I've gone through. Actually
> I've found a version of generate.el, which is made in 1989. It includes
> those functions with similar names you cited (without 'gen-' prefix).
> And I runs without an error in emacs22. But it leaves out too much
> commands in the generated code. I looked into generated.el's
> implementation, and found it actually reads command-history to get the
> code. And command-history itself is leaving out a lot commands.
>
> That's why I made those modifications, trying to get a complete command
> history. And then the story you've read.
>
> Please also read my reply to Robert.
I didn't see your reply to Robert.
Yes, I think now that it was generate.el I was thinking of. There appear to
be different kinds of files with this same name, however (e.g. one that
generates MPEG files). I guess the one you found is this?
http://mirrors.wikifusion.info/gnu/elisp-archive/as-is/generate.el.Z
Doesn't generate.el give you enough of a code skeleton to complete the
command? You mention missing horizontal movement commands and a fragmented
treatment of isearch, but it should be possible to patch up the code in
those areas, no? Of course, if you could improve it, that would be even
better. Good luck, and please post what you've got when you're done
somewhere (e.g. gnu-emacs-sources, Emacs Wiki).
next prev parent reply other threads:[~2007-10-27 17:40 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
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 [this message]
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=BNELLINCGFJLDJIKDGACEECGCEAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
--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).