unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alex <agrambot@gmail.com>
Cc: 24179@debbugs.gnu.org
Subject: bug#24179: 25.1; scroll-conservatively over SCROLL_LIMIT may put point in the wrong place
Date: Mon, 08 Aug 2016 19:58:38 +0300	[thread overview]
Message-ID: <83fuqfi4e9.fsf@gnu.org> (raw)
In-Reply-To: <87r39zkyli.fsf@gmail.com> (message from Alex on Mon, 08 Aug 2016 10:35:37 -0600)

> From: Alex <agrambot@gmail.com>
> Cc: 24179@debbugs.gnu.org
> Date: Mon, 08 Aug 2016 10:35:37 -0600
> 
> Unfortunately it seems like there's a brief delay (that is only
> noticeable in magit-blame) now where the point is temporarily in the
> wrong place (as before), before quickly moving to the correct position.

Not on my system, not after C-f at position 1350 anyway.

However, what you describe happens elsewhere in magit-blame's display.
E.g., I see it when I do "M-g c 1350 RET" as part of the recipe.  So
this is a separate issue.

In general, overlay strings with newlines are hard on the display
engine, especially when line-move-visual is on and under
scroll-conservatively.

> > Btw, magit-blame could be nicer to the display engine by placing a
> > 'cursor' property on the first character of each before-string it
> > creates to show the blamed commit.
> 
> Perhaps that would help with the above delay?

Could be.  It will also eliminate those annoying jumps of the cursor
when it needs to "step over" the lines that come from before-strings.





  reply	other threads:[~2016-08-08 16:58 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 [this message]
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
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=83fuqfi4e9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24179@debbugs.gnu.org \
    --cc=agrambot@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).