unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 26626@debbugs.gnu.org
Subject: bug#26626: 24.5; doc of `last-command-event' and `last-nonmenu-event'
Date: Sun, 23 Apr 2017 10:35:19 -0700 (PDT)	[thread overview]
Message-ID: <036c27e0-4509-45e8-942e-9b454b34b0ef@default> (raw)

The doc is not very clear - both (elisp) `Command Loop Info' and the doc
strings.

The essential difference in the descriptions seems to be the last input
event read "as part of a key sequence" versus read "as part of a
command".  But "read as part of a command" is unclear.  Does it mean
read by a command (e.g., by a call to `read-char' within the command
definition)?  No.  But that's all I can think of, when reading that
description.

The doc of `last-nonmenu-event' is pretty clear.  Or at least it is
before reading also the doc of `last-command-event' and trying to make
sense of that.  Even the name of the latter is unclear - what's a
"command event"?

The example given for `last-command-event' suggests that what is meant
is the last event in the key sequence that invoked/initiated a command.
I think that's closer to what the meaning/behavior is.

In GNU Emacs 24.5.1 (i686-pc-mingw32)
 of 2015-04-11 on LEG570
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/usr --host=i686-pc-mingw32'





             reply	other threads:[~2017-04-23 17:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-23 17:35 Drew Adams [this message]
2019-07-26  9:33 ` bug#26626: 24.5; doc of `last-command-event' and `last-nonmenu-event' 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
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=036c27e0-4509-45e8-942e-9b454b34b0ef@default \
    --to=drew.adams@oracle.com \
    --cc=26626@debbugs.gnu.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).