GNU bug report logs - #57349
29.0.50; pixel-scroll-precision-mode. error integer-or-marker-p nil

Previous Next

Full log

Message #29 received at 57349 <at> debbugs.gnu.org (full text, mbox):

From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 57349 <at> debbugs.gnu.org
Subject: Re: bug#57349: 29.0.50; pixel-scroll-precision-mode. error
 integer-or-marker-p nil
Date: Tue, 23 Aug 2022 14:36:52 +0200

Gerd Möllmann <gerd.moellmann <at> gmail.com> writes:

> I could add a check in the function that does the (goto-char nil), but I
> don't know if that would be only fixing a symptom of something else.

I just had an idea.  What if this deoends on the mini-window.  One of
the functions signalling looks like this:

(defun pixel-scroll-precision-scroll-up-page (delta)
  "Scroll the current window up by DELTA pixels.
Note that this function doesn't work if DELTA is larger than
the height of the current window."
  (let* ((edges (window-edges nil t nil t))
         (max-y (- (nth 3 edges)
                   (nth 1 edges)))
         (usable-height max-y)
         (posn (posn-at-x-y 0 (+ (window-tab-line-height)
                                 (window-header-line-height)
                                 (- max-y delta))))
         (point (posn-point posn))
         (up-point (save-excursion
                     (goto-char point)
                     ^^^ here point is nil
                     (vertical-motion (- (1+ scroll-margin)))
                     (point))))

The documentation of window-edges says it is using the selected window
when its window argument is nil.  The selected window can't be the
mini-window unless the minibuffer is active.

And indeed, when I enter the minibuffer (M-:), and mouse-wheel as
descibed before, no error occurs.

Does that sound plausible?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.