all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 66769@debbugs.gnu.org, aaronjensen@gmail.com
Subject: bug#66769: 30.0.50; pixel-scroll-precision-mode and scroll-margin regression
Date: Sat, 28 Oct 2023 09:43:19 +0300	[thread overview]
Message-ID: <83wmv7ckmw.fsf@gnu.org> (raw)
In-Reply-To: <877cn7xzg0.fsf@yahoo.com> (bug-gnu-emacs@gnu.org)

> Cc: 66769@debbugs.gnu.org
> Date: Sat, 28 Oct 2023 10:17:51 +0800
> From:  Po Lu via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> Aaron Jensen <aaronjensen@gmail.com> writes:
> 
> > Commit 1da4fca0647ebf1d5d6f12817301a17661560810 caused a regression of
> > bug#52231
> >
> > The repro is the same:
> >
> > (progn (setq scroll-margin 4)
> >        (pixel-scroll-precision-mode))
> >
> > And scroll down a buffer with mouse wheel.
> >
> > The buffer does not scroll properly, it jumps back unless you scroll
> > fast enough.
> 
> Hmm, I'm not certain what the solution to this should be.
> 
> For images to scroll properly, the "target point" must be derived from
> whether the point is visible after scrolling, instead of outside a set
> number of rows from the window start or end.  Yet the latter information
> is mandatory if the scroll margin is to be taken into account, and no
> function supplies both besides posn-at-point, which is much too slow.

What is the "target point" in the above text? target for what?

> The immediate remedy is to restore the old code when scroll-margin is in
> effect and document the consequent incapacity to scroll over large
> images as an unfortunate corollary.  Is that acceptable by you?

Why not use the too-slow posn-at-point, but only in this case?





  reply	other threads:[~2023-10-28  6:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27  5:00 bug#66769: 30.0.50; pixel-scroll-precision-mode and scroll-margin regression Aaron Jensen
2023-10-28  2:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-28  6:43   ` Eli Zaretskii [this message]
2023-10-28  7:35     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-28  8:29       ` Eli Zaretskii
2023-10-28  8:34         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-28  8:42           ` Eli Zaretskii
2023-10-28 12:33             ` Aaron Jensen
2023-10-28 12:54               ` Eli Zaretskii
2023-11-02  5:49   ` Aaron Jensen
2023-11-02  6:16     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-02  6:28     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83wmv7ckmw.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=66769@debbugs.gnu.org \
    --cc=aaronjensen@gmail.com \
    --cc=luangruo@yahoo.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.