From: Stefan Monnier <monnier@iro.umontreal.ca>
To: bruce.connor.am@gmail.com
Cc: 18589@debbugs.gnu.org
Subject: bug#18589: Why is the the longlines package obsolete?
Date: Tue, 30 Sep 2014 14:19:36 -0400 [thread overview]
Message-ID: <jwvh9zpj7w7.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <CAAdUY-JcSwV5vnYQ+CEbqxTNXm0+TuA7k=jSm8PfwZYUgAwsXg@mail.gmail.com> (bruce connor am's message of "Tue, 30 Sep 2014 10:57:19 +0100")
> However, from what I understand, visual-line-mode isn't capable of wraping
> lines to be shorter than window width, which was one of longlines' features.
You can get the same result by fiddling with the window margins or by
splitting your window. I seem to remember someone writing code to do
that conveniently, but I wouldn't know where to find it.
> Is longlines-mode really redundant?
visual-lines-mode provides the feature for which longlines-mode was
written, so in this sense it's definitely obsolete/redundant.
Of course, by virtue of working differently, it might provide some
functionality which visual-lines-mode can't provide. But "lines shorter
than the window" is not really one of them.
Recently someone pointed out that using longlines-mode in a buffer that
contain *very* long lines makes it possible to view&edit the buffer
without suffering unbearable performance problems. So maybe in this
sense it's not completely obsolete.
Stefan
next prev parent reply other threads:[~2014-09-30 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 9:57 bug#18589: Why is the the longlines package obsolete? bruce.connor.am
2014-09-30 15:54 ` Glenn Morris
2014-09-30 16:18 ` bruce.connor.am
2014-09-30 18:19 ` Stefan Monnier [this message]
2014-09-30 23:40 ` bruce.connor.am
2014-10-01 1:33 ` Stefan Monnier
2014-10-01 8:01 ` bruce.connor.am
2014-10-01 20:39 ` Glenn Morris
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvh9zpj7w7.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=18589@debbugs.gnu.org \
--cc=bruce.connor.am@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.