From: Alex Gramiak <agrambot@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 35246@debbugs.gnu.org
Subject: bug#35246: 26.2; Mouse wheel scrolling in GTK build sometimes scrolls the entire buffer
Date: Mon, 15 Apr 2019 11:10:30 -0600 [thread overview]
Message-ID: <87sgujjit5.fsf@gmail.com> (raw)
In-Reply-To: <83a7gri5vo.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 15 Apr 2019 19:35:07 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Alex Gramiak <agrambot@gmail.com>
>> Cc: 35246@debbugs.gnu.org
>> Date: Mon, 15 Apr 2019 10:18:24 -0600
>>
>> > What does "C-h l" show after that?
>>
>> A couple days ago I had a similar event happen (busy cursor pops up, and
>> a few seconds later normal mouse scrolling occurred). C-h l in that
>> window:
>>
>> <help-echo> <down-mouse-5> <mouse-5> [mwheel-scroll]
>> <double-down-mouse-5> <double-mouse-5> [mwheel-scroll]
>> <triple-down-mouse-5> <triple-mouse-5> [mwheel-scroll]
>> <triple-down-mouse-5> <triple-mouse-5> [mwheel-scroll]
>> <triple-down-mouse-5> <triple-mouse-5> [mwheel-scroll]
>> <triple-down-mouse-5> <triple-mouse-5> [mwheel-scroll]
>> <triple-down-mouse-5> <triple-mouse-5> [mwheel-scroll]
>> <down-mouse-4> <mouse-4> [mwheel-scroll]
>> <double-down-mouse-4> <double-mouse-4> [mwheel-scroll]
>> <help-echo> <down-mouse-5> <mouse-5> [mwheel-scroll]
>> <down-mouse-5> <mouse-5> [mwheel-scroll]
>> C-h l [view-lossage]
>
> So somehow, Emacs receives a long series of mouse wheel-scrolling
> events, perhaps due to multiple down-mouse events. And since we have
> mouse-wheel-progressive-speed, a series of such events produces
> scrolling far away.
Unfortunately, I set mouse-wheel-progressive-speed to nil a long time
ago.
> The question is where did those events come from? Is it possible that
> something is wrong with your mouse wheel or the driver?
I'd be surprised, since Emacs is the only program that I've seen this
occur in. I scroll a fair bit with the mouse wheel in Firefox and have
never seen this there.
>> P.S. Is there a way to get the event time in C-h l? If not, I think
>> there should be an option for that.
>
> How would that help? You'll most probably see very close times there.
There may have been some scroll events that occurred before I refocused
the frame that wouldn't have close times, so it might be nice to
distinguish them. I was also thinking that it might be helpful in other
bug reports involving events.
> What kind of mouse is this? Is that by any chance a mouse pad of a
> laptop?
No, just a regular desktop mouse with a scroll wheel.
next prev parent reply other threads:[~2019-04-15 17:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 17:23 bug#35246: 26.2; Mouse wheel scrolling in GTK build sometimes scrolls the entire buffer Alex Gramiak
2019-04-12 17:47 ` Eli Zaretskii
2019-04-15 16:18 ` Alex Gramiak
2019-04-15 16:35 ` Eli Zaretskii
2019-04-15 16:42 ` Eli Zaretskii
2019-04-15 17:10 ` Alex Gramiak [this message]
2019-04-15 18:49 ` Eli Zaretskii
2019-04-15 20:00 ` Alex Gramiak
2019-04-16 1:15 ` Alex Gramiak
2020-09-02 21:32 ` Stefan Kangas
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sgujjit5.fsf@gmail.com \
--to=agrambot@gmail.com \
--cc=35246@debbugs.gnu.org \
--cc=eliz@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 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).