From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: 45652@debbugs.gnu.org
Subject: bug#45652: so-long mode not triggered despite big file with very long lines
Date: Mon, 11 Jan 2021 20:55:38 +0800 [thread overview]
Message-ID: <87k0sjljjp.5.fsf@jidanni.org> (raw)
In-Reply-To: <877dosudon.5.fsf@jidanni.org>
Let's make a deal: have so-long mode be the default (for those who have
opted in) for all "big" files in the first place.
I recall for this .har, it starts out well behaved, but then the
whopping lines are closer to the bottom of the file.
I would say that opening any large file is fraught with danger (of
locking up emacs, requiring kill -1.)
And, if the user is sure his file is safe, he can always toggle so-long
mode off for that file.
Even having emacs scan a file for big lines sounds like it might be
risky. So it would be great to give the scanner a vacation in such large
file cases.
PS> for `so-long-detected-long-line-p' for details.
Not yet in 27.1
PS> https://git.savannah.nongnu.org/cgit/so-long.git/plain/so-long.el?h=wip
That's OK, I'm not really following this that closely. Just giving suggestions.
next prev parent reply other threads:[~2021-01-11 12:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 11:47 bug#45652: so-long mode not triggered despite big file with very long lines 積丹尼 Dan Jacobson
2021-01-10 14:53 ` Lars Ingebrigtsen
2021-01-11 11:21 ` 積丹尼 Dan Jacobson
2021-01-11 11:28 ` Phil Sainty
2021-01-11 12:55 ` 積丹尼 Dan Jacobson [this message]
2021-01-11 19:10 ` Phil Sainty
2021-01-11 23:04 ` 積丹尼 Dan Jacobson
2021-01-12 2:30 ` Phil Sainty
2021-01-12 5:53 ` 積丹尼 Dan Jacobson
2021-01-11 18:39 ` Lars Ingebrigtsen
2021-01-11 19:18 ` Phil Sainty
2021-01-11 19:30 ` Lars Ingebrigtsen
2021-01-11 21:07 ` Lars Ingebrigtsen
2021-01-12 2:42 ` Phil Sainty
2021-01-12 12:41 ` Lars Ingebrigtsen
2021-01-12 15:28 ` Eli Zaretskii
2021-01-12 15:37 ` Lars Ingebrigtsen
2021-01-12 15:50 ` Eli Zaretskii
2021-01-12 17:44 ` Lars Ingebrigtsen
2021-01-12 19:22 ` Lars Ingebrigtsen
2021-01-12 23:49 ` Phil Sainty
2021-07-30 5:30 ` Phil Sainty
2021-08-03 11:47 ` Phil Sainty
2021-01-12 3:25 ` Eli Zaretskii
2021-01-12 12:40 ` 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
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=87k0sjljjp.5.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=45652@debbugs.gnu.org \
--cc=psainty@orcon.net.nz \
/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).