From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Convert an existing keyboard macro to elisp code?
Date: Sat, 4 Aug 2012 18:51:36 +0200 [thread overview]
Message-ID: <20120804165136.GB14023@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <87mx2cxb7x.fsf@googlemail.com>
On Fri, Aug 03, 2012 at 05:10:42PM +0200, Thorsten Jolitz wrote:
>
> Unfortunately, the answer was more a less a 'NO'(or 'YOU HAVE TO WRITE
> IT YOURSELF').
>
You can always name the macro and save the lisp as a command in your
init file.
M-x kmacro-name-last-macro RET <somename>
M-x insert-kbd-macro RET <abovename>
HTH
--
Suvayu
Open source is the future. It sets us free.
prev parent reply other threads:[~2012-08-04 16:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 15:10 Convert an existing keyboard macro to elisp code? Thorsten Jolitz
2012-08-03 16:33 ` PJ Weisberg
2012-08-03 17:00 ` Yuri Khan
2012-08-03 18:16 ` Thorsten Jolitz
2012-08-04 6:13 ` Andreas Röhler
[not found] ` <mailman.6259.1344011630.855.help-gnu-emacs@gnu.org>
2012-08-04 9:48 ` Raffaele Ricciardi
2012-08-04 16:39 ` Thorsten Jolitz
2012-08-04 16:51 ` Suvayu Ali [this message]
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=20120804165136.GB14023@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@gmail.com \
--cc=help-gnu-emacs@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.
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).