unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: antoine.levitt@gmail.com, 8355@debbugs.gnu.org
Subject: bug#8355: 24.0.50; Boxes in mode-line and scrolling
Date: Tue, 08 Dec 2020 20:29:57 +0200	[thread overview]
Message-ID: <83r1o05exm.fsf@gnu.org> (raw)
In-Reply-To: <87czzkb1qz.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue,  08 Dec 2020 19:18:12 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 8355@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
> Date: Tue, 08 Dec 2020 19:18:12 +0100
> 
> Antoine Levitt <antoine.levitt@gmail.com> writes:
> 
> > Here's a reproducer from emacs -Q (just reproduced on 27.1):
> >
> > Set
> > (setq scroll-conservatively 100000000)
> > (setq scroll-preserve-screen-position 'stay)
> >
> > Open a latex file of some complexity (with sections and math, for
> > instance https://arxiv.org/e-print/2003.00726, but it works on any tex
> > file), and make sure it's in latex-mode. Go somewhere in the middle of
> > the file, center point (C-l), then scroll up then down (C-v and M-v).
> 
> Yup; I can reproduce this in Emacs 28 -- point moves around a lot when
> paging back and forth.

I wouldn't say "a lot".  On my system it moves by less than a screen
line.

> > I traced it down to
> > lines of varying heights: it disappears if I set
> > (setq font-latex-fontify-script nil)
> > (setq font-latex-fontify-sectioning 'color)
> 
> Yes, I guess this is due to the mixture of line heights in that
> buffer -- when it's computing how many lines to scroll back and forth,
> it's not being consistent when going forward and backward.
> 
> Eli, does this sound familiar to you?

Not really.  I will look into it, in case there's some off-by-one, but
you are probably right about the reason.





  reply	other threads:[~2020-12-08 18:29 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 [this message]
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
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=83r1o05exm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=8355@debbugs.gnu.org \
    --cc=antoine.levitt@gmail.com \
    --cc=larsi@gnus.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).