unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#4907: 23.1; (elisp)Motion Events: Incorrect event description
@ 2009-11-11 18:31 ` Drew Adams
  2009-11-14 15:20   ` bug#4907: marked as done (23.1; (elisp)Motion Events: Incorrect event description) Emacs bug Tracking System
  0 siblings, 1 reply; 2+ messages in thread
From: Drew Adams @ 2009-11-11 18:31 UTC (permalink / raw)
  To: bug-gnu-emacs

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)'
 







^ permalink raw reply	[flat|nested] 2+ messages in thread

* bug#4907: marked as done (23.1; (elisp)Motion Events: Incorrect event description)
  2009-11-11 18:31 ` bug#4907: 23.1; (elisp)Motion Events: Incorrect event description Drew Adams
@ 2009-11-14 15:20   ` Emacs bug Tracking System
  0 siblings, 0 replies; 2+ messages in thread
From: Emacs bug Tracking System @ 2009-11-14 15:20 UTC (permalink / raw)
  To: Chong Yidong

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]

Your message dated Sat, 14 Nov 2009 10:16:15 -0500
with message-id <87pr7l9lxc.fsf@stupidchicken.com>
and subject line 23.1; (elisp)Motion Events: Incorrect event description
has caused the Emacs bug report #4907,
regarding 23.1; (elisp)Motion Events: Incorrect event description
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
4907: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=4907
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 4233 bytes --]

From: "Drew Adams" <drew.adams@oracle.com>
To: <bug-gnu-emacs@gnu.org>
Subject: 23.1; (elisp)Motion Events: Incorrect event description
Date: Wed, 11 Nov 2009 10:31:45 -0800
Message-ID: <F97822A7AD724681B7BDF2B2E5786C33@us.oracle.com>

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)'
 




[-- Attachment #3: Type: message/rfc822, Size: 1677 bytes --]

From: Chong Yidong <cyd@stupidchicken.com>
To: Drew@furry, Adams@furry, " <drew.adams@oracle.com>"@furry
Cc: 4907-done@emacsbugs.donarmstrong.com
Subject: 23.1; (elisp)Motion Events: Incorrect event description
Date: Sat, 14 Nov 2009 10:16:15 -0500
Message-ID: <87pr7l9lxc.fsf@stupidchicken.com>

> This is incorrect, AFAICT. (mouse-movement (POSITION)) should
> instead be (mouse-movement POSITION).  The value of POSITION is
> itself a list.

Fixed, thanks.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-11-14 15:20 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <87pr7l9lxc.fsf@stupidchicken.com>
2009-11-11 18:31 ` bug#4907: 23.1; (elisp)Motion Events: Incorrect event description Drew Adams
2009-11-14 15:20   ` bug#4907: marked as done (23.1; (elisp)Motion Events: Incorrect event description) Emacs bug Tracking System

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).