From: "Juri Linkov" <juri@jurta.org>
To: yezonghui@gmail.com
Cc: emacs-devel@gnu.org
Subject: Re: recording-elisp.el - try recording commands as elisp code
Date: Fri, 2 Nov 2007 01:01:39 +0200 (EET) [thread overview]
Message-ID: <49248.83.178.59.207.1193958099.squirrel@webmail.jurta.org> (raw)
In-Reply-To: <fgdgd7$65u$1@ger.gmane.org>
> This recording.el is maybe some useful results from our discussion on
> recording kbd macro as elisp results. I'm now posting it not because it is
> perfectly usable, but to trigger some ideas on improvements.
Thanks.
> I started from a patch Juri gave to me. In his code there are modifications
> in the C code and in kmacro.el and isearch.el. I recognize that the C code
> patch is a must to get command args, and left them as is.
I think I should install my C patch that adds a new variable this-command-args.
This will allow you to continue freely implementing this feature.
> But I think it is better to implement the recording outside other elisp
> source. So I pulled his code out of those el files and wrote
> recording-elisp.el. I also made further modifications to handle isearch
> commands better.
I suggest you to give a shorter name to this package (e.g. record-lisp.el)
and to use the same prefix for all function and variable names.
> If anybody is interested to give it a try. it is quite simple: M-x
> start-recording-commands, do something, M-x end-recording-commands, and
> then M-x insert-recorded-commands into current buffer.
It's fine that you implement separate commands to record Lisp commands
with their arguments since actually this feature is not dependent
on keyboard macros. But I think `C-x (' and `C-x )' still should record
Lisp commands too, because these keybindings are convenient to start and
end recording of command sequences, even though they record different
things: one feature records a keyboard macro, and another - Lisp code.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2007-11-01 23:01 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 21:27 recording-elisp.el - try recording commands as elisp code yzhh
2007-11-01 23:01 ` Juri Linkov [this message]
2007-11-02 5:39 ` yzhh
2007-11-02 20:46 ` Juri Linkov
2007-11-03 3:35 ` yzhh
2007-11-03 10:21 ` Reiner Steib
2007-11-04 5:02 ` yzhh
2007-11-02 2:06 ` Richard Stallman
2007-11-02 5:44 ` yzhh
2007-11-03 3:58 ` Richard Stallman
2007-11-03 7:14 ` yzhh
2007-11-02 6:14 ` yzhh
2007-11-02 20:45 ` Juri Linkov
2007-11-03 3:57 ` yzhh
2007-11-03 20:48 ` Richard Stallman
2007-11-04 8:51 ` yzhh
2007-11-04 16:48 ` Drew Adams
2007-11-05 5:40 ` yzhh
2007-11-06 2:16 ` Richard Stallman
2007-11-06 6:29 ` yzhh
2007-11-07 0:15 ` Richard Stallman
2007-11-06 16:33 ` Mathias Dahl
2007-11-06 22:28 ` Juri Linkov
2007-11-07 7:55 ` Richard Stallman
2007-11-05 6:20 ` Richard Stallman
2007-11-05 14:27 ` yzhh
2007-11-05 14:43 ` Stefan Monnier
2007-11-05 15:03 ` yzhh
2007-11-06 2:16 ` Richard Stallman
2007-11-06 8:28 ` Stefan Monnier
2007-11-05 6:20 ` Richard Stallman
2007-11-06 0:45 ` Juri Linkov
2007-11-06 6:12 ` yzhh
2007-11-07 0:15 ` Richard Stallman
2007-11-06 8:37 ` Richard Stallman
2007-11-06 22:28 ` Juri Linkov
2007-11-07 7:56 ` Richard Stallman
2007-11-02 21:28 ` Stefan Monnier
2007-11-03 4:23 ` yzhh
2007-11-03 3:58 ` Richard Stallman
2007-11-03 7:12 ` yzhh
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49248.83.178.59.207.1193958099.squirrel@webmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.