From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Devon Sean McCullough <Devon2020@jovi.net>, 44818@debbugs.gnu.org
Subject: bug#44818: 27.0.91; wedged
Date: Tue, 24 Nov 2020 08:04:16 +0100 [thread overview]
Message-ID: <877dqb9qxb.fsf@gnus.org> (raw)
In-Reply-To: <83a6v8vzok.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 23 Nov 2020 17:51:55 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> When you visit such a long file in Emacs 27.1, you should see a
> suggestion to visit it literally; take it.
>
> A more general solution is to turn on so-long mode.
This is such a general problem that people bump into all the time that I
think Emacs should have an even more general solution, and it should be
on by default.
The long-file warning isn't sufficient -- there's plenty of smaller
files that have this problem, too.
Why doesn't Emacs just check for long lines (in the C code, for speed)
when opening files, and offer the "visit literally?" if it detects them?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-11-24 7:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 1:04 bug#44809: One very long line of <中文> XML tags puts emacs out of business 積丹尼 Dan Jacobson
2020-11-24 7:05 ` Lars Ingebrigtsen
2020-11-27 19:43 ` bug#44809: Warn that current file needs so-long mode 積丹尼 Dan Jacobson
[not found] ` <handler.s.C.160651363628407.transcript@debbugs.gnu.org>
2020-11-23 5:07 ` bug#44818: 27.0.91; wedged Devon Sean McCullough
2020-11-23 15:51 ` Eli Zaretskii
2020-11-24 7:04 ` Lars Ingebrigtsen [this message]
2020-11-24 15:39 ` Eli Zaretskii
2020-11-25 6:57 ` Lars Ingebrigtsen
2020-11-25 15:37 ` Eli Zaretskii
2020-11-24 18:42 ` Devon Sean McCullough
2020-11-24 18:48 ` Eli Zaretskii
2020-11-25 1:35 ` Devon Sean McCullough
2020-11-25 8:34 ` Andreas Schwab
2020-11-25 14:47 ` Devon Sean McCullough
2020-11-25 15:06 ` Eli Zaretskii
2020-11-26 17:06 ` Devon Sean McCullough
2020-11-27 5:40 ` Richard Stallman
2020-12-01 11:32 ` Devon Sean McCullough
2020-12-02 4:32 ` Richard Stallman
2020-12-02 15:00 ` Eli Zaretskii
2020-12-03 5:29 ` Richard Stallman
2020-12-03 14:53 ` Eli Zaretskii
2020-12-04 6:01 ` Richard Stallman
2020-12-04 8:36 ` Eli Zaretskii
2020-11-27 8:20 ` Michael Albinus
2020-11-27 22:26 ` bug#44818: Looks like I retitled both bugs 積丹尼 Dan Jacobson
2020-11-29 9:50 ` bug#44809: Warn that current file needs so-long mode Lars Ingebrigtsen
2022-07-23 8:56 ` bug#44818: Say "Consider switching so-long mode on" when detecting long line files 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=877dqb9qxb.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=44818@debbugs.gnu.org \
--cc=Devon2020@jovi.net \
--cc=eliz@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.
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).