From: Gregory Heytings <gregory@heytings.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: feature/fix-the-long-lines-display-bug c760d2ed16: * etc/PROBLEMS: Remove the entry which is no longer relevant.
Date: Mon, 18 Jul 2022 21:04:31 +0000 [thread overview]
Message-ID: <fa7b8ced35579cdfe9ee@heytings.org> (raw)
In-Reply-To: <jwvsfmydtmx.fsf-monnier+emacs@gnu.org>
>> -*** Editing files with very long lines is slow.
>> -
>> -For example, simply moving through a file that contains hundreds of
>> -thousands of characters per line is slow, and consumes a lot of CPU.
>> -This is a known limitation of Emacs with no solution at this time.
>
> I wish this were true, but AFAIK the problem is still very much present.
> We deal with it a bit better, but that doesn't mean the problem is gone.
> In my tests, editing the end of a 1MB single-line JSON file is still
> basically not an option, for example.
>
Please try the feature branch, and you'll see the problem is gone.
next prev parent reply other threads:[~2022-07-18 21:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165817030092.24067.4562191765367761985@vcs2.savannah.gnu.org>
[not found] ` <20220718185141.39F11C0F203@vcs2.savannah.gnu.org>
2022-07-18 21:01 ` feature/fix-the-long-lines-display-bug c760d2ed16: * etc/PROBLEMS: Remove the entry which is no longer relevant Stefan Monnier
2022-07-18 21:04 ` Gregory Heytings [this message]
2022-07-18 21:36 ` Philip Kaludercic
2022-07-18 21:46 ` Gregory Heytings
2022-07-19 4:10 ` Philip Kaludercic
2022-07-19 5:21 ` Gregory Heytings
2022-07-21 11:50 ` Gregory Heytings
2022-07-21 12:43 ` Stefan Kangas
2022-07-21 14:51 ` Daniel Martín
2022-07-21 15:25 ` Stefan Monnier
2022-07-21 16:09 ` Eli Zaretskii
2022-07-21 16:36 ` Gregory Heytings
2022-07-22 14:48 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa7b8ced35579cdfe9ee@heytings.org \
--to=gregory@heytings.org \
--cc=emacs-devel@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.