From: Drew Adams <drew.adams@oracle.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 26626@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#26626: 24.5; doc of `last-command-event' and `last-nonmenu-event'
Date: Fri, 26 Jul 2019 08:46:21 -0700 (PDT) [thread overview]
Message-ID: <29db676e-f1f3-4dfc-b494-fb2c97f59b2e@default> (raw)
In-Reply-To: <858sskkfyq.fsf@gmail.com>
> > There's no such thing as a "command key sequence",
> > as opposed, one imagines, to a "non-command key
> > sequence".
>
> It's just what you said in the OP: "the key sequence that
> invoked/initiated a command".
Yes, that's still the best way to put it, I think.
> > I still think that the text for this should borrow
> > from what is said for `last-nonmenu-event'. IIUC,
> > `last-command-event' is the "last input event read
> > as part of a key sequence".
>
> That would be misleading.
You're right. It's the first input event read
as part of a key sequence - not the last such.
The larger point was that it is an input event
read as part of a key sequence. But yes, you're
absolutely right that the text for
`last-nonmenu-event' needs more of a tweak than
the one I gave it.
next prev parent reply other threads:[~2019-07-26 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-23 17:35 bug#26626: 24.5; doc of `last-command-event' and `last-nonmenu-event' Drew Adams
2019-07-26 9:33 ` Lars Ingebrigtsen
2019-07-26 14:30 ` Drew Adams
2019-07-26 14:49 ` Andreas Schwab
2019-07-26 15:37 ` Drew Adams
2019-07-26 14:50 ` Noam Postavsky
2019-07-26 15:46 ` Drew Adams [this message]
2019-07-26 15:50 ` Noam Postavsky
2019-07-26 15:53 ` Drew Adams
2019-07-26 21:43 ` Noam Postavsky
2019-07-27 0:25 ` Drew Adams
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=29db676e-f1f3-4dfc-b494-fb2c97f59b2e@default \
--to=drew.adams@oracle.com \
--cc=26626@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=npostavs@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).