GNU bug report logs -
#65360
emacs 29.1 with MSYS2: vertical scrolling with touchpad not working
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 65360 in the body.
You can then email your comments to 65360 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#65360
; Package
emacs
.
(Fri, 18 Aug 2023 05:17:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Vincent Torri <vincent.torri <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Fri, 18 Aug 2023 05:17:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hello
I have a DELL XPS 13 with Windows 10, and I installed emacs 29.1 with
msys2. When I try to scroll vertically to the bottom of the file with
touchpad, using 2 fingers, emacs content is going briefly to bottom
then is going upper
no problem with other applications
Vincent Torri
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#65360
; Package
emacs
.
(Fri, 18 Aug 2023 05:42:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 65360 <at> debbugs.gnu.org (full text, mbox):
merge 65360 65070
thanks
> From: Vincent Torri <vincent.torri <at> gmail.com>
> Date: Fri, 18 Aug 2023 07:15:39 +0200
>
> I have a DELL XPS 13 with Windows 10, and I installed emacs 29.1 with
> msys2. When I try to scroll vertically to the bottom of the file with
> touchpad, using 2 fingers, emacs content is going briefly to bottom
> then is going upper
This is a known bug#65070. Unfortunately, we don't currently have
anyone with access to such a machine who could debug the relevant code
and tell what is wrong with it. If you can run Emacs under GDB on
that machine and report some findings (I can provide more detailed
instructions), we might be able to fix this.
Merged 65070 65360.
Request was from
Eli Zaretskii <eliz <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Fri, 18 Aug 2023 05:42:03 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#65360
; Package
emacs
.
(Fri, 18 Aug 2023 05:53:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 65360 <at> debbugs.gnu.org (full text, mbox):
On Fri, Aug 18, 2023 at 7:40 AM Eli Zaretskii <eliz <at> gnu.org> wrote:
>
> merge 65360 65070
> thanks
>
> > From: Vincent Torri <vincent.torri <at> gmail.com>
> > Date: Fri, 18 Aug 2023 07:15:39 +0200
> >
> > I have a DELL XPS 13 with Windows 10, and I installed emacs 29.1 with
> > msys2. When I try to scroll vertically to the bottom of the file with
> > touchpad, using 2 fingers, emacs content is going briefly to bottom
> > then is going upper
>
> This is a known bug#65070.
ok
> Unfortunately, we don't currently have
> anyone with access to such a machine who could debug the relevant code
> and tell what is wrong with it. If you can run Emacs under GDB on
> that machine and report some findings (I can provide more detailed
> instructions), we might be able to fix this.
I can do that, tell me what to do
Vincent
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#65360
; Package
emacs
.
(Fri, 18 Aug 2023 06:30:01 GMT)
Full text and
rfc822 format available.
Message #16 received at 65360 <at> debbugs.gnu.org (full text, mbox):
> From: Vincent Torri <vincent.torri <at> gmail.com>
> Date: Fri, 18 Aug 2023 07:51:45 +0200
> Cc: 65360 <at> debbugs.gnu.org
>
> > Unfortunately, we don't currently have
> > anyone with access to such a machine who could debug the relevant code
> > and tell what is wrong with it. If you can run Emacs under GDB on
> > that machine and report some findings (I can provide more detailed
> > instructions), we might be able to fix this.
>
> I can do that, tell me what to do
Thank you.
The relevant code is in w32term.c:w32_construct_mouse_wheel. For
starters, could you please step through that function and tell what
you see when you scroll with the touchpad? In particular, does the
value of 'delta' become positive or negative depending on the
direction of the scrolling? Also, what are the computed values of p.x
and p.y, and what are the values in the structure pointer to by
'result' immediately before the function returns?
Note: to be able to show values of Lisp objects, you need to tell GDB
to read the src/.gdbinit file in the Emacs source tree:
(gdb) source /path/to/emacs/src/.gdbinit
P.S. It goes without saying that you will need to have the sources of
Emacs 29.1 available, if you don't already.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#65360
; Package
emacs
.
(Fri, 18 Aug 2023 06:42:02 GMT)
Full text and
rfc822 format available.
Message #19 received at 65360 <at> debbugs.gnu.org (full text, mbox):
On Fri, Aug 18, 2023 at 8:28 AM Eli Zaretskii <eliz <at> gnu.org> wrote:
>
> > From: Vincent Torri <vincent.torri <at> gmail.com>
> > Date: Fri, 18 Aug 2023 07:51:45 +0200
> > Cc: 65360 <at> debbugs.gnu.org
> >
> > > Unfortunately, we don't currently have
> > > anyone with access to such a machine who could debug the relevant code
> > > and tell what is wrong with it. If you can run Emacs under GDB on
> > > that machine and report some findings (I can provide more detailed
> > > instructions), we might be able to fix this.
> >
> > I can do that, tell me what to do
>
> Thank you.
>
> The relevant code is in w32term.c:w32_construct_mouse_wheel.
ok
> For
> starters, could you please step through that function and tell what
> you see when you scroll with the touchpad? In particular, does the
> value of 'delta' become positive or negative depending on the
> direction of the scrolling? Also, what are the computed values of p.x
> and p.y, and what are the values in the structure pointer to by
> 'result' immediately before the function returns?
>
> Note: to be able to show values of Lisp objects, you need to tell GDB
> to read the src/.gdbinit file in the Emacs source tree:
>
> (gdb) source /path/to/emacs/src/.gdbinit
>
> P.S. It goes without saying that you will need to have the sources of
> Emacs 29.1 available, if you don't already.
maybe it will be simpler for me to compile emacs and debug it directly
with some printf(). At least i know where to look at now
Vincent
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#65360
; Package
emacs
.
(Fri, 18 Aug 2023 06:57:02 GMT)
Full text and
rfc822 format available.
Message #22 received at 65360 <at> debbugs.gnu.org (full text, mbox):
> From: Vincent Torri <vincent.torri <at> gmail.com>
> Date: Fri, 18 Aug 2023 08:41:05 +0200
> Cc: 65360 <at> debbugs.gnu.org
>
> maybe it will be simpler for me to compile emacs and debug it directly
> with some printf(). At least i know where to look at now
That can also be done, with the caveats that:
. to look at some variable, you will have to add code and recompile
Emacs
. if the function(s) in question are invoked frequently when you
scroll, you will have a lot of output, without a good way of
knowing which output was caused by which UI gesture
But that doesn't make printf-debugging impossible, so if it's easier
for you, let's try that!
Thanks.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#65360
; Package
emacs
.
(Fri, 18 Aug 2023 07:02:02 GMT)
Full text and
rfc822 format available.
Message #25 received at 65360 <at> debbugs.gnu.org (full text, mbox):
On Fri, Aug 18, 2023 at 8:56 AM Eli Zaretskii <eliz <at> gnu.org> wrote:
>
> > From: Vincent Torri <vincent.torri <at> gmail.com>
> > Date: Fri, 18 Aug 2023 08:41:05 +0200
> > Cc: 65360 <at> debbugs.gnu.org
> >
> > maybe it will be simpler for me to compile emacs and debug it directly
> > with some printf(). At least i know where to look at now
>
> That can also be done, with the caveats that:
>
> . to look at some variable, you will have to add code and recompile
> Emacs
normally, make will recompile only what is needed, one file
> . if the function(s) in question are invoked frequently when you
> scroll, you will have a lot of output, without a good way of
> knowing which output was caused by which UI gesture
well, there will not a lot of output : just scrolling once to the
bottom is problematic
> But that doesn't make printf-debugging impossible, so if it's easier
> for you, let's try that!
i'll inform you about what I get
Vincent
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#65360
; Package
emacs
.
(Fri, 18 Aug 2023 19:48:02 GMT)
Full text and
rfc822 format available.
Message #28 received at 65360 <at> debbugs.gnu.org (full text, mbox):
On Fri, Aug 18, 2023 at 9:01 AM Vincent Torri <vincent.torri <at> gmail.com> wrote:
>
> On Fri, Aug 18, 2023 at 8:56 AM Eli Zaretskii <eliz <at> gnu.org> wrote:
> >
> > > From: Vincent Torri <vincent.torri <at> gmail.com>
> > > Date: Fri, 18 Aug 2023 08:41:05 +0200
> > > Cc: 65360 <at> debbugs.gnu.org
> > >
> > > maybe it will be simpler for me to compile emacs and debug it directly
> > > with some printf(). At least i know where to look at now
> >
> > That can also be done, with the caveats that:
> >
> > . to look at some variable, you will have to add code and recompile
> > Emacs
>
> normally, make will recompile only what is needed, one file
>
> > . if the function(s) in question are invoked frequently when you
> > scroll, you will have a lot of output, without a good way of
> > knowing which output was caused by which UI gesture
>
> well, there will not a lot of output : just scrolling once to the
> bottom is problematic
>
> > But that doesn't make printf-debugging impossible, so if it's easier
> > for you, let's try that!
>
> i'll inform you about what I get
- when I move two fingers from bottom to top of the touchpad, i get for example:
* delta: -1
* p 2227 x 1414
delta is always negative in that case
- when I move two fingers from top to bottom of the touchpad, i get for example:
* delta: 4
* p 2205 x 1336
delta is always positive in that case
I've also found that the function always exits in that test, in case it helps:
if (eabs (sum_delta_y) < WHEEL_DELTA)
{
result->kind = NO_EVENT;
return Qnil;
}
Unrelated : you should check the warnings, at least on Windows,
because i've seen a NULL pointer dereference, and several use of
uninitialized variables
Vincent
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#65360
; Package
emacs
.
(Sat, 26 Aug 2023 03:02:02 GMT)
Full text and
rfc822 format available.
Message #31 received at 65360 <at> debbugs.gnu.org (full text, mbox):
hello
it is fixed in current git
thank you
Vincent Torri
Reply sent
to
Eli Zaretskii <eliz <at> gnu.org>
:
You have taken responsibility.
(Sat, 26 Aug 2023 05:53:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
Vincent Torri <vincent.torri <at> gmail.com>
:
bug acknowledged by developer.
(Sat, 26 Aug 2023 05:53:01 GMT)
Full text and
rfc822 format available.
Message #36 received at 65360-done <at> debbugs.gnu.org (full text, mbox):
> From: Vincent Torri <vincent.torri <at> gmail.com>
> Date: Sat, 26 Aug 2023 05:00:53 +0200
> Cc: 65360 <at> debbugs.gnu.org
>
> hello
>
> it is fixed in current git
Thanks for testing, and for helping to diagnose the issue. I'm
therefore closing this bug.
Reply sent
to
Eli Zaretskii <eliz <at> gnu.org>
:
You have taken responsibility.
(Sat, 26 Aug 2023 05:53:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Hiroya Ebine <hiroya.ebine1 <at> gmail.com>
:
bug acknowledged by developer.
(Sat, 26 Aug 2023 05:53:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sat, 23 Sep 2023 11:24:11 GMT)
Full text and
rfc822 format available.
This bug report was last modified 1 year and 231 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.