From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 57349@debbugs.gnu.org
Subject: bug#57349: 29.0.50; pixel-scroll-precision-mode. error integer-or-marker-p nil
Date: Tue, 23 Aug 2022 14:36:52 +0200 [thread overview]
Message-ID: <m2o7wbb0gr.fsf@Mini.fritz.box> (raw)
In-Reply-To: <m2v8qjb1fk.fsf@Mini.fritz.box> ("Gerd Möllmann"'s message of "Tue, 23 Aug 2022 14:15:59 +0200")
Gerd Möllmann <gerd.moellmann@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?
next prev parent reply other threads:[~2022-08-23 12:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 6:12 bug#57349: 29.0.50; pixel-scroll-precision-mode. error integer-or-marker-p nil Gerd Möllmann
2022-08-23 7:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-23 9:03 ` Gerd Möllmann
2022-08-23 11:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-23 12:17 ` Gerd Möllmann
2022-08-23 11:57 ` Eli Zaretskii
2022-08-23 12:15 ` Gerd Möllmann
2022-08-23 12:36 ` Gerd Möllmann [this message]
2022-08-23 12:46 ` Eli Zaretskii
2022-08-23 13:59 ` Gerd Möllmann
2022-08-23 12:36 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2o7wbb0gr.fsf@Mini.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=57349@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).