unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: control@debbugs.gnu.org, 44809@debbugs.gnu.org
Subject: bug#44809: Warn that current file needs so-long mode
Date: Sat, 28 Nov 2020 03:43:25 +0800	[thread overview]
Message-ID: <87ft4ud1r6.5.fsf_-_@jidanni.org> (raw)
In-Reply-To: <877dqcdgtq.5.fsf@jidanni.org>

retitle 44809 Say "Consider switching so-long mode on" when detecting long line files
thanks

>>>>> "LI" == Lars Ingebrigtsen <larsi@gnus.org> writes:

>> Before long one can only put it out of its misery with
>> $ killall -1 emacs.

LI> Yes, this is a general Emacs problem.  Consider switching so-long mode
LI> on.

OK. SO LONG as emacs also says that automatically,
when detecting such files.
Else the user will never know.
And ends up reporting more bugs than necessary.

Then at least the user will know something is up and won't try ESC >
etc. locking up emacs.





  reply	other threads:[~2020-11-27 19:43 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   ` 積丹尼 Dan Jacobson [this message]
     [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
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=87ft4ud1r6.5.fsf_-_@jidanni.org \
    --to=jidanni@jidanni.org \
    --cc=44809@debbugs.gnu.org \
    --cc=control@debbugs.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).