unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: What is an "input event"?
Date: Fri, 23 Nov 2018 12:28:01 +0200	[thread overview]
Message-ID: <83wop4f5qm.fsf@gnu.org> (raw)
In-Reply-To: <jwvlg5ml8gq.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Wed, 21 Nov 2018 11:12:15 -0500)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Wed, 21 Nov 2018 11:12:15 -0500
> 
> Looking at the doc of last-repeatable-command I think we should clarify
> what we mean by "input event".  The docstring says:
> 
>     Last command that may be repeated.
>     The last command executed that was not bound to an input event.
>     This is the command ‘repeat’ will try to repeat.
>     Taken from a previous value of ‘real-this-command’.
> 
> and the manual says:
> 
>     This variable stores the most recently executed command that was not
>     part of an input event.  This is the command @code{repeat} will try to
>     repeat, @xref{Repeating,,, emacs, The GNU Emacs Manual}.
> 
> but according to the source code, this variable holds the last command
> that was run via a "simple" event such as a keyboard key rather than
> a "complex" event like a mouse click (the test is simply CONSP).
> 
> Do we somewhere define "input event" to mean an event with parameters?

"Input Events" in the ELisp manual.  Which describes quite a few
classes of input events.

> I thought keyboard keys are also "input events".

Yes, keyboard input also counts as input events.

Those documentation parts should say "non-keyboard input events", or
something like that.



      parent reply	other threads:[~2018-11-23 10:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-21 16:12 What is an "input event"? Stefan Monnier
2018-11-23  7:41 ` martin rudalics
2018-11-23 10:28 ` Eli Zaretskii [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

  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=83wop4f5qm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).