From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#29325: 26.0.90: Info scrolling stuck Date: Sun, 19 Nov 2017 19:12:00 +0200 Message-ID: <83r2sudwgv.fsf@gnu.org> References: <83fu9ehuog.fsf@gnu.org> <83d14hidlk.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1511111595 6930 195.159.176.226 (19 Nov 2017 17:13:15 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 19 Nov 2017 17:13:15 +0000 (UTC) Cc: 29325@debbugs.gnu.org To: charles@aurox.ch (Charles A. Roelli) Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Nov 19 18:13:10 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eGT9W-0001BK-HV for geb-bug-gnu-emacs@m.gmane.org; Sun, 19 Nov 2017 18:13:06 +0100 Original-Received: from localhost ([::1]:53787 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eGT9d-0004lq-VN for geb-bug-gnu-emacs@m.gmane.org; Sun, 19 Nov 2017 12:13:13 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56130) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eGT9W-0004kq-9V for bug-gnu-emacs@gnu.org; Sun, 19 Nov 2017 12:13:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eGT9S-0006Np-8k for bug-gnu-emacs@gnu.org; Sun, 19 Nov 2017 12:13:06 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:39062) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eGT9S-0006Nc-4n for bug-gnu-emacs@gnu.org; Sun, 19 Nov 2017 12:13:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eGT9R-0005CK-Tu for bug-gnu-emacs@gnu.org; Sun, 19 Nov 2017 12:13:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 19 Nov 2017 17:13:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 29325 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 29325-submit@debbugs.gnu.org id=B29325.151111154219935 (code B ref 29325); Sun, 19 Nov 2017 17:13:01 +0000 Original-Received: (at 29325) by debbugs.gnu.org; 19 Nov 2017 17:12:22 +0000 Original-Received: from localhost ([127.0.0.1]:47743 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eGT8o-0005BT-2K for submit@debbugs.gnu.org; Sun, 19 Nov 2017 12:12:22 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:36642) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eGT8m-0005BG-58 for 29325@debbugs.gnu.org; Sun, 19 Nov 2017 12:12:20 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eGT8c-000652-GG for 29325@debbugs.gnu.org; Sun, 19 Nov 2017 12:12:15 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:51260) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eGT8c-00064y-Cs; Sun, 19 Nov 2017 12:12:10 -0500 Original-Received: from [176.228.60.248] (port=2107 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1eGT8b-0006pq-Qr; Sun, 19 Nov 2017 12:12:10 -0500 In-reply-to: (charles@aurox.ch) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 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.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:140103 Archived-At: > Date: Sun, 19 Nov 2017 17:49:50 +0100 > From: charles@aurox.ch (Charles A. Roelli) > CC: 29325@debbugs.gnu.org > > > Still not reproducible. > > > > Does the same problem happen if you scroll with "M-1 M-v" instead of > > the mouse wheel? > > No: it works fine in that case. If this is only about scrolling with the mouse wheel, then perhaps the factor which differs between our systems is the amount of scrolling per wheel notch. How many lines does a single notch scroll in your case? And does the problem happen if you turn the wheel slowly? > > (cond ((eq button mouse-wheel-down-event) > > (condition-case nil (funcall mwheel-scroll-down-function amt) > > ;; Make sure we do indeed scroll to the beginning of > > ;; the buffer. > > (beginning-of-buffer > > (unwind-protect > > (funcall mwheel-scroll-down-function) > > ;; If the first scroll succeeded, then some scrolling > > ;; is possible: keep scrolling til the beginning but > > ;; do not signal an error. For some reason, we have > > ;; to do it even if the first scroll signaled an > > ;; error, because otherwise the window is recentered > > ;; for a reason that escapes me. This problem seems > > ;; to only affect scroll-down. --Stef > > (set-window-start (selected-window) (point-min)))))) > > That is, when attempting to scroll down (as in, moving towards > beginning of buffer) under some mysterious circumstances, the window > gets recentered around point instead of being scrolled. However, if > point is moved to the first line of the window, say, then the > scrolling does work as expected (as I've found out by experimenting > more with my initial recipe). I have serious difficulties dealing with unexplained and undescribed problems that happen "under mysterious circumstances". If you build with --enable-checking='yes,glyphs', and then turn on redisplay tracing with "M-x trace-redisplay" before scrolling with the wheel, what do you see? And how does that trace differ from when you scroll with "M-1 M-v"? (I find it useful to disable blink-cursor-mode and global-eldoc-mode before such experiments, because they tend to trigger extra redisplay cycles that conceal the interesting parts.)