unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Mickey Petersen <mickey@fyeah.org>
Cc: Eli Zaretskii <eliz@gnu.org>, 58980@debbugs.gnu.org
Subject: bug#58980: 29.0.50; Mouse wheel scroll twitches up sometimes when I scroll down
Date: Thu, 03 Nov 2022 19:07:23 +0800	[thread overview]
Message-ID: <87r0yke1p0.fsf@yahoo.com> (raw)
In-Reply-To: <4fe2bb6a-393a-7d5b-d90f-fd01e875a96a@fyeah.org> (Mickey Petersen's message of "Thu, 3 Nov 2022 09:46:46 +0000")

Mickey Petersen <mickey@fyeah.org> writes:

> I _do_, however, have a way that seems to reproduce the issue: when I
> scroll an inactive window and then go back to scrolling the active
> window the bug manifests itself more easily:
>
> 1. Ensure there are two windows minimum.

Windows, or frames?

> Seems there's some stateful behaviour that does or does not get
> carried over when the 'hovered window scroll' changes?

No, that shouldn't be it.  Emacs tracks scroll valuators on a
display-local basis, but only gets motion events for the valuator when
the mouse pointer is inside a frame.  As a result, scroll valuators are
reset upon crossing events, as by the time an XI_Enter event arrives,
the stored value can no longer be trusted.

So please answer the question above.





  parent reply	other threads:[~2022-11-03 11:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 16:20 bug#58980: 29.0.50; Mouse wheel scroll twitches up sometimes when I scroll down Mickey Petersen
2022-11-03  8:31 ` Eli Zaretskii
2022-11-03  9:46   ` Mickey Petersen
2022-11-03 10:04     ` Eli Zaretskii
2022-11-03 11:07     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
     [not found]       ` <0eece511-bacd-2d16-107b-9b9251cc8236@fyeah.org>
     [not found]         ` <87eduke019.fsf@yahoo.com>
     [not found]           ` <af233f63-79d3-2125-9a78-91ef30f55128@fyeah.org>
     [not found]             ` <87y1ssckpe.fsf@yahoo.com>
     [not found]               ` <561adb8a-2f09-9bbd-1c9a-d99098613ed9@fyeah.org>
     [not found]                 ` <87tu3gci00.fsf@yahoo.com>
     [not found]                   ` <138ccba0-9bc5-ad23-c103-fd118caf73ff@fyeah.org>
     [not found]                     ` <87pme3d0mh.fsf@yahoo.com>
     [not found]                       ` <6980406f-2807-1b7b-86e9-6a0e1b4cc470@fyeah.org>
2022-11-04 11:22                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-04 11:28                           ` Mickey Petersen
2022-11-04 11:30                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-04 11:31                               ` Mickey Petersen
2022-11-03 11:05   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87r0yke1p0.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=58980@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=mickey@fyeah.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).