GNU bug report logs -
#6372
24.0.50; C-mouse-1 activates region on Windows
Previous Next
To reply to this bug, email your comments to 6372 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
owner <at> debbugs.gnu.org, bug-gnu-emacs <at> gnu.org
:
bug#6372
; Package
emacs
.
(Mon, 07 Jun 2010 17:22:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
"Drew Adams" <drew.adams <at> oracle.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Mon, 07 Jun 2010 17:22:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
emacs -Q
1. Click C-mouse-1. The Buffer Menu opens.
2. Click mouse-1 outside the menu. The menu disappears, which is
correct.
But the region is activated, which is incorrect. Clicking mouse-1 here
should simply set point, without activating the region.
In GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600)
of 2010-05-23 on G41R2F1
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --no-opt --cflags -Ic:/xpm/include'
Forcibly Merged 6372 11772.
Request was from
Chong Yidong <cyd <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Sun, 08 Jul 2012 13:40:01 GMT)
Full text and
rfc822 format available.
Disconnected #6372 from all other report(s).
Request was from
Chong Yidong <cyd <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Sun, 08 Jul 2012 13:43:02 GMT)
Full text and
rfc822 format available.
Did not alter fixed versions and reopened.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 08 Jul 2012 13:46:01 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#6372
; Package
emacs
.
(Sun, 08 Jul 2012 13:47:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 6372 <at> debbugs.gnu.org (full text, mbox):
"Drew Adams" <drew.adams <at> oracle.com> writes:
> 1. Click C-mouse-1. The Buffer Menu opens.
>
> 2. Click mouse-1 outside the menu. The menu disappears, which is
> correct.
>
> But the region is activated, which is incorrect. Clicking mouse-1 here
> should simply set point, without activating the region.
FWIW, this is not reproducible on GNU/Linux. Maybe a Windows-only
issue; can someone with access to Windows check if this still happens?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#6372
; Package
emacs
.
(Sun, 08 Jul 2012 15:06:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 6372 <at> debbugs.gnu.org (full text, mbox):
Chong Yidong <cyd <at> gnu.org> writes:
> "Drew Adams" <drew.adams <at> oracle.com> writes:
>
>> 1. Click C-mouse-1. The Buffer Menu opens.
>>
>> 2. Click mouse-1 outside the menu. The menu disappears, which is
>> correct.
>>
>> But the region is activated, which is incorrect. Clicking mouse-1 here
>> should simply set point, without activating the region.
>
> FWIW, this is not reproducible on GNU/Linux. Maybe a Windows-only
> issue; can someone with access to Windows check if this still happens?
It does happen.
And if I ctrl-click mouse-1 when the menu if open, minibuffer says
"<C-drag-mouse-1> is undefined", so looks like doing mouse-1 click when
the menu is open is registered as drag-mouse-1 event.
(I tried it in Ubuntu on an older Emacs 24 build, and that didn't happen
either).
In GNU Emacs 24.1.50.1 (i386-mingw-nt6.1.7601) of 2012-07-06.
--Dmitry
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#6372
; Package
emacs
.
(Sun, 08 Jul 2012 17:25:01 GMT)
Full text and
rfc822 format available.
Message #20 received at 6372 <at> debbugs.gnu.org (full text, mbox):
> "Drew Adams" <drew.adams <at> oracle.com> writes:
>
> > 1. Click C-mouse-1. The Buffer Menu opens.
> >
> > 2. Click mouse-1 outside the menu. The menu disappears, which is
> > correct.
> >
> > But the region is activated, which is incorrect. Clicking
> > mouse-1 here should simply set point, without activating the region.
>
> FWIW, this is not reproducible on GNU/Linux. Maybe a Windows-only
> issue; can someone with access to Windows check if this still happens?
Yes, the bug is still there.
I just checked in this build:
In GNU Emacs 24.1.50.1 (i386-mingw-nt5.1.2600)
of 2012-07-01 on MARVIN
Bzr revision: 108826 yamaoka <at> jpl.org-20120702004841-kzatmydft6dct0ry
Windowing system distributor `Microsoft Corp.', version 5.1.2600
Configured using:
`configure --with-gcc (4.6) --no-opt --enable-checking --cflags
-ID:/devel/emacs/libs/libXpm-3.5.8/include
-ID:/devel/emacs/libs/libXpm-3.5.8/src
-ID:/devel/emacs/libs/libpng-dev_1.4.3-1/include
-ID:/devel/emacs/libs/zlib-dev_1.2.5-2/include
-ID:/devel/emacs/libs/giflib-4.1.4-1/include
-ID:/devel/emacs/libs/jpeg-6b-4/include
-ID:/devel/emacs/libs/tiff-3.8.2-1/include
-ID:/devel/emacs/libs/gnutls-3.0.9/include
-ID:/devel/emacs/libs/libiconv-1.13.1-1-dev/include
-ID:/devel/emacs/libs/libxml2-2.7.8/include/libxml2'
emacs -Q
`C-mouse-1'
Move mouse outside the popped up menu, and so that some text is between the
first click and the next.
`mouse-1'
The text between the first and second clicks is selected (active region).
Thx.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#6372
; Package
emacs
.
(Sun, 08 Jul 2012 18:16:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 6372 <at> debbugs.gnu.org (full text, mbox):
> From: "Drew Adams" <drew.adams <at> oracle.com>
> Date: Sun, 8 Jul 2012 10:18:40 -0700
> Cc: 6372 <at> debbugs.gnu.org
>
> > "Drew Adams" <drew.adams <at> oracle.com> writes:
> >
> > > 1. Click C-mouse-1. The Buffer Menu opens.
> > >
> > > 2. Click mouse-1 outside the menu. The menu disappears, which is
> > > correct.
> > >
> > > But the region is activated, which is incorrect. Clicking
> > > mouse-1 here should simply set point, without activating the region.
> >
> > FWIW, this is not reproducible on GNU/Linux. Maybe a Windows-only
> > issue; can someone with access to Windows check if this still happens?
>
> Yes, the bug is still there.
Indeed. After the recipe, "C-h l" shows this:
<C-down-mouse-1> <drag-mouse-1> C-h l
What do you see on GNU/Linux? Which toolkit(s) did you try it with?
FWIW, in the MSDOS build the problem doesn't happen, and view-lossage
shows just this:
<C-down-mouse-1> C-h l
Any clue where could drag-mouse-1 come from? I guess we don't discard
some events that we should.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#6372
; Package
emacs
.
(Mon, 09 Jul 2012 04:43:04 GMT)
Full text and
rfc822 format available.
Message #26 received at 6372 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
> Indeed. After the recipe, "C-h l" shows this:
>
> <C-down-mouse-1> <drag-mouse-1> C-h l
>
> What do you see on GNU/Linux? Which toolkit(s) did you try it with?
>
> FWIW, in the MSDOS build the problem doesn't happen, and view-lossage
> shows just this:
>
> <C-down-mouse-1> C-h l
>
> Any clue where could drag-mouse-1 come from? I guess we don't discard
> some events that we should.
On GNU/Linux (both GTK build and Lucid build) I see
<C-down-mouse-1> C-h l
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#6372
; Package
emacs
.
(Sat, 21 Jul 2012 11:49:02 GMT)
Full text and
rfc822 format available.
Message #29 received at 6372 <at> debbugs.gnu.org (full text, mbox):
> From: Chong Yidong <cyd <at> gnu.org>
> Cc: Drew Adams <drew.adams <at> oracle.com>, 6372 <at> debbugs.gnu.org
> Date: Mon, 09 Jul 2012 12:37:05 +0800
>
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
> > Indeed. After the recipe, "C-h l" shows this:
> >
> > <C-down-mouse-1> <drag-mouse-1> C-h l
> >
> > What do you see on GNU/Linux? Which toolkit(s) did you try it with?
> >
> > FWIW, in the MSDOS build the problem doesn't happen, and view-lossage
> > shows just this:
> >
> > <C-down-mouse-1> C-h l
> >
> > Any clue where could drag-mouse-1 come from? I guess we don't discard
> > some events that we should.
>
> On GNU/Linux (both GTK build and Lucid build) I see
>
> <C-down-mouse-1> C-h l
Thanks.
I'm sorry, but it will take someone who knows more than I do about
MS-Windows messages and their processing to fix this one. I describe
my findings below in the hope that someone will pick up where I left
off.
We track mouse events during pop-up menu by sending the
WM_EMACS_TRACKPOPUPMENU message to the Emacs message pump. This
message is handled by w32_wnd_proc around line 3770 of w32fns.c.
There, we call TrackPopupMenu, a Windows API that displays the menu
and returns the user selection of menu items. After TrackPopupMenu
returns, we remove any mouse events still in the message queue, by
calling PeekMessage with appropriate arguments, and return the user
selection to our caller, which is w32_menu_show. The user selection
returned is zero when the user closes the menu without selecting any
item, by clicking outside the menu. w32_menu_show then removes any
mouse events in the Emacs event queue by calling discard_mouse_events.
What happens in this case, and is the reason for the bug, is that
somehow the mouse click event that pops down the menu is not delivered
to Emacs until _after_ w32_menu_show returns. That click is not
removed by PeekMessage mentioned above, and is not discarded by
discard_mouse_events. It is read by w32_wnd_proc only after all of
the above processing is complete, and any memory of the menu that was
popped down is gone. So Emacs processes that mouse click as a normal
event, oblivious to the fact that it actually happened as part of the
menu.
What I don't understand here is why that mouse click is not delivered
when we call PeekMessage, so that it could be discarded. It's as if
Windows withholds that message from being put into the Emacs message
queue. Why is that, and what can we do to be able to peek at that
click message as part of menu processing and discard it, is beyond me.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#6372
; Package
emacs
.
(Wed, 08 Aug 2012 18:48:02 GMT)
Full text and
rfc822 format available.
Message #32 received at 6372 <at> debbugs.gnu.org (full text, mbox):
ping.
> From: Eli Zaretskii Sent: Saturday, July 21, 2012 4:42 AM
> I'm sorry, but it will take someone who knows more than I do about
> MS-Windows messages and their processing to fix this one. I describe
> my findings below in the hope that someone will pick up where I left
> off.
>
> We track mouse events during pop-up menu by sending the
> WM_EMACS_TRACKPOPUPMENU message to the Emacs message pump. This
> message is handled by w32_wnd_proc around line 3770 of w32fns.c.
> There, we call TrackPopupMenu, a Windows API that displays the menu
> and returns the user selection of menu items. After TrackPopupMenu
> returns, we remove any mouse events still in the message queue, by
> calling PeekMessage with appropriate arguments, and return the user
> selection to our caller, which is w32_menu_show. The user selection
> returned is zero when the user closes the menu without selecting any
> item, by clicking outside the menu. w32_menu_show then removes any
> mouse events in the Emacs event queue by calling discard_mouse_events.
>
> What happens in this case, and is the reason for the bug, is that
> somehow the mouse click event that pops down the menu is not delivered
> to Emacs until _after_ w32_menu_show returns. That click is not
> removed by PeekMessage mentioned above, and is not discarded by
> discard_mouse_events. It is read by w32_wnd_proc only after all of
> the above processing is complete, and any memory of the menu that was
> popped down is gone. So Emacs processes that mouse click as a normal
> event, oblivious to the fact that it actually happened as part of the
> menu.
>
> What I don't understand here is why that mouse click is not delivered
> when we call PeekMessage, so that it could be discarded. It's as if
> Windows withholds that message from being put into the Emacs message
> queue. Why is that, and what can we do to be able to peek at that
> click message as part of menu processing and discard it, is beyond me.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#6372
; Package
emacs
.
(Sun, 16 Sep 2012 23:37:01 GMT)
Full text and
rfc822 format available.
Message #35 received at 6372 <at> debbugs.gnu.org (full text, mbox):
ping
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#6372
; Package
emacs
.
(Fri, 19 Oct 2012 15:06:02 GMT)
Full text and
rfc822 format available.
Message #38 received at 6372 <at> debbugs.gnu.org (full text, mbox):
ping
Added tag(s) help and confirmed.
Request was from
Noam Postavsky <npostavs <at> users.sourceforge.net>
to
control <at> debbugs.gnu.org
.
(Fri, 01 Jul 2016 03:41:01 GMT)
Full text and
rfc822 format available.
bug reassigned from package 'emacs' to 'emacs,w32'.
Request was from
Noam Postavsky <npostavs <at> users.sourceforge.net>
to
control <at> debbugs.gnu.org
.
(Fri, 01 Jul 2016 03:41:01 GMT)
Full text and
rfc822 format available.
bug No longer marked as found in versions 24.0.50 and 24.1.
Request was from
Noam Postavsky <npostavs <at> users.sourceforge.net>
to
control <at> debbugs.gnu.org
.
(Fri, 01 Jul 2016 03:41:01 GMT)
Full text and
rfc822 format available.
Severity set to 'minor' from 'normal'
Request was from
Noam Postavsky <npostavs <at> users.sourceforge.net>
to
control <at> debbugs.gnu.org
.
(Fri, 01 Jul 2016 03:41:02 GMT)
Full text and
rfc822 format available.
bug Marked as found in versions 25.0.95.
Request was from
Noam Postavsky <npostavs <at> users.sourceforge.net>
to
control <at> debbugs.gnu.org
.
(Fri, 01 Jul 2016 03:41:02 GMT)
Full text and
rfc822 format available.
bug reassigned from package 'emacs,w32' to 'emacs'.
Request was from
Noam Postavsky <npostavs <at> users.sourceforge.net>
to
control <at> debbugs.gnu.org
.
(Fri, 01 Jul 2016 04:00:02 GMT)
Full text and
rfc822 format available.
bug No longer marked as found in versions 25.0.95.
Request was from
Noam Postavsky <npostavs <at> users.sourceforge.net>
to
control <at> debbugs.gnu.org
.
(Fri, 01 Jul 2016 04:00:02 GMT)
Full text and
rfc822 format available.
bug Marked as found in versions 24.1.
Request was from
Noam Postavsky <npostavs <at> users.sourceforge.net>
to
control <at> debbugs.gnu.org
.
(Fri, 01 Jul 2016 04:00:02 GMT)
Full text and
rfc822 format available.
bug Marked as found in versions 25.0.95.
Request was from
Noam Postavsky <npostavs <at> users.sourceforge.net>
to
control <at> debbugs.gnu.org
.
(Fri, 01 Jul 2016 04:00:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#6372
; Package
emacs
.
(Tue, 18 Aug 2020 11:11:01 GMT)
Full text and
rfc822 format available.
Message #59 received at 6372 <at> debbugs.gnu.org (full text, mbox):
"Drew Adams" <drew.adams <at> oracle.com> writes:
> emacs -Q
>
> 1. Click C-mouse-1. The Buffer Menu opens.
>
> 2. Click mouse-1 outside the menu. The menu disappears, which is
> correct.
>
> But the region is activated, which is incorrect. Clicking mouse-1 here
> should simply set point, without activating the region.
>
>
> In GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600)
> of 2010-05-23 on G41R2F1
> Windowing system distributor `Microsoft Corp.', version 5.1.2600
> configured using `configure --with-gcc (3.4) --no-opt --cflags -Ic:/xpm/include'
That was more than 10 years ago.
I can't reproduce this on GNU/Linux, but from the discussion this looked
like a Windows-specific bug.
Since this was such a long time ago, I just wanted to ask if you (or
anyone else) can still reproduce this? Thanks.
Best regards,
Stefan Kangas
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#6372
; Package
emacs
.
(Tue, 18 Aug 2020 12:12:02 GMT)
Full text and
rfc822 format available.
Message #62 received at 6372 <at> debbugs.gnu.org (full text, mbox):
> From: Stefan Kangas <stefan <at> marxist.se>
> Date: Tue, 18 Aug 2020 11:10:33 +0000
> Cc: 6372 <at> debbugs.gnu.org
>
> > emacs -Q
> >
> > 1. Click C-mouse-1. The Buffer Menu opens.
> >
> > 2. Click mouse-1 outside the menu. The menu disappears, which is
> > correct.
> >
> > But the region is activated, which is incorrect. Clicking mouse-1 here
> > should simply set point, without activating the region.
> >
> >
> > In GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600)
> > of 2010-05-23 on G41R2F1
> > Windowing system distributor `Microsoft Corp.', version 5.1.2600
> > configured using `configure --with-gcc (3.4) --no-opt --cflags -Ic:/xpm/include'
>
> That was more than 10 years ago.
>
> I can't reproduce this on GNU/Linux, but from the discussion this looked
> like a Windows-specific bug.
>
> Since this was such a long time ago, I just wanted to ask if you (or
> anyone else) can still reproduce this? Thanks.
I still see it, yes.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#6372
; Package
emacs
.
(Tue, 18 Aug 2020 16:41:02 GMT)
Full text and
rfc822 format available.
Message #65 received at 6372 <at> debbugs.gnu.org (full text, mbox):
> I still see it, yes.
I do too.
Changed bug title to '24.0.50; C-mouse-1 activates region on Windows' from '24.0.50; C-mouse-1 activates region'
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Sun, 17 Apr 2022 13:57:01 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#6372
; Package
emacs
.
(Fri, 16 Aug 2024 01:20:02 GMT)
Full text and
rfc822 format available.
Message #70 received at 6372 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
This seems to happen because TrackPopupMenu returns as
soon as the WM_LBUTTONDOWN is received. That message is
correctly purged. The problem comes from the subsequent
WM_LBUTTONUP message.
This patch is not a clean solution, but keeps the problem local.
[patch.diff (text/plain, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#6372
; Package
emacs
.
(Sun, 18 Aug 2024 21:49:01 GMT)
Full text and
rfc822 format available.
Message #73 received at 6372 <at> debbugs.gnu.org (full text, mbox):
Cecilio Pardo <cpardo <at> imayhem.com> writes:
> This seems to happen because TrackPopupMenu returns as
> soon as the WM_LBUTTONDOWN is received. That message is
> correctly purged. The problem comes from the subsequent
> WM_LBUTTONUP message.
>
> This patch is not a clean solution, but keeps the problem local.
>
>
>
> [2. text/plain; patch.diff]...
To confirm, is the bug report related to 24.0.50, a rather old version?
Have you checked if this bug is present in a recent version of Emacs?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#6372
; Package
emacs
.
(Mon, 19 Aug 2024 07:13:02 GMT)
Full text and
rfc822 format available.
Message #76 received at 6372 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 18/08/2024 23:47, Jeremy Bryant wrote:
>
>> This seems to happen because TrackPopupMenu returns as
>> soon as the WM_LBUTTONDOWN is received. That message is
>> correctly purged. The problem comes from the subsequent
>> WM_LBUTTONUP message.
>>
>> This patch is not a clean solution, but keeps the problem local.
>>
>>
>>
>> [2. text/plain; patch.diff]...
> To confirm, is the bug report related to 24.0.50, a rather old version?
>
> Have you checked if this bug is present in a recent version of Emacs?
Yes, it is present in current version.
[Message part 2 (text/html, inline)]
This bug report was last modified 297 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.