unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: charles@aurox.ch (Charles A. Roelli)
Cc: 29325@debbugs.gnu.org
Subject: bug#29325: 26.0.90: Info scrolling stuck
Date: Mon, 20 Nov 2017 22:25:33 +0200	[thread overview]
Message-ID: <83r2ssd7eq.fsf@gnu.org> (raw)
In-Reply-To: <m260a4wwvs.fsf@aurox.ch> (charles@aurox.ch)

> Date: Mon, 20 Nov 2017 20:52:39 +0100
> From: charles@aurox.ch (Charles A. Roelli)
> CC: 29325@debbugs.gnu.org
> 
> I don't have access to a GNU/Linux system at the moment, but if I
> recall correctly, it would be 5 lines at a time, when scrolling
> slowly.

Then I'd expect the same behavior to happen if you do "M-5 M-v"
instead of turning the wheel.  Does it?

If M-v doesn't reproduce the problem, then what about removing the
tricky code, and leaving just

  (funcall mwheel-scroll-down-function amt)

without all the rest?  I cannot understand why we need the rest, maybe
I'm missing something.  mwheel-scroll-down-function is by default
scroll-down, exactly the same function called by M-v, so the results
should be the same, assuming that 'amt' is 5 when turning the wheel.

> The behavior is different depending on how fast the mouse wheel is
> turned.  If it is turned slowly several times in a row, it is possible
> to make window-start reach as far as the second or third line of the
> buffer.  If you turn it once more, then window-start jerks down a few
> lines instead of reaching the start of the buffer.  This can be
> repeated ad infinitum.
> 
> In contrast, when turning the mouse wheel quickly (a few notches in
> one second), it is not possible to get window-start anywhere near the
> start of the buffer, except by using non-mouse commands or by setting
> point closer to the top of the window first (with the mouse).

Just to make sure we are not barking up the wrong tree: this is in
"emacs -Q" with no customizations of any scroll-related variables,
like scroll-margin, scroll-conservatively, etc., right?





  reply	other threads:[~2017-11-20 20:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-16 19:41 bug#29325: 26.0.90: Info scrolling stuck Charles A. Roelli
2017-11-16 19:47 ` Eli Zaretskii
2017-11-16 20:45   ` Charles A. Roelli
2017-11-17  7:11     ` Eli Zaretskii
2017-11-19 16:49       ` Charles A. Roelli
2017-11-19 17:12         ` Eli Zaretskii
2017-11-20 19:52           ` Charles A. Roelli
2017-11-20 20:25             ` Eli Zaretskii [this message]
2017-11-21 19:24               ` Charles A. Roelli
2017-11-21 19:42                 ` Eli Zaretskii
2017-11-21 19:58                   ` Eli Zaretskii
2017-11-22 15:38                   ` Eli Zaretskii
2017-11-22 19:04                     ` Charles A. Roelli
2017-11-23 20:08                     ` Charles A. Roelli
2017-11-23 20:31                       ` Eli Zaretskii
2017-11-22 18:56                   ` Charles A. Roelli
     [not found] <<m2efoyvwoa.fsf@aurox.ch>
2017-11-16 22:35 ` Drew Adams

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=83r2ssd7eq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=29325@debbugs.gnu.org \
    --cc=charles@aurox.ch \
    /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).