From: Gregory Heytings <gregory@heytings.org>
To: Alan Mackenzie <acm@muc.de>
Cc: Eli Zaretskii <eliz@gnu.org>, larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: How the long-lines "optimisation" breaks font locking.
Date: Thu, 04 Aug 2022 15:22:19 +0000 [thread overview]
Message-ID: <3d639ea126ded0b4a733@heytings.org> (raw)
In-Reply-To: <YuvbNR6q7181G0Ab@ACM>
>
> No matter what criterion one deems "workable", there will be some size
> of buffer, or line, which renders Emacs "unworkable".
>
Wrong. You can now edit files with 1 GB or 5 GB on a single line almost
fine. The limit is now the amount of memory on your computer. I keep
investigating to see if it's possible to overcome that limit. Stay tuned!
next prev parent reply other threads:[~2022-08-04 15:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 18:39 How the long-lines "optimisation" breaks font locking Alan Mackenzie
2022-08-03 19:03 ` Lars Ingebrigtsen
2022-08-04 10:44 ` Alan Mackenzie
2022-08-04 12:54 ` Eli Zaretskii
2022-08-04 14:44 ` Alan Mackenzie
2022-08-04 14:52 ` Lars Ingebrigtsen
2022-08-04 15:22 ` Gregory Heytings [this message]
2022-08-05 1:23 ` Ihor Radchenko
2022-08-04 16:09 ` Eli Zaretskii
2022-08-05 10:56 ` Alan Mackenzie
2022-08-05 11:20 ` Eli Zaretskii
2022-08-05 13:04 ` Dmitry Gutov
2022-08-05 14:22 ` Eli Zaretskii
2022-08-05 14:29 ` Dmitry Gutov
2022-08-05 15:30 ` Eli Zaretskii
2022-08-05 19:50 ` Dmitry Gutov
2022-08-06 5:36 ` Eli Zaretskii
2022-08-06 10:54 ` Dmitry Gutov
2022-08-04 13:11 ` Eric S Fraga
2022-08-04 13:34 ` Po Lu
2022-08-04 14:38 ` Eric S Fraga
2022-08-04 16:16 ` SOLVED: " Eric S Fraga
2022-08-04 16:21 ` Eric S Fraga
2022-08-04 17:36 ` Stefan Kangas
2022-08-05 9:36 ` Eric S Fraga
2022-08-05 11:13 ` Eli Zaretskii
2022-08-05 12:28 ` Eric S Fraga
2022-08-05 13:40 ` Eric S Fraga
2022-08-05 23:11 ` Tim Cross
2022-08-05 23:23 ` Lars Ingebrigtsen
2022-08-08 11:51 ` Fraga, Eric
2022-08-03 19:15 ` Eli Zaretskii
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=3d639ea126ded0b4a733@heytings.org \
--to=gregory@heytings.org \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).