From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#61307: 30.0.50; pixel-scroll-precision-mode: window-scroll-functions? Date: Wed, 15 Feb 2023 15:21:17 +0200 Message-ID: <83y1ozawtu.fsf@gnu.org> 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> <87sff7374b.fsf@web.de> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40099"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 61307@debbugs.gnu.org To: Michael Heerdegen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Feb 15 14:22:14 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 1pSHji-000AHl-6G for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 15 Feb 2023 14:22:14 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pSHjY-0007LS-9A; Wed, 15 Feb 2023 08:22:04 -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 1pSHjW-0007LI-K2 for bug-gnu-emacs@gnu.org; Wed, 15 Feb 2023 08:22:02 -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 1pSHjW-00053o-Ah for bug-gnu-emacs@gnu.org; Wed, 15 Feb 2023 08:22:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pSHjW-0000Ps-6U for bug-gnu-emacs@gnu.org; Wed, 15 Feb 2023 08:22:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 15 Feb 2023 13:22:02 +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.16764673061573 (code B ref 61307); Wed, 15 Feb 2023 13:22:02 +0000 Original-Received: (at 61307) by debbugs.gnu.org; 15 Feb 2023 13:21:46 +0000 Original-Received: from localhost ([127.0.0.1]:58211 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pSHjG-0000PI-BK for submit@debbugs.gnu.org; Wed, 15 Feb 2023 08:21:46 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:45788) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pSHjC-0000Ok-0I for 61307@debbugs.gnu.org; Wed, 15 Feb 2023 08:21:44 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pSHj6-0004L8-IE; Wed, 15 Feb 2023 08:21:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=wxbTf+3yuOJRZAiAwt+d3l4s8ng+OTpy9RsZYIGcTGg=; b=pGh3VW/nBmLK WIvIqZXu9ywspteeteWdSft7TIi6O8vxMRa+sOANcrAKR4YjHmxXPvet3LDVjSgLPSvSwqLgMkNyz MQQ1wYoJVzPZPvIMwXWC9QCEp3iQqyIF6k9Ep96bb1D5W+dKRuFN3TfVELU5wvX0/9bh6+S7BnaU7 Mi2NoDigdygU9dkK8L329/Rle7PoEhhkUbw/T2QSs38Za3YqtZi08iCk+0rINJtZairs7jsn5L5Qv ii2FWluAKeI9l2rj9ogdnPWxA41WyJb8QijHHFln8Fq7xHOBnAV+/NUUd6X4RWGEBrC5TBXThf2Uf xWF5ZaUQmVPxtw/JvIK0jw==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pSHj5-0003Ae-VA; Wed, 15 Feb 2023 08:21:36 -0500 In-Reply-To: <87sff7374b.fsf@web.de> (message from Michael Heerdegen on Wed, 15 Feb 2023 05:06:12 +0100) 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:255694 Archived-At: > From: Michael Heerdegen > Cc: 61307@debbugs.gnu.org > Date: Wed, 15 Feb 2023 05:06:12 +0100 > > 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. I hoped you will answer the specific questions I asked, quoted above. But since you don't have a device to actually observe pixel-scroll-precision-mode on your system, something I didn't know until now, I guess you cannot answer them? (I also don't have access to a suitable system, otherwise I wouldn't have bothered you with the questions.) > But I understand that what I see when scrolling with a normal wheel > mouse is only one case we need to handle. Right. Though on such a system, we should probably call window-scroll-functions every scroll. > AFAIU, scrolling by > dragging the vertical scroll bar is not handled by precision scrolling. Correct. > 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. Yes, capable mice (which also require a capable system to support them), and touch pads. > Or would you suggest to call the window-scroll functions just after a > certain time limit? I don't think a timer would be appropriate here. > 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). Not necessarily. To see a similar situation, disable image-auto-resize mode, visit a large image, and scroll with C-n or C-p: you won't see window-scroll-functions called at all. That's basically what pixel-scroll-precision-mode works: it uses the window's vscroll, like we do with tall images.