From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: lekktu@gmail.com, 6671@debbugs.gnu.org
Subject: bug#6671: moving point and scroll-conservatively
Date: Fri, 25 Mar 2011 10:48:09 +0200 [thread overview]
Message-ID: <83mxkjtwl2.fsf@gnu.org> (raw)
In-Reply-To: <87d3lguf1j.fsf@stupidchicken.com>
> From: Chong Yidong <cyd@stupidchicken.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 6671@debbugs.gnu.org
> Date: Thu, 24 Mar 2011 22:09:28 -0400
>
> I don't think the problem is keyboard-triggered commands changing the
> buffer too fast between redisplays. I've done a bit of tracing, and
> redisplay is called once for every one, some times two, calls to
> command-execute. Certainly not the ten or twenty times that would cause
> window scrolling to fall behind.
It could easily fall behind with high enough rate of keyboard
auto-repeat operation. There are 2 possible situations: when
redisplay-dont-pause is set and when it is nil.
When redisplay-dont-pause is set, we don't check for available input
until we finish one redisplay cycle completely. When the user leans
on a key and high-rate auto-repeat is at work and, we can easily have
many keystrokes in the buffer by the time we finish a full redisplay,
especially if you have many large frames. Processing many <down>
strokes, for example, can easily get you several screenfuls away.
When redisplay-dont-pause is nil, we check for input in several places
during redisplay, and bail out if there's input. In that case, with
high-rate keyboard input, we quickly create a situation where
important data structures and flags are out of sync and cannot be
relied upon, and try_scrolling cannot be used at all, which again
means recentering (because we only try not to recenter inside
try_scrolling).
> Instead, the recentering is caused by the situation I described in an
> earlier email, where the action of fontification functions causes
> redisplay to become confused. I don't know whether there are other
> causes of anomalous recentering, but that is the only one I have
> encountered while experimenting with the code.
Try leaning on <down> in etc/HELLO, after turning off font-lock.
next prev parent reply other threads:[~2011-03-25 8:48 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 11:34 moving point and scroll-conservatively Eli Zaretskii
2010-06-26 11:52 ` Juanma Barranquero
2010-06-26 12:25 ` Eli Zaretskii
2010-06-26 13:08 ` David De La Harpe Golden
2010-06-26 14:08 ` Christoph
2010-06-26 21:25 ` Juanma Barranquero
2010-06-28 21:08 ` Juri Linkov
2010-06-26 12:44 ` David De La Harpe Golden
2010-07-19 12:48 ` Juanma Barranquero
2010-07-19 17:39 ` Eli Zaretskii
2010-07-19 20:25 ` bug#6671: " Juanma Barranquero
2010-08-02 0:29 ` Juanma Barranquero
2011-03-24 0:42 ` Chong Yidong
2011-03-24 2:07 ` Juanma Barranquero
2011-03-24 3:58 ` Chong Yidong
2011-03-24 7:23 ` Eli Zaretskii
2011-03-24 15:14 ` Chong Yidong
2011-03-24 20:01 ` Chong Yidong
2011-03-24 20:25 ` Eli Zaretskii
2011-03-24 20:57 ` Juanma Barranquero
2011-03-24 21:36 ` Chong Yidong
2011-03-25 9:13 ` Eli Zaretskii
2011-03-25 15:58 ` Chong Yidong
2011-03-24 20:56 ` Juanma Barranquero
2011-03-24 21:47 ` Chong Yidong
2011-03-24 23:06 ` Juanma Barranquero
2011-03-25 2:09 ` Chong Yidong
2011-03-25 8:48 ` Eli Zaretskii [this message]
2011-03-25 9:45 ` Eli Zaretskii
2011-03-25 11:10 ` Juanma Barranquero
2011-03-25 9:44 ` Eli Zaretskii
2011-03-25 9:32 ` Eli Zaretskii
2011-03-26 12:32 ` Eli Zaretskii
2011-03-27 2:39 ` Juanma Barranquero
2011-03-27 3:59 ` Eli Zaretskii
2011-03-28 23:00 ` Juanma Barranquero
2011-03-29 4:03 ` Eli Zaretskii
2011-03-29 10:54 ` Juanma Barranquero
2011-03-29 12:42 ` Eli Zaretskii
2011-03-31 19:19 ` Eli Zaretskii
2011-03-24 7:25 ` 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=83mxkjtwl2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=6671@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=lekktu@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 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.