all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: matthew.fidler@gmail.com, 15653@debbugs.gnu.org
Subject: bug#15653: 24.3; call-interactively not sending keys
Date: Sat, 17 Aug 2019 14:21:00 -0700	[thread overview]
Message-ID: <87a7c7mqtf.fsf@mouse.gnus.org> (raw)
In-Reply-To: <83k1bcntta.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 17 Aug 2019 10:18:41 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Yes, it _is_ the interactive spec.  When that spec uses 'e' or '@' or
> something else that needs to analyze the invoking events, then Emacs
> provides the information from KEYS instead.
>
> I don't really see hat needs to be clarified in the docs, but given
> the above, perhaps Lars or Matthew could propose a clarification?

The confusion that both Matthew and me had here was that the doc string
talked about "inquiring what events that invoked it", and
`this-command-keys' talks about "return the key sequence that invoked
this command".  So it's not an unnatural inference to make that these
things are somehow tied together.

I've now clarified the call-interactively doc string to say explicitly
that the argument affects the return value of the interactive spec of
FUNCTION.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2019-08-17 21:21 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
2019-08-17  7:18   ` Eli Zaretskii
2019-08-17 21:21     ` Lars Ingebrigtsen [this message]

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=87a7c7mqtf.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=15653@debbugs.gnu.org \
    --cc=eliz@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 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.