From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: kevin.d.rodgers@gmail.com, 14206@debbugs.gnu.org
Subject: bug#14206: 24.3.50; doc string of `execute-kbd-macro'
Date: Fri, 29 Apr 2016 15:00:07 +0200 [thread overview]
Message-ID: <87mvoca7u0.fsf@gnus.org> (raw)
In-Reply-To: <83shy4x5ro.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 29 Apr 2016 09:56:11 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> No, I think (fset 'foo "\M-:").
>
> IOW, an indirect function could produce a macro, right?
>
> In general, keyboard macros produce strings like that, which I'm sure
> you know, so I'm not sure if I understand your question.
I did not know that putting non-function stuff into the function slot of
a symbol was a thing that we do. Actually, I don't think it is. :-)
So I agree that this documentation is still kinda incomprehensible, even
though what it says is literally true:
MACRO can also be a vector of keyboard events. If MACRO is a symbol,
its function definition is used.
Perhaps something like
If MACRO is a symbol, and its function definition is a string or a
vector of keyboard events, its function definition is used.
? Or put it at the end, saying that it's deprecated...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-04-29 13:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 0:33 bug#14206: 24.3.50; doc string of `execute-kbd-macro' Drew Adams
2014-02-08 11:59 ` Lars Ingebrigtsen
2014-02-08 12:11 ` Andreas Schwab
2014-02-08 15:45 ` Kevin Rodgers
2014-02-09 1:50 ` Lars Ingebrigtsen
2016-04-28 23:29 ` Lars Ingebrigtsen
2016-04-29 6:56 ` Eli Zaretskii
2016-04-29 13:00 ` Lars Ingebrigtsen [this message]
2016-04-29 15:55 ` Andreas Schwab
2016-04-29 16:10 ` Lars Ingebrigtsen
2016-04-29 19:23 ` Andreas Schwab
2016-04-29 9:24 ` Andreas Schwab
2016-04-29 13:02 ` Lars Ingebrigtsen
2016-04-30 15:56 ` Johan Bockgård
2022-03-14 11:17 ` Lars Ingebrigtsen
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=87mvoca7u0.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=14206@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=kevin.d.rodgers@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).