From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 14206@debbugs.gnu.org
Subject: bug#14206: 24.3.50; doc string of `execute-kbd-macro'
Date: Sat, 08 Feb 2014 03:59:31 -0800 [thread overview]
Message-ID: <87vbwpstlo.fsf@building.gnus.org> (raw)
In-Reply-To: <BB89EAF6234044E7B955737CDC55BAA3@us.oracle.com> (Drew Adams's message of "Sun, 14 Apr 2013 17:33:45 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
> The doc string is misleading, especially this part: "as string of editor
> command characters". Presumably what is meant is as a sequence of
> command chars (better - a sequence of events). Compare the Elisp manual
> description, which explicitly mentions that MACRO can be a string or a
> vector (or a symbol with a function value).
Uhm...
(defun foo () "foo")
(execute-kbd-macro 'foo)
->
Debugger entered--Lisp error: (error "Keyboard macros must be strings or vectors")
execute-kbd-macro(foo)
eval((execute-kbd-macro (quote foo)) nil)
(execute-kbd-macro "foo")
-> foo
(execute-kbd-macro ["f"])
->
After 0 kbd macro iterations: undefined: Keyboard macro terminated by a command ringing the bell
What kind of vector is this talking about?
It's kinda confusing all over.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2014-02-08 11:59 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vbwpstlo.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=14206@debbugs.gnu.org \
--cc=drew.adams@oracle.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.