all messages for Emacs-related lists mirrored at yhetil.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: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Eli Zaretskii <eliz@gnu.org>, 61307@debbugs.gnu.org
Subject: bug#61307: 30.0.50; pixel-scroll-precision-mode: window-scroll-functions?
Date: Sun, 19 Feb 2023 16:30:15 +0800	[thread overview]
Message-ID: <871qmmjbvs.fsf@yahoo.com> (raw)
In-Reply-To: <87a61axg1i.fsf@web.de> (Michael Heerdegen's message of "Sun, 19 Feb 2023 08:36:41 +0100")

Michael Heerdegen <michael_heerdegen@web.de> writes:

> That is also my question!

I suggest adding a new counter to the kinetic state which counts the
number of pixels scrolled, taking into account the direction of the
scroll.  Then, once (abs counter) exceeds the line height, run
window-scroll-functions.

Alternatively, do that every time set-window-start is called.

>> Either way, please make sure it stays fast (or at least put it behind an
>> option which is off by default.)
>
> How can I be sure it stays fast?  It's obviously the right thing for my
> setup, but I have _zero_ experience with other setups (devices).  If you
> have, help would be very appreciated.

I'd recommend asking people to try it, especially with editing modes
that have lots of gizmos (``lsp-ui'' seems to be one of those, whatever
it is.)





  reply	other threads:[~2023-02-19  8:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06  1:49 bug#61307: 30.0.50; pixel-scroll-precision-mode: window-scroll-functions? Michael Heerdegen
2023-02-06 12:15 ` Eli Zaretskii
2023-02-06 21:30   ` Michael Heerdegen
2023-02-12 12:15     ` Eli Zaretskii
2023-02-13  2:20       ` Michael Heerdegen
2023-02-13  3:31         ` Eli Zaretskii
2023-02-13  3:44           ` Michael Heerdegen
2023-02-13 12:56             ` Eli Zaretskii
2023-02-14  1:30               ` Michael Heerdegen
2023-02-14 13:06                 ` Eli Zaretskii
2023-02-15  4:06                   ` Michael Heerdegen
2023-02-15 13:21                     ` Eli Zaretskii
2023-02-16  4:57                       ` Michael Heerdegen
2023-02-16  8:22                         ` Eli Zaretskii
2023-02-16  8:47                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-16  8:54                           ` Michael Heerdegen
2023-02-19  5:50                           ` Michael Heerdegen
2023-02-19  6:54                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-19  7:36                               ` Michael Heerdegen
2023-02-19  8:30                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-02-06 14:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-06 15:25   ` 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=871qmmjbvs.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=61307@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=michael_heerdegen@web.de \
    /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.