unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: antoine.levitt@gmail.com, 8355@debbugs.gnu.org
Subject: bug#8355: 24.0.50; Boxes in mode-line and scrolling
Date: Wed, 09 Dec 2020 18:01:44 +0100	[thread overview]
Message-ID: <87h7ouykuf.fsf@gnus.org> (raw)
In-Reply-To: <838sa754yt.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 09 Dec 2020 18:17:30 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> I installed a partial fix for this.  It improves the situation, in
> that for many starting positions of point, the sequence of N C-v's
> followed by N M-v's, or vice versa, will now end up in the same line
> and the same screen position.  There are still cases where we end up
> short by one line, and I don't see how that could be fixed as long as
> the buffer has some stretches of lines with smaller or larger height.
>
> Please try the latest master; if the improvement is sufficient, we can
> close this bug.

I tried it now, and it's a lot more consistent now than it was before.
Before it was almost always off by one line, but now it's correct most
of the time.

I tried this on something that has more dramatic line height
differences, and the phenomenon is more noticeable there -- when
scrolling downwards, things are very predictable, but when scrolling
backwards, Emacs seems to decide to scroll a couple of screenfuls when
there's large images in the buffer, and you have to C-v twice to get
back to where you were.

Should I make a test case?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-12-09 17:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-27 13:41 bug#8355: 24.0.50; Boxes in mode-line and scrolling Antoine Levitt
2020-12-08 15:05 ` Lars Ingebrigtsen
2020-12-08 15:56   ` Antoine Levitt
2020-12-08 18:18     ` Lars Ingebrigtsen
2020-12-08 18:29       ` Eli Zaretskii
2020-12-08 18:19     ` Eli Zaretskii
2020-12-08 18:27       ` Lars Ingebrigtsen
2020-12-08 18:33         ` Eli Zaretskii
2020-12-09 16:17           ` Eli Zaretskii
2020-12-09 17:01             ` Lars Ingebrigtsen [this message]
2020-12-09 17:13               ` Eli Zaretskii
2020-12-09 17:24                 ` Lars Ingebrigtsen
2020-12-09 20:47                   ` Antoine Levitt
2020-12-10  3:34                     ` Eli Zaretskii
2020-12-11  8:35                       ` Antoine Levitt
2020-12-11  8:47                         ` Eli Zaretskii
2020-12-11  9:08                           ` Antoine Levitt
2020-12-11 11:59                             ` Eli Zaretskii
2020-12-11 12:25                               ` Antoine Levitt
2020-12-14 18:25                                 ` Eli Zaretskii
2020-12-14 19:02                                   ` Antoine Levitt
2020-12-14 19:27                                     ` Eli Zaretskii
2020-12-14 18:26                   ` Eli Zaretskii
2020-12-14 19:05                     ` Lars Ingebrigtsen
2020-12-14 19:30                       ` Eli Zaretskii
2020-12-15  5:23                         ` Lars Ingebrigtsen
2021-01-20 17:09                           ` Lars Ingebrigtsen

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=87h7ouykuf.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=8355@debbugs.gnu.org \
    --cc=antoine.levitt@gmail.com \
    --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).