emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: Leo Okawa Ericson <git@relevant-information.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH 0/1] Add option to delay fontification of source blocks
Date: Mon, 29 Mar 2021 01:03:28 -0400	[thread overview]
Message-ID: <87ft0e7dr3.fsf@kyleam.com> (raw)
In-Reply-To: <20210325171941.101077-1-git@relevant-information.com>

Leo Okawa Ericson writes:

> Fontification of long code blocks can be very slow. The patch, which should be
> in another other email, mitigates this by
> adding an option to delay the fontification after the user has become idle by
> using idle timers. This seems to be faster from my limited testing, but I'm not
> sure if something will go horribly wrong because of the timers.

Thanks for the patch.  My initial reaction is that I'm not sure about
adding an idle timer for a particular aspect of fontification.  If we do
go this route, I think the case needs to be made why this spot is
special, and why we don't expect or would reject follow-up patches for
this and that other area.

Have you explored whether jit-lock (e.g., jit-lock-defer-time) helps for
your use case?

  parent reply	other threads:[~2021-03-29  5:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25 17:19 [PATCH 0/1] Add option to delay fontification of source blocks Leo Okawa Ericson
2021-03-25 17:19 ` [PATCH 1/1] org-src.el: " Leo Okawa Ericson
2021-03-29  5:03 ` Kyle Meyer [this message]
2021-04-02 12:44   ` [PATCH 0/1] " Leo Okawa Ericson
2021-04-25  3:48     ` Timothy
  -- strict thread matches above, loose matches on Subject: below --
2021-03-25 17:43 Leo Okawa Ericson
2021-04-25  3:48 ` Timothy
2021-03-25 18:25 leo
2021-04-25  3:49 ` Timothy

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ft0e7dr3.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=git@relevant-information.com \


* 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


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).