From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: What is an "input event"? Date: Fri, 23 Nov 2018 12:28:01 +0200 Message-ID: <83wop4f5qm.fsf@gnu.org> References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1542968768 367 195.159.176.226 (23 Nov 2018 10:26:08 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 23 Nov 2018 10:26:08 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 23 11:26:04 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gQ8ey-0008RP-CZ for ged-emacs-devel@m.gmane.org; Fri, 23 Nov 2018 11:26:04 +0100 Original-Received: from localhost ([::1]:51495 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gQ8h5-0003Fl-3a for ged-emacs-devel@m.gmane.org; Fri, 23 Nov 2018 05:28:15 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51870) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gQ8gy-0003FF-6p for emacs-devel@gnu.org; Fri, 23 Nov 2018 05:28:08 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gQ8gv-0003zi-04 for emacs-devel@gnu.org; Fri, 23 Nov 2018 05:28:08 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:44522) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gQ8gu-0003zO-TV; Fri, 23 Nov 2018 05:28:04 -0500 Original-Received: from [176.228.60.248] (port=3757 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1gQ8gu-0001dO-Gn; Fri, 23 Nov 2018 05:28:04 -0500 In-reply-to: (message from Stefan Monnier on Wed, 21 Nov 2018 11:12:15 -0500) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:231311 Archived-At: > From: Stefan Monnier > 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.