From: Juri Linkov <juri@linkov.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Philip Kaludercic <philipk@posteo.net>,
emacs-devel@gnu.org, Andrea Corallo <akrl@sdf.org>
Subject: Re: Native compilation of Keyboard Macros
Date: Sat, 17 Sep 2022 20:52:38 +0300 [thread overview]
Message-ID: <86wna1c2hl.fsf@mail.linkov.net> (raw)
In-Reply-To: <jwvleqjrv8p.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 16 Sep 2022 15:27:18 -0400")
> So, I think you should focus on the problem of turning a keyboard macro
> into code. We know it's impossible in general, so it has to be
> "user-visible" (i.e. the user specifically asks for it and is made aware
> that the result is a chunk of code which will not always run the same
> commands as the keyboard macro).
>
> You could have a "run kmacro and turn *this* execution into ELisp code".
> IIUC some people tried to do that already, but I can't remember where
> I saw that and my search-fu is weak right now.
The last executed commands are already remembered at different levels,
so the hard task is to decide at what level to turn them to code:
1. at level of complex command execution, such as from the history
retrieved by `repeat-complex-command` (C-x ESC ESC), for example:
(rgrep "macro" "* .*" "emacs/lisp/")
2. at level of commands corresponding to all typed keys,
such as retrieved by `view-lossage` (C-h l),
for example, for the same as above:
M-x ;; execute-extended-command
r ;; self-insert-command
g ;; self-insert-command
r ;; self-insert-command
<tab> ;; minibuffer-complete
<return> ;; minibuffer-complete-and-exit
m ;; self-insert-command
a ;; self-insert-command
c ;; self-insert-command
r ;; self-insert-command
o ;; self-insert-command
<return> ;; exit-minibuffer
<return> ;; exit-minibuffer
<return> ;; minibuffer-complete-and-exit
next prev parent reply other threads:[~2022-09-17 17:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 18:56 Native compilation of Keyboard Macros Philip Kaludercic
2022-09-16 19:27 ` Stefan Monnier
2022-09-17 17:52 ` Juri Linkov [this message]
2022-09-17 18:26 ` Philip Kaludercic
2022-09-17 18:40 ` Juri Linkov
2022-09-17 20:00 ` Philip Kaludercic
2022-09-18 3:12 ` Stefan Monnier
2022-09-18 5:02 ` Visuwesh
2022-09-18 13:46 ` Stefan Monnier
2022-09-16 19:54 ` Óscar Fuentes
2022-09-17 14:49 ` Philip Kaludercic
2022-09-17 15:33 ` Óscar Fuentes
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=86wna1c2hl.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=akrl@sdf.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
/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).