From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Eli Zaretskii <eliz@gnu.org>, 57245@debbugs.gnu.org
Subject: bug#57245: 29.0.50; M-> in a large XML file (without long lines) is slow
Date: Tue, 16 Aug 2022 17:45:13 -0400 [thread overview]
Message-ID: <jwvtu6b50ex.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <6688b0ad-54e1-4a59-e9b6-4cdc803a8359@yandex.ru> (Dmitry Gutov's message of "Tue, 16 Aug 2022 23:49:38 +0300")
> The font-lock narrowing (if it's indeed the method we're going to use to
> speed up its performance) shouldn't be conditioned on the presence of
> long lines.
font-lock does suffer from long lines, so the current code's handling of
font-lock makes some sense. But indeed, we all agree it's not
sufficient because it only handles the long lines problem, and we still
need to tackle the case of large buffers, which is related but different.
Stefan
next prev parent reply other threads:[~2022-08-16 21:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 14:33 bug#57245: 29.0.50; M-> in a large XML file (without long lines) is slow Dmitry Gutov
2022-08-16 16:54 ` Eli Zaretskii
2022-08-16 18:40 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-16 18:59 ` Eli Zaretskii
2022-08-16 19:32 ` Dmitry Gutov
2022-08-16 20:22 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-16 20:49 ` Dmitry Gutov
2022-08-16 21:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-16 22:20 ` Dmitry Gutov
2022-08-17 11:36 ` Eli Zaretskii
2022-08-17 11:46 ` Dmitry Gutov
2022-08-17 12:16 ` Eli Zaretskii
2022-08-17 12:30 ` Dmitry Gutov
2022-08-17 12:33 ` Eli Zaretskii
2022-08-17 12:46 ` Dmitry Gutov
2022-08-17 11:24 ` Eli Zaretskii
2022-08-17 12:14 ` Dmitry Gutov
2022-08-17 12:20 ` Eli Zaretskii
2022-08-17 12:40 ` Dmitry Gutov
2022-08-17 13:20 ` 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=jwvtu6b50ex.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=57245@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.