From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.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 09:56:11 +0300 [thread overview]
Message-ID: <83shy4x5ro.fsf@gnu.org> (raw)
In-Reply-To: <87k2jh1fea.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 29 Apr 2016 01:29:17 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Fri, 29 Apr 2016 01:29:17 +0200
> Cc: 14206@debbugs.gnu.org
>
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
> > Kevin Rodgers <kevin.d.rodgers@gmail.com> writes:
> >
> >>> (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)
> >
> > So is the "If MACRO is a symbol, its function definition is used." thing
> > wrong?
>
> This is what Fexecute_kbd_macro does:
>
> final = indirect_function (macro);
> if (!STRINGP (final) && !VECTORP (final))
> error ("Keyboard macros must be strings or vectors");
>
> In what contexts can a function end up being a string? Uhm... If
> somebody has said
>
> (fset 'foo "bar")
>
> ?
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.
next prev parent reply other threads:[~2016-04-29 6:56 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 [this message]
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=83shy4x5ro.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=14206@debbugs.gnu.org \
--cc=kevin.d.rodgers@gmail.com \
--cc=larsi@gnus.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.
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.