From: Drew Adams <drew.adams@oracle.com>
To: Andreas Schwab <schwab@linux-m68k.org>
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:37:14 -0700 (PDT) [thread overview]
Message-ID: <655ff364-e380-4278-bc2a-2cabddf6febd@default> (raw)
In-Reply-To: <87k1c4svf9.fsf@igel.home>
> > There's no such thing as a "command key sequence",
> > as opposed, one imagines, to a "non-command key
> > sequence". A key sequence that is complete is
> > always bound to a command.
>
> Not true. Everything that isn't a prefix key is a complete key, bound
> or not.
Right. I misspoke. I didn't mean that only bound
key sequences are complete key sequences.
The point is that there's no such thing as a "command"
key sequence", just as there's no such thing as a
non-command key sequence. Key sequences can be bound
only to commands - not to anything else. Commands
can be bound to key sequences - not to anything else.
next prev parent reply other threads:[~2019-07-26 15:37 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 [this message]
2019-07-26 14:50 ` Noam Postavsky
2019-07-26 15:46 ` Drew Adams
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=655ff364-e380-4278-bc2a-2cabddf6febd@default \
--to=drew.adams@oracle.com \
--cc=26626@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=schwab@linux-m68k.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 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).