From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs freezes when editing a file with one extremely long line even with so-long-minor-mode enabled.
Date: Sat, 07 May 2022 16:46:48 +0200 [thread overview]
Message-ID: <87k0ax9z8n.fsf@dataswamp.org> (raw)
In-Reply-To: m2k0axq0u1.fsf@gmail.com
Daniel Fleischer wrote:
>> Don't have files "with one extremely long line".
>>
>> 1. It doesn't make sense.
>>
>> 2. Emacs freezes.
>
> One of the cases I deal with is editing JSON files.
> These usually don't have any styling information because
> they are text-base serialized objects and so no newlines and
> can range from a few bytes to hundreds of MB, all in
> a single line.
Not good.
> Sure I can open them and "beautify" them
Sure, but you shouldn't need to.
> but they are automatically generated
Nuclear missile 1: - Target area identified.
Nuclear missile 2: - Here is where we need to blow up.
Nuclear missile 3: - Auto-generated is all well and good but
tell the program that does it not to create a file like that.
Nuclear missiles 1 & 2: - ...
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-05-07 14:46 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 23:45 Emacs freezes when editing a file with one extremely long line even with so-long-minor-mode enabled Hongyi Zhao
2022-05-07 2:45 ` Emanuel Berg
2022-05-07 7:05 ` Daniel Fleischer
2022-05-07 14:46 ` Emanuel Berg [this message]
2022-05-07 6:19 ` Eli Zaretskii
2022-05-07 6:23 ` Hongyi Zhao
2022-05-07 7:09 ` Eli Zaretskii
2022-05-07 7:33 ` Hongyi Zhao
2022-05-07 7:36 ` Hongyi Zhao
2022-05-07 7:43 ` Eli Zaretskii
2022-05-07 8:12 ` Hongyi Zhao
2022-05-07 11:38 ` Leo Butler
2022-05-07 12:15 ` Eli Zaretskii
2022-05-08 3:42 ` Michael Heerdegen
2022-05-07 12:42 ` 황병희
2022-05-07 23:35 ` Michael Heerdegen
2022-05-08 0:10 ` Hongyi Zhao
2022-05-08 0:49 ` Michael Heerdegen
2022-05-08 2:54 ` Hongyi Zhao
2022-05-08 3:31 ` Michael Heerdegen
2022-05-08 3:58 ` Hongyi Zhao
2022-05-08 4:11 ` Michael Heerdegen
2022-05-08 4:18 ` Hongyi Zhao
2022-05-08 4:38 ` Michael Heerdegen
2022-05-08 4:56 ` Michael Heerdegen
2022-05-08 5:35 ` Michael Heerdegen
2022-05-08 5:47 ` Hongyi Zhao
2022-05-09 4:53 ` Michael Heerdegen
2022-05-09 6:48 ` Hongyi Zhao
2022-05-08 5:31 ` Eli Zaretskii
2022-05-08 5:38 ` Hongyi Zhao
2022-05-08 5:53 ` Eli Zaretskii
2022-05-08 7:29 ` Hongyi Zhao
2022-05-09 4:54 ` Michael Heerdegen
2022-05-09 6:41 ` Hongyi Zhao
2022-05-10 2:07 ` Michael Heerdegen
2022-05-10 2:26 ` Hongyi Zhao
2022-05-09 9:48 ` Manuel Giraud
2022-05-11 6:33 ` Michael Heerdegen
2022-05-11 8:21 ` Manuel Giraud
2022-05-11 11:27 ` 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=87k0ax9z8n.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=help-gnu-emacs@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.
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).