From: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>
To: eliz@gnu.org
Cc: tkk@misasa.okayama-u.ac.jp, valentjedi@gmail.com, 29737@debbugs.gnu.org
Subject: bug#29737: 27.0.50; pixel-scroll-mode is laggy
Date: Sun, 07 Jan 2018 11:06:26 +0900 (JST) [thread overview]
Message-ID: <20180107.110626.867464466770164046.tkk@misasa.okayama-u.ac.jp> (raw)
In-Reply-To: <83y3la993c.fsf@gnu.org>
>> Date: Mon, 01 Jan 2018 09:58:38 +0900 (JST)
>> Cc: eliz@gnu.org, 29737@debbugs.gnu.org, tkk@misasa.okayama-u.ac.jp
>> From: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>
>>
>> I think that on scrolling of 1000 lines, smooth scroll is not
>> necessary. User wants smooth scrolling only for the first spin of
>> mouse wheel.
>>
>> This patch introduces a new variable `pixel-dead-time' and
>> `pixel-last-scroll-time'. When another scroll request was delivered
>> within `pixel-dead-time', very likely user does not want smooth
>> scrolling.
>>
>> On such situation, `scroll-down' is called instead of
>> `pixel-scroll-pixel-down'. On theory there should not be lag because
>> of smoothing.
>>
>> I tested the revised pixel-scroll-mode for a week and confirmed that
>> works good. When `pixel-dead-time' is zero, its behavior is the same
>> as before. I think `pixel-dead-time' 0.1 works better.
>>
>> I'm sending ChangeLog and a patch relative to the current master.
>
> There was no response, but do you think we should push this
> regardless? (It should go to the release branch, not to master.)
I think I understood what the laggy meant. The laggy scroll is slow
scroll with too frequent redisplay. If my understanding is correct, I
am sure this patch fixes the laggy problem.
I think it is good to avoid the laggy situation. Thus I think, to
push this patch to the release branch is a good idea.
next prev parent reply other threads:[~2018-01-07 2:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 17:55 bug#29737: 27.0.50; pixel-scroll-mode is laggy Valentin Ignatyev
2017-12-16 18:30 ` Eli Zaretskii
[not found] ` <CAO90aWvmqMg=wkt4YyqE8kDP_BNZjAih7AEdyP-Zt74OydpUHA@mail.gmail.com>
2017-12-16 19:33 ` Eli Zaretskii
2017-12-16 19:35 ` Valentin Ignatyev
2017-12-17 2:00 ` Tak Kunihiro
2017-12-22 10:22 ` Eli Zaretskii
2017-12-23 3:18 ` Tak Kunihiro
2017-12-23 9:20 ` Eli Zaretskii
2017-12-23 11:30 ` Valentin Ignatyev
2017-12-23 11:53 ` Valentin Ignatyev
2017-12-24 2:28 ` Tak Kunihiro
2017-12-24 5:18 ` Valentin Ignatyev
2017-12-25 3:48 ` Tak Kunihiro
2018-01-01 0:58 ` Tak Kunihiro
2018-01-06 17:43 ` Eli Zaretskii
2018-01-07 2:06 ` Tak Kunihiro [this message]
2018-01-07 7:19 ` Eli Zaretskii
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=20180107.110626.867464466770164046.tkk@misasa.okayama-u.ac.jp \
--to=tkk@misasa.okayama-u.ac.jp \
--cc=29737@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=valentjedi@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.