all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mark Diekhans <markd@soe.ucsc.edu>
Cc: 13675@debbugs.gnu.org
Subject: bug#13675: Extremely slow redisplay when lines are very long
Date: Fri, 20 Oct 2017 09:44:30 +0300	[thread overview]
Message-ID: <831slye2sx.fsf@gnu.org> (raw)
In-Reply-To: <23017.21788.768005.940877@eduroam-169-233-201-230.ucsc.edu> (message from Mark Diekhans on Thu, 19 Oct 2017 18:45:00 -0700)

> From: Mark Diekhans <markd@soe.ucsc.edu>
> Date: Thu, 19 Oct 2017 18:45:00 -0700
> 
> Is there anyone working on the long-line display speed issue?

Not that I know of.  I don't even have an idea for how to speed it up,
and I don't think anyone's come up with such ideas.

> It is especially bad with font lock mode.

What mode/kind of file needs font lock and has such long lines?

In general, if you must handle such files, my advice is to use M-x
find-file-literally for them, it might make Emacs just barely
bearable, if you are lucky.  But then you lose any font locking and
text encoding support, so this is only feasible for plain-ASCII files
that basically present some text.

> If the fix is really complex, it would be much better emacs
> refuse to display the file than force killing it.

Patches for presenting a warning for such files, like we do with very
large files, are welcome.





  reply	other threads:[~2017-10-20  6:44 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 [this message]
2017-10-20 11:57     ` Phil Sainty
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=831slye2sx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=13675@debbugs.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.