unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 6671@debbugs.gnu.org
Subject: bug#6671: moving point and scroll-conservatively
Date: Fri, 25 Mar 2011 00:06:00 +0100	[thread overview]
Message-ID: <AANLkTink-X3fCDb8m+-KAT8HzGeUYta20KUDN4+h+jj3@mail.gmail.com> (raw)
In-Reply-To: <87ei5wdwce.fsf@stupidchicken.com>

On Thu, Mar 24, 2011 at 22:47, Chong Yidong <cyd@stupidchicken.com> wrote:

> This means that any time point moves below the bottom of the window, the
> resulting scroll will leave the cursor at the bottom of the window.  Any
> time point moves above the top of the window, the resulting scroll will
> leave the cursor at the top of the window.  Unlike numerical values of
> scroll-conservatively, there is no "scrolling limit" to check.

In other words, `scroll-conservatively' set to t means "scroll
line-by-line", or "scroll but never recenter". I'm OK with that (well,
I'm much more than OK; that's what I consider the only sane behavior
of scrolling, and what many other text editors do, though I readily
admit that most Emacs users seem to prefer the recentering behavior).

But the trick is making it fast enough, isn't? IIRC, the current
sluggish performance and some other changes were brought in to cope
with redisplay pausing for a while and then suddenly "jumping ahead"
in the buffer because it wasn't fast enough to keep up with typematic
repeat during scrolling (pre-Unicode2 merge it always was,
post-Unicode2 scrolling line-by-line is jumpy the best of days,
specially when moving up the beginning of the buffer).

    Juanma





  reply	other threads:[~2011-03-24 23:06 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <83pqzec9i8.fsf@gnu.org>
2010-07-19 20:25 ` bug#6671: moving point and scroll-conservatively 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 [this message]
2011-03-25  2:09                     ` Chong Yidong
2011-03-25  8:48                       ` Eli Zaretskii
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

  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=AANLkTink-X3fCDb8m+-KAT8HzGeUYta20KUDN4+h+jj3@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=6671@debbugs.gnu.org \
    --cc=cyd@stupidchicken.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).