From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
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 15:36:54 +0300 [thread overview]
Message-ID: <83k06z87bt.fsf@gnu.org> (raw)
In-Reply-To: <m2v8qjb1fk.fsf@Mini.fritz.box> (message from Gerd Möllmann on Tue, 23 Aug 2022 14:15:59 +0200)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: 57349@debbugs.gnu.org
> Date: Tue, 23 Aug 2022 14:15:59 +0200
>
> >> or sometimes errors 'Wrong type argument: integer-or-marker-p, nil'.
> >
> > This shouldn't happen, indeed.
> >
> >> Not sure what to make of this. Looks like posn-at-x-y returns a posn
> >> with a nil point? Or maybe posn-point returns nil?
> >
> > Either this should be fixed, or the code should be prepared for nil in
> > this case.
>
> Yup.
>
> 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 don't think it's reasonable to expect that posn-WHATEVER functions
will always return a valid buffer position. There are parts on the
window/frame decorations where no buffer position makes sense. We
sometimes forcibly put some close position there, or get it as a side
effect of the implementation, but I don't think we should rely on it.
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
2022-08-23 12:46 ` Eli Zaretskii
2022-08-23 13:59 ` Gerd Möllmann
2022-08-23 12:36 ` Eli Zaretskii [this message]
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=83k06z87bt.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57349@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.com \
/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).