From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: cyd@stupidchicken.com, 6671@debbugs.gnu.org
Subject: bug#6671: moving point and scroll-conservatively
Date: Sun, 27 Mar 2011 05:59:49 +0200 [thread overview]
Message-ID: <83ipv5rz62.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTimJLH=7MKo6WhSJ9ho-7-KHjCFDRXZ1NEZBYyTb@mail.gmail.com>
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Sun, 27 Mar 2011 04:39:36 +0200
> Cc: Chong Yidong <cyd@stupidchicken.com>, 6671@debbugs.gnu.org
>
> On Sat, Mar 26, 2011 at 19:48, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Would people who use these variables please try the patch below, and
> > report any findings, both positive and negative? Please report your
> > findings to the bug tracker at 6671@debbugs.gnu.org, so that the
> > details get filed there.
>
> On first tests, it seems to work great. I see no unwanted recentering,
> line-by-line scrolling is smooth and reasonably fast, and goto-line
> moves around the file blindlingly fast again.
That's good to hear. Please see if it still works great after fixing
a stupid mistake with parentheses (see my other mail this morning).
> Scrolling via scroll-up-command is still bad if you lean on the key,
> but that is not related to this patch, I think.
In what sense is that "bad"?
And by "scroll-up-command" do you mean `scroll-up' and `scroll-down'?
next prev parent reply other threads:[~2011-03-27 3:59 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
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 [this message]
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=83ipv5rz62.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 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).