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 00:57:43 +1300 [thread overview]
Message-ID: <1d241e49-61bc-089c-ce02-2075a4e98905@orcon.net.nz> (raw)
In-Reply-To: <831slye2sx.fsf@gnu.org>
On 20/10/17 19:44, Eli Zaretskii wrote:
> What mode/kind of file needs font lock and has such long lines?
The common cases I would run into were with 'minified' files of
programming code, where as much whitespace as possible has been
removed to reduce the file size.
e.g. Things like https://code.jquery.com/jquery-git.min.js
That kind of file is not intended to be edited by hand, but so
far as Emacs is concerned it's just a regular javascript file,
and therefore font-lock and all the other modes which would be
enabled for editing javascript will be used.
> Patches for presenting a warning for such files, like we do with
> very large files, are welcome.
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 (based on a pre-configured
list).
It can only address certain classes of problem, mind, and it
needs some more work (and has been waiting for me to get back
to it); but it more or less does what it's intended to do, so
others might find it useful as-is (I certainly use it myself).
See https://www.emacswiki.org/emacs/SoLong for more information.
-Phil
next prev parent reply other threads:[~2017-10-20 11:57 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 [this message]
2017-10-21 2:03 ` Phil Sainty
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=1d241e49-61bc-089c-ce02-2075a4e98905@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.