unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Antoine Levitt <antoine.levitt@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 8355@debbugs.gnu.org
Subject: bug#8355: 24.0.50; Boxes in mode-line and scrolling
Date: Wed, 09 Dec 2020 21:47:48 +0100	[thread overview]
Message-ID: <87y2i6yadn.fsf@inria.fr> (raw)
In-Reply-To: <87czziyjsc.fsf@gnus.org>



09 December 2020 18:24 +01, Lars Ingebrigtsen:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> Yes, please.
>
> This one should illustrate the problem, I think:

Thanks Eli for doing this! Trying out in tex files (same reproducer as
before), it does seem to be a bit better than previously in that I
sometimes see no movement when doing C-v M-v, and generally movement
when it occurs seems to be reduced (ie one line at a time rather than
several), but movement does remain the rule and no movement the
exception. This is even with the default settings for latex, which
results in very moderate line height discrepancies: on a random tex file
on my computer, (line-pixel-height) says normal lines are 18 pixels,
with the ones having subscripts and superscripts being 19 pixels.
Although I often have a lot of subscripts and superscripts, so it's
possible there's more than 9 lines that are 19 pixels tall on my screen,
if that's what matters.

Best,
Antoine





  reply	other threads:[~2020-12-09 20:47 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
2020-12-09 17:13               ` Eli Zaretskii
2020-12-09 17:24                 ` Lars Ingebrigtsen
2020-12-09 20:47                   ` Antoine Levitt [this message]
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=87y2i6yadn.fsf@inria.fr \
    --to=antoine.levitt@gmail.com \
    --cc=8355@debbugs.gnu.org \
    --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).