* bug#61465: so-long-commentary: say how to prepare against long line output
@ 2023-02-12 23:26 Dan Jacobson
2023-02-13 13:52 ` Eli Zaretskii
0 siblings, 1 reply; 2+ messages in thread
From: Dan Jacobson @ 2023-02-12 23:26 UTC (permalink / raw)
To: 61465
(so-long-commentary)
should mention how to guard against
M-! shell-command "cat long_line_file.txt", and
M-x compile "cat long_line_file.txt"
in addition to just dealing with
M-x find-file long_line_file.txt .
emacs-version "28.2"
^ permalink raw reply [flat|nested] 2+ messages in thread
* bug#61465: so-long-commentary: say how to prepare against long line output
2023-02-12 23:26 bug#61465: so-long-commentary: say how to prepare against long line output Dan Jacobson
@ 2023-02-13 13:52 ` Eli Zaretskii
0 siblings, 0 replies; 2+ messages in thread
From: Eli Zaretskii @ 2023-02-13 13:52 UTC (permalink / raw)
To: Dan Jacobson; +Cc: 61465
tags 61465 wontfix
close 61465
thanks
> From: Dan Jacobson <jidanni@jidanni.org>
> Date: Mon, 13 Feb 2023 07:26:14 +0800
>
> (so-long-commentary)
> should mention how to guard against
> M-! shell-command "cat long_line_file.txt", and
> M-x compile "cat long_line_file.txt"
> in addition to just dealing with
> M-x find-file long_line_file.txt .
>
> emacs-version "28.2"
This mode basically takes back seat in Emacs 29, since we have much
better ways of handling files with very long lines. So I don't think
we should invest any significant effort in extending so-long-mode now.
Closing.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2023-02-13 13:52 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-12 23:26 bug#61465: so-long-commentary: say how to prepare against long line output Dan Jacobson
2023-02-13 13:52 ` Eli Zaretskii
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).