From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Convert an existing keyboard macro to elisp code?
Date: Sat, 04 Aug 2012 08:13:59 +0200 [thread overview]
Message-ID: <501CBDA7.2020003@easy-emacs.de> (raw)
In-Reply-To: <CAJsNXT=86=O+Q5CYi-+WYjvqkRYYtVE1dZOq2hNnrx3P02uW1Q@mail.gmail.com>
Am 03.08.2012 18:33, schrieb PJ Weisberg:
> On Fri, Aug 3, 2012 at 8:10 AM, Thorsten Jolitz <tjolitz@googlemail.com> wrote:
>> Unfortunately, the answer was more a less a 'NO'(or 'YOU HAVE TO WRITE
>> IT YOURSELF').
>>
>> Since Emacs is a pretty dynamic project, I thought I give it another try
>> on the mailing list - maybe this feature request has been implemented in
>> the meantime by somebody?
>
> If it were just a matter of reading the key sequence and mapping it to
> functions it wouldn't be too bad, but the more I think about this, the
> more it seems like a rat hole. How would you translate
>
> (fset 'my-macro
> [?\M-x ?m ?a ?g tab ?i ?t tab ?s ?t tab ?t tab return ?m ?a tab return])
>
> into
>
> (defun my-macro ()
> (interactive)
> (magit-status "c:/Users/PJ/Documents/magit/"))
>
> ?
>
> You would need to know what auto-completion happened when the user
> pressed tab, and then you would need to know how the function
> translated its user input into interactive arguments. I don't think
> there's a way to do it without running the macro and (somehow)
> watching what happens. And that could have unpleasant side effects.
>
> And this particular example wouldn't even be portable, since when I
> type "M-x magit-status RET magit RET", Magit actually does some magic
> to translate that into a full path. So on my other machine, the
> proper definition of that macro would be
>
> (defun my-macro ()
> (interactive)
> (magit-status "/home/pj/source-code/magit"))
>
>
> And that doesn't even take into account different keymaps.
>
> -PJ
>
Hi,
so you might get different code when calling from different circumstances. Which wouldn't hinder to notate a would-be-executed code from
a point of interest.
Basically IMHO such a thing is feasible.
Andreas
> Gehm's Corollary to Clark's Law: Any technology distinguishable from
> magic is insufficiently advanced.
>
>
next prev parent reply other threads:[~2012-08-04 6:13 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 [this message]
[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
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=501CBDA7.2020003@easy-emacs.de \
--to=andreas.roehler@easy-emacs.de \
--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).