From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Michael Heerdegen Newsgroups: gmane.emacs.bugs Subject: bug#61307: 30.0.50; pixel-scroll-precision-mode: window-scroll-functions? Date: Wed, 15 Feb 2023 05:06:12 +0100 Message-ID: <87sff7374b.fsf@web.de> References: <87y1pbsgu5.fsf@web.de> <83h6vzq9at.fsf@gnu.org> <878rhascr8.fsf@web.de> <83wn4ngjvp.fsf@gnu.org> <875yc6cnmk.fsf@web.de> <83mt5ifdhn.fsf@gnu.org> <87o7pyb556.fsf@web.de> <83k00lg1ve.fsf@gnu.org> <873579jaot.fsf@web.de> <83edqse6qr.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26240"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: 61307@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Feb 15 05:07:38 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pS94y-0006Yb-LU for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 15 Feb 2023 05:07:36 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pS94a-0001HL-7i; Tue, 14 Feb 2023 23:07:12 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pS94Q-0001Dx-F9 for bug-gnu-emacs@gnu.org; Tue, 14 Feb 2023 23:07:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pS94Q-00078U-6j for bug-gnu-emacs@gnu.org; Tue, 14 Feb 2023 23:07:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pS94P-0005NV-My for bug-gnu-emacs@gnu.org; Tue, 14 Feb 2023 23:07:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Michael Heerdegen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 15 Feb 2023 04:07:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 61307 X-GNU-PR-Package: emacs Original-Received: via spool by 61307-submit@debbugs.gnu.org id=B61307.167643398420618 (code B ref 61307); Wed, 15 Feb 2023 04:07:01 +0000 Original-Received: (at 61307) by debbugs.gnu.org; 15 Feb 2023 04:06:24 +0000 Original-Received: from localhost ([127.0.0.1]:57526 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pS93n-0005MU-VU for submit@debbugs.gnu.org; Tue, 14 Feb 2023 23:06:24 -0500 Original-Received: from mout.web.de ([212.227.15.4]:54205) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pS93m-0005ME-E5 for 61307@debbugs.gnu.org; Tue, 14 Feb 2023 23:06:23 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=s29768273; t=1676433975; bh=72toS6LlozdqQiIAzpkJDV/h00lc5iKyastr0Ows5rc=; h=X-UI-Sender-Class:From:To:Cc:Subject:In-Reply-To:References:Date; b=rVb/i2pQUixREcxDGDeyq7YsNnQ4NmQnHgalc7KLUtzWGWfTymFiuFu+Ga9Zvzl4D bteF2yW/cO2O1ynXepgeM0FLI2Hp3PnlMcekKAZilvYITtYSFK3fM+DxFp6K1UxMRV GleaS0IJ0Dsx+daQT6SIK4l0atLd8M0BVfhxtQPTzmon78wMWGXv8/NiXM9LluTImK yXgmkp19DLQsborUyVuCJgHNLjAwGRdlOLbttbYaF+v8wtNnqMi9Lb0ZK3u408vJ7U 5ZRl8bJseZcq3f5XXcA9oaSih8iWK5t/yjtrDQoRnihWVxCSo57Fm4k48LzM9L7v+E vcRYBTvmdqRzQ== X-UI-Sender-Class: 814a7b36-bfc1-4dae-8640-3722d8ec6cd6 Original-Received: from drachen.dragon ([84.59.210.57]) by smtp.web.de (mrweb005 [213.165.67.108]) with ESMTPSA (Nemesis) id 1MALiZ-1pHzm01yLj-00Br0q; Wed, 15 Feb 2023 05:06:15 +0100 In-Reply-To: <83edqse6qr.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 14 Feb 2023 15:06:36 +0200") X-Provags-ID: V03:K1:x3xlVKVPr96MYNVbktfY02NEaSmX9aLeaIV95KzslI0x8bGawU4 2g6G1VZzhej88pLowihxMXdyQ/JOxDbqaVhHrk7Md7vCAVIB6fwCcE5JGgn7ZtBKtuYAjdy ZvZb4g81mJfknqgLnc9DZeLOO/JJa4+DV0kVQwMUks+crn8L6PT3eRyrrUQTIZ4ho/nGqoK DFDQn29IElJn6tqSN7D4g== UI-OutboundReport: notjunk:1;M01:P0:MLQXguzzdsk=;bXdswnsFYAOnCylbJjmFHfMQGPE JwwPhPiRhvikV5USA86gwXtSAmT98SpS45ZOVrwXQ/aqK03pMs49l+OnIP10JtIwh1gJY/CQZ mTMYBaqjfMV/VqAD+Idgu90ktrEhjAqkhsOu/Gz5bXWJKjkUrdNAHY1P3Mc+iXMRylq1quOeZ gj+Y8okXitRh3/QiC2sbUxk+ADOh3XRd/wnqNEmo/HoLTBB/QUIrgS0lDhd+KN2hj3Rg25sSF 81e1MwrxiaS1Fqh4FRsV2MWnpeep6U/iF6Q/QpyuGTUbupOnmqcJ2t5NdLQfWy/h+OqZtrE6U YV/+bsFOmlMtPLqad0y3P1ObrzNEsS5ROa7GU4cbjIdARvZJHG9gYdy2JJ4pVznX3FooUm0rO IfQ+yrDb2070cG32EEgwOPT7OJSDW8juUM+pphnH6P4NEuyRjme7KKIKWD/pwmfLy58J3EQva JwV2i8BxXasP3AoeHrTpWm8uENcApcsAgVnJ7WeVIXycvC5RiM49EYcKIUAAYs+EQL9y1dH0Z bUHV5v1LAsLH6DDE5zYdnwkc9ia+uhPeo5jg0nILIqFn762GH3iqga3kxg7/LNYap67Ze8/0Q 8+I/SuVW7CnO1fW7wf9SObCjI78EDrS5wZRNyLH/HQFIIwTUkydsyUvk1PWKP6LMFVt463MhB 77C8ViOc9kNtZmc/bykpd9RbCkwXZjG+dBZypQRcfHHNkqkEDGMU5lUKYreeuD/28ytzlzvEi LIJ7abkf5icTOn9Fw4oBZHFW72QNseVAgBLIFNf6QWyO9uNOBDQrohpx4n2m0GufGa7Axjef X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:255662 Archived-At: Eli Zaretskii writes: > > I don't see the hook called for each pixel. What do you mean? > > Each time you do the smallest possible scroll, by how many pixels, or > by what fraction of the screen-line's height does Emacs scroll the > window? IOW, by how many pixels is the display scrolled for each call > to window-scroll-functions? > > Precision pixel-scrolling supports many different devices (mice and > touch-pads), which can scroll at very different resolutions. The > possibility that window-scroll-functions be called too frequently > depends on what exactly do your device and your Emacs build support in > this scenario, and I don't yet have a clear idea about that, since you > didn't tell. I feel a bit lost. What should I tell? I have no idea what I could know about this that you don't already know. But I understand that what I see when scrolling with a normal wheel mouse is only one case we need to handle. AFAIU, scrolling by dragging the vertical scroll bar is not handled by precision scrolling. So we speak about touch events (although `pixel-scroll-precision-mode-map' only binds , but that event may also be generated very often) and mice with a more or less continuous scroll wheel (or ball) and such things. I don't have access to such a device and really feel uncomfortable to suggest a patch for these cases I must admit. Or would you suggest to call the window-scroll functions just after a certain time limit? A pixel-delta limit would probably not be sufficient, since we want to call the functions also for small scroll amounts if they are not directly followed by another scroll (I guess). So do we just want to use a timer for this? Or use a combination of those approaches (scrolling farther than a certain amount fires the scroll functions immediately, but also small amounts call them if the user doesn't scroll after delta more milliseconds)? Michael.