From: divya--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 74281@debbugs.gnu.org
Subject: bug#74281: 30.0.91; font-lock mode hangs on scrolling large Scheme file
Date: Thu, 02 Jan 2025 14:12:06 +0000 [thread overview]
Message-ID: <e66ea071712c29557364ba65ad9c0ba8@subvertising.org> (raw)
In-Reply-To: <jwv4j2koq9z.fsf-monnier+emacs@gnu.org>
Hello again Stefan and Happy GNU/Year.
> Hmm... on my tests, I can reproduce in `emacs-30` the very slow
> font-locking you described when we're at the end of the buffer, but not
> on `master`. Just to confirm that you're running the "right" code, can
> you do `M-: font-lock--syntax-table-affects-ppss RET` from within that
> `tex.scm` buffer? It should return nil if my fix was applied. If it
> returns t then you're presumably still using the old code (or there's
> something else amiss). If it returns something else than nil or t then
> there's something else amiss.
I just checked and my compiled build was of an older commit. The
variable was set `t`. I built from the latest commit and indeed now I
can scroll flawlessly in the reported file.
> FWIW, even with the fix, Emacs is not quite able to keep up with `M-v`
> with an auto-repeat of 40/s when done from the end of the buffer, but:
> - When I release the key it catches up fairly quickly (hence the "not
> quite"). So I wouldn't describe it as "hangs".
> - This is on my 16 years old 2.5GHz Core 2 Duo (Thinkpad T61).
> - It's an Emacs compiled with `-Og` and with `--enable-checking`.
That's reasonable for the system. I do not notice any sort of lag with
`M-v` on my system (Ryzen 7 5700G).
Thank you Eli and Stefan for the prompt fix. Really admire the work you
guys do.
Regards,
Divya Ranjan,
Mathematics, Philosophy and Libre Software
next prev parent reply other threads:[~2025-01-02 14:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-09 16:04 bug#74281: 30.0.91; font-lock mode hangs on scrolling large Scheme file Divya Ranjan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-14 8:44 ` Eli Zaretskii
2024-11-14 9:32 ` Divya Ranjan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-14 10:06 ` Eli Zaretskii
2024-11-14 11:09 ` Divya Ranjan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-14 11:42 ` Eli Zaretskii
2024-11-14 16:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 9:51 ` Eli Zaretskii
2024-12-14 9:34 ` Eli Zaretskii
2024-12-28 11:09 ` Eli Zaretskii
2024-12-29 18:38 ` Divya Ranjan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-28 15:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-28 16:33 ` Eli Zaretskii
2024-12-29 15:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-29 18:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-29 18:58 ` Eli Zaretskii
2024-12-29 20:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-30 12:47 ` Eli Zaretskii
2024-12-29 18:43 ` Divya Ranjan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-30 4:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-30 5:35 ` Divya Ranjan via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-30 21:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-02 14:12 ` divya--- via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2025-01-04 13:10 ` Eli Zaretskii
2025-01-04 14:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e66ea071712c29557364ba65ad9c0ba8@subvertising.org \
--to=bug-gnu-emacs@gnu.org \
--cc=74281@debbugs.gnu.org \
--cc=divya@subvertising.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.