From: Eli Zaretskii <eliz@gnu.org>
To: Valentin Ignatyev <valentjedi@gmail.com>,
Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>
Cc: 29737@debbugs.gnu.org
Subject: bug#29737: 27.0.50; pixel-scroll-mode is laggy
Date: Sat, 16 Dec 2017 21:33:45 +0200 [thread overview]
Message-ID: <83shcaqxgm.fsf@gnu.org> (raw)
In-Reply-To: <CAO90aWvmqMg=wkt4YyqE8kDP_BNZjAih7AEdyP-Zt74OydpUHA@mail.gmail.com> (message from Valentin Ignatyev on Sun, 17 Dec 2017 04:52:51 +1000)
Please always CC the bug address.
> From: Valentin Ignatyev <valentjedi@gmail.com>
> Date: Sun, 17 Dec 2017 04:52:51 +1000
>
> Hi again Eli! Thanks for the fast response!
> It happens in all major modes I've tried it (org-mode, python-mode, and web-mode).
> It still happens in the fundamental mode as well (tried to scroll emacs-news in fundamental mode). Setting
> mouse-wheel-progressive-speed to nil seems to have no effect or very little effect that I can't notice.
> Scrolling with a Ctrl key is much smoother yet not lagless (it also loads CPU in about 50% or so). And it's
> looks like line-wise, not pixel-wise ;)
>
> Just to mention, I've tried your suggestions without any additional elisp (e.g with -Q flag).
CC'ing Tak, who wrote this mode. Tak, would you please look into
this?
next prev parent reply other threads:[~2017-12-16 19:33 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 [this message]
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
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=83shcaqxgm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29737@debbugs.gnu.org \
--cc=tkk@misasa.okayama-u.ac.jp \
--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.