From: "Drew Adams" <drew.adams@oracle.com>
To: <bug-gnu-emacs@gnu.org>
Subject: bug#4907: 23.1; (elisp)Motion Events: Incorrect event description
Date: Wed, 11 Nov 2009 10:31:45 -0800 [thread overview]
Message-ID: <F97822A7AD724681B7BDF2B2E5786C33@us.oracle.com> (raw)
The node says:
Emacs sometimes generates "mouse motion" events to describe motion of
the mouse without any button activity. Mouse motion events are
represented by lists that look like this:
(mouse-movement (POSITION))
The second element of the list describes the current position of the
mouse, just as in a click event (*note Click Events::).
The special form `track-mouse' enables generation of motion events
within its body. Outside of `track-mouse' forms, Emacs does not
generate events for mere motion of the mouse, and these events do not
appear. *Note Mouse Tracking::.
This is incorrect, AFAICT. (mouse-movement (POSITION)) should
instead be (mouse-movement POSITION). The value of POSITION is
itself a list. This is an example value of a motion event:
(mouse-movement (#<window 10 on *info*> mode-line (256 . 332) 9231031
(#(" (elisp) Motion Events" 9 22 (face mode-line-buffer-id help-echo
"mouse-1: scroll forward, mouse-3: scroll back" mouse-face
mode-line-highlight local-map (keymap (mode-line keymap (mouse-3
. Info-mouse-scroll-down) (mouse-1 . Info-mouse-scroll-up))))) . 12)
82181 (31 . 155) nil (7 . 12) (8 . 16)))
In GNU Emacs 23.1.1 (i386-mingw-nt5.1.2600)
of 2009-07-29 on SOFT-MJASON
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (4.4)'
next reply other threads:[~2009-11-11 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87pr7l9lxc.fsf@stupidchicken.com>
2009-11-11 18:31 ` Drew Adams [this message]
2009-11-14 15:20 ` bug#4907: marked as done (23.1; (elisp)Motion Events: Incorrect event description) Emacs bug Tracking System
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F97822A7AD724681B7BDF2B2E5786C33@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=4907@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.