From: Eval Exec <execvy@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 74813@debbugs.gnu.org
Subject: bug#74813: 31.0.50; scroll-down is 10x slower and laggy than scroll-up
Date: Sat, 28 Dec 2024 21:31:28 +0800 [thread overview]
Message-ID: <CAKfPJDoXtxPdWEJWNxcw6QX3Arvy-AKt4_+9q+8fzFh96a0MXQ@mail.gmail.com> (raw)
In-Reply-To: <864j2oul7t.fsf@gnu.org>
Friendly Pong. I'm busy these days. I will upload a reproducible
minimal init.el tomorrow.
On Sat, Dec 28, 2024 at 6:59 PM Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Cc: 74813@debbugs.gnu.org
> > Date: Thu, 12 Dec 2024 11:11:45 +0200
> > From: Eli Zaretskii <eliz@gnu.org>
> >
> > > From: Eval Exec <execvy@gmail.com>
> > > Date: Thu, 12 Dec 2024 15:59:51 +0800
> > >
> > >
> > > I opened a large rust file, about 5000 lines.
> > > scroll-up is quick and smooth, no laggy:
> > > [...]
> > >
> > > but scroll down is very laggy:
> > >
> > > 2667 87% - command-execute
> > > 2666 87% - funcall-interactively
> > > 2666 87% - evil-scroll-page-up
> > > 2666 87% - scroll-down
> > > 2665 87% - apply
> > > 2664 87% - ad-Advice-scroll-down
> > ^^^^^^^^^^^^^^^^^^^^^
> > > 2663 87% - #<primitive-function scroll-down>
> >
> > First, you have an advice on scroll-down.
> >
> > Furthermore, scrolling down exposes portions of a file that were never
> > seen before, which needs to fontify them. If fontification is
> > expensive, it is expected that you will see some lags. What happens
> > if you scroll down, then go back to the beginning, and then scroll
> > down again -- is scrolling down the second time much faster?
> >
> > Also, you didn't say which major mode did you use for this file.
>
> Ping! Can you please answer my questions?
prev parent reply other threads:[~2024-12-28 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 7:59 bug#74813: 31.0.50; scroll-down is 10x slower and laggy than scroll-up Eval Exec
2024-12-12 9:11 ` Eli Zaretskii
2024-12-28 10:59 ` Eli Zaretskii
2024-12-28 13:31 ` Eval Exec [this message]
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=CAKfPJDoXtxPdWEJWNxcw6QX3Arvy-AKt4_+9q+8fzFh96a0MXQ@mail.gmail.com \
--to=execvy@gmail.com \
--cc=74813@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).