From: Phil Sainty <psainty@orcon.net.nz>
To: Eli Zaretskii <eliz@gnu.org>, Mark Diekhans <markd@soe.ucsc.edu>
Cc: 13675@debbugs.gnu.org
Subject: bug#13675: Extremely slow redisplay when lines are very long
Date: Sat, 21 Oct 2017 15:03:28 +1300 [thread overview]
Message-ID: <21c26b38-0d14-3600-a80d-ddd95f41cc09@orcon.net.nz> (raw)
In-Reply-To: <1d241e49-61bc-089c-ce02-2075a4e98905@orcon.net.nz>
On 21/10/17 00:57, Phil Sainty wrote:
> FWIW I wrote https://savannah.nongnu.org/projects/so-long which
> tries to avoid performance issues in buffers with unexpectedly
> long lines by automatically changing the major mode and disabling
> various minor modes for that buffer
I wrote a more detailed overview at:
https://lists.gnu.org/archive/html/emacs-devel/2016-07/msg00742.html
That was preparation for adding so-long.el to GNU ELPA -- before I
came to the realisation that the scenarios which affected me had all
been caused by third-party libraries, and that the most notable
issue had already been fixed upstream by the library's author.
At this point I worried that I was severely over-stating the benefits
of my code, as I no longer had a good example of my library improving
things by a significant margin, and in particular could not find a
scenario using only default Emacs libraries. I think this was the
main reason why I didn't proceed with adding so-long to ELPA at the
time.
I do think it might still be worth adding to ELPA, but a good example
of it being useful would be really helpful.
As such, if anyone is reading this, tries out so-long.el, and finds
that it does indeed help them (with or without configuration), please
drop me a line with some details?
thanks,
-Phil
next prev parent reply other threads:[~2017-10-21 2:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-10 16:26 bug#13675: 24.2.93; Extremely slow redisplay when lines are very long Eli Zaretskii
2013-02-10 17:36 ` Eli Zaretskii
2017-10-20 1:45 ` bug#13675: " Mark Diekhans
2017-10-20 6:44 ` Eli Zaretskii
2017-10-20 11:57 ` Phil Sainty
2017-10-21 2:03 ` Phil Sainty [this message]
2017-10-20 15:50 ` Mark Diekhans
2017-10-20 16:10 ` Eli Zaretskii
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=21c26b38-0d14-3600-a80d-ddd95f41cc09@orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=13675@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=markd@soe.ucsc.edu \
/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.