From: Eli Zaretskii <eliz@gnu.org>
To: Alex Gramiak <agrambot@gmail.com>
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 21:49:02 +0300 [thread overview]
Message-ID: <83wojvgl41.fsf@gnu.org> (raw)
In-Reply-To: <87sgujjit5.fsf@gmail.com> (message from Alex Gramiak on Mon, 15 Apr 2019 11:10:30 -0600)
> From: Alex Gramiak <agrambot@gmail.com>
> Cc: 35246@debbugs.gnu.org
> Date: Mon, 15 Apr 2019 11:10:30 -0600
>
> > 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.
So you did actually scroll the wheel when this happened in Emacs, just
not that much? I thought these scroll events were unrelated to what
you did at the time. If you did use the mouse when that happened, can
you describe what you did with it?
> >> 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 don't understand: before you refocus the frame, the scroll events
are not delivered to Emacs, they are delivered to the frame or window
that has focus. Right?
next prev parent reply other threads:[~2019-04-15 18:49 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
2019-04-15 18:49 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wojvgl41.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35246@debbugs.gnu.org \
--cc=agrambot@gmail.com \
/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.