From: Lars Ingebrigtsen <larsi@gnus.org>
To: Matthew Fidler <matthew.fidler@gmail.com>
Cc: 15653@debbugs.gnu.org
Subject: bug#15653: 24.3; call-interactively not sending keys
Date: Wed, 14 Aug 2019 20:12:08 -0700 [thread overview]
Message-ID: <87zhkb3ywn.fsf@mouse.gnus.org> (raw)
In-Reply-To: <CAOmN8O60oapQc-s4POZ0fW-DYBthXB=p0YGMHfhhEiHmqDtUsw@mail.gmail.com> (Matthew Fidler's message of "Sun, 20 Oct 2013 02:50:16 +0800")
Matthew Fidler <matthew.fidler@gmail.com> writes:
> After starting emacs -Q evaluate the following:
>
> (defun test-me ()
> (interactive)
> (message "Test Me: %s" (key-description (this-single-command-keys))))
>
> (defun test-me-2 ()
> (interactive)
> (message "Test Me 2: %s" (key-description (this-single-command-keys)))
> (call-interactively 'test-me nil (read-kbd-macro "C-1" t)))
>
> (global-set-key (read-kbd-macro "C-c a" t) 'test-me-2)
>
> Then, Type C-c a. The message shows:
>
> Test Me 2: C-c a
> Test Me: C-c a
>
> It should show
>
> Test Me 2: C-1
> Test Me: C-c a
The documentation here is rather unclear:
---
Optional third arg KEYS, if given, specifies the sequence of events to
supply, as a vector, if the command inquires which events were used to
invoke it.
---
But apparently `this-single-command-keys' is not the way to inquire
about what events were used to invoke it, and I'm not quite sure what
this is in reference to. I thought that perhaps it was an interactive
spec or something, but no.
Reading the source code wasn't enlightening, either. Anybody know what
"inquires which events" is in reference to?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-08-15 3:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-19 18:50 bug#15653: 24.3; call-interactively not sending keys Matthew Fidler
2019-08-15 3:12 ` Lars Ingebrigtsen [this message]
2019-08-17 7:18 ` Eli Zaretskii
2019-08-17 21:21 ` 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=87zhkb3ywn.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=15653@debbugs.gnu.org \
--cc=matthew.fidler@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).