From: Phil Sainty <psainty@orcon.net.nz>
To: 51051@debbugs.gnu.org
Subject: bug#51051: Restore longlines.el to non-obsolete status
Date: Wed, 06 Oct 2021 14:36:09 +1300 [thread overview]
Message-ID: <9ae936c82a87607abd814ae6cd7ef95b@webmail.orcon.net.nz> (raw)
longlines.el was marked obsolete in 24.4 on the basis that
visual-line-mode provided a better alternative, and indeed
visual-line-mode is better for wrapping lines of normal lengths;
however longlines-mode is actually very valuable for editing
files with lines that are so long that they cause performance
problems. This is because longlines-mode converts the long
lines into short lines for editing, and therefore it will give
you good performance at *any* position in the file.
For this reason, so-long.el has supported longlines-mode as a
standard action since version 1.0. While so-long-mode is very
fast to enable, it still won't cope well if you move point deep
into an incredibly long line. Conversely longlines-mode is slow
to enable (as it has to break all the long lines), but it then
gives good performance everywhere in the buffer. As such they
complement one another (and you can switch between them via the
"So Long" menu).
As longlines.el is still valuable for reasons unrelated to
visual-line-mode, I'd like it to be restored to non-obsolete
status. I think the relationship with visual-line-mode (and
recommendation of the latter for line-wrapping in general) can
just be documented in the longlines commentary.
-Phil
next reply other threads:[~2021-10-06 1:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 1:36 Phil Sainty [this message]
2021-10-06 9:21 ` bug#51051: Restore longlines.el to non-obsolete status Lars Ingebrigtsen
2021-10-06 23:16 ` Stefan Kangas
-- strict thread matches above, loose matches on Subject: below --
2014-09-30 9:57 bug#18589: Why is the the longlines package obsolete? bruce.connor.am
2014-09-30 18:19 ` Stefan Monnier
2022-07-02 15:33 ` bug#51051: Restore longlines.el to non-obsolete status 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=9ae936c82a87607abd814ae6cd7ef95b@webmail.orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=51051@debbugs.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).