From: Alex <agrambot@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24179@debbugs.gnu.org
Subject: bug#24179: 25.1; scroll-conservatively over SCROLL_LIMIT may put point in the wrong place
Date: Thu, 11 Aug 2016 16:20:07 -0600 [thread overview]
Message-ID: <87fuqb3q3s.fsf@gmail.com> (raw)
In-Reply-To: <83inv7fiq5.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 11 Aug 2016 18:06:26 +0300")
tags 24179 fixed
close 24179
quit
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Alex <agrambot@gmail.com>
>> Cc: 24179@debbugs.gnu.org
>> Date: Mon, 08 Aug 2016 11:22:29 -0600
>> You're right, though it also seems to happen when using C-n. I tried
>> turning off line-move-visual and the delay is still there.
>
> I have now fixed that problem as well.
Thanks, I don't see it anymore with C-n. It's expected that the delay
with M-g c and magit-blame's `n' command is still present, right?
Though your new commit does seem to lessen those delays, if that means
anything.
> OK. If no new issues come up due to my changes, please close the bug
> in a few days.
Hopefully the above did that.
next prev parent reply other threads:[~2016-08-11 22:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-07 21:15 bug#24179: 25.1; scroll-conservatively over SCROLL_LIMIT may put point in the wrong place Alex
2016-08-08 2:39 ` Eli Zaretskii
2016-08-08 5:42 ` Alex
2016-08-08 15:31 ` Eli Zaretskii
2016-08-08 16:35 ` Alex
2016-08-08 16:58 ` Eli Zaretskii
2016-08-08 17:22 ` Alex
2016-08-08 17:35 ` Eli Zaretskii
2016-08-11 15:06 ` Eli Zaretskii
2016-08-11 22:20 ` Alex [this message]
2016-08-12 14:17 ` Eli Zaretskii
2016-08-12 22:01 ` Alex
2016-08-13 6:52 ` Eli Zaretskii
2016-08-13 16:59 ` Alex
2016-08-13 17:25 ` Eli Zaretskii
2016-08-14 18:27 ` Eli Zaretskii
2016-08-14 20:05 ` Alex
2016-08-11 16:39 ` bug#24179: 24179 Jonas Bernoulli
2016-08-11 17:15 ` Eli Zaretskii
2016-08-11 18:29 ` Jonas Bernoulli
2016-08-11 19:55 ` Eli Zaretskii
2016-08-11 20:07 ` Eli Zaretskii
2016-08-11 22:19 ` Jonas Bernoulli
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=87fuqb3q3s.fsf@gmail.com \
--to=agrambot@gmail.com \
--cc=24179@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).