unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: joakim@verona.se
To: Ryan B <public@ryanb.org>
Cc: emacs-devel@gnu.org
Subject: Re: Making font-lock handle long lines better
Date: Fri, 10 Feb 2017 16:57:43 +0100	[thread overview]
Message-ID: <m3poiq11jc.fsf@chopper> (raw)
In-Reply-To: <CA+caGh_JN9FRi71VjUTwvYBKKygG-KuGGoe3GBgjthPRh00nRg@mail.gmail.com> (Ryan B.'s message of "Fri, 10 Feb 2017 07:44:15 -0800")

Ryan B <public@ryanb.org> writes:

> hi all! it seems like it's been a known issue for a while that font-lock is slow on very long lines. i've tried lots of optimizations - jit-lock/lazy-lock, font-lock-maximum-decoration, etc. - but even on modern hardware, fontifying still hangs my emacs for 5-10s on
> long lines, e.g. 10k-20k characters, whenever they appear. 
>
> i'm thinking of adding an opt-in line length limit to font-lock-mode, after which it would stop fontifying, evaluating regexps, etc. within each line. i'd love to hear opinions on whether that makes sense, and whether you might consider accepting it into trunk.

As a user, I would appreciate this feature. I dont know if its feasible
to implement it though.


>
> thanks in advance!
-- 
Joakim Verona
joakim@verona.se




  reply	other threads:[~2017-02-10 15:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10 15:44 Making font-lock handle long lines better Ryan B
2017-02-10 15:57 ` joakim [this message]
2017-02-10 16:24 ` Eli Zaretskii
2017-02-11 20:10   ` Wilfred Hughes
2017-02-11 20:28     ` Eli Zaretskii
2017-02-11 23:06       ` Anders Lindgren
2018-05-13 19:44         ` Ryan B
2018-05-15  0:05           ` Noam Postavsky
2018-05-15  8:08             ` Jostein Kjønigsen
2018-05-15 16:50               ` Eli Zaretskii
2018-05-15 18:32                 ` Stefan Monnier
2017-02-11 22:06 ` Ryan B

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=m3poiq11jc.fsf@chopper \
    --to=joakim@verona.se \
    --cc=emacs-devel@gnu.org \
    --cc=public@ryanb.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).