emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Leo Okawa Ericson <git@relevant-information.com>
To: emacs-orgmode@gnu.org
Cc: Leo Okawa Ericson <leo@relevant-information.com>
Subject: [PATCH 0/1] Add option to delay fontification of source blocks
Date: Thu, 25 Mar 2021 18:43:40 +0100	[thread overview]
Message-ID: <20210325174341.104985-1-git@relevant-information.com> (raw)

From: Leo Okawa Ericson <leo@relevant-information.com>

I tried sending this patch once before, but I think it got caught as spam so I'm
trying this again.

Fontification of long code blocks can be very slow. The patch (in the reply to
this 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.

There is a trade-off in that there will be no syntax highlightinting when the
user is typing. I don't know how to keep existing fontification so it would be
great if somebody could share a solution to that.

I have signed the copyright papers so that shouldn't be a problem. This is my
first patch submission so any suggestions for improvement are welcome.

Leo Okawa Ericson (1):
  org-src.el: Add option to delay fontification of source blocks

 lisp/org-src.el | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)


             reply	other threads:[~2021-03-28  1:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25 17:43 Leo Okawa Ericson [this message]
2021-03-25 17:43 ` [PATCH 1/1] org-src.el: Add option to delay fontification of source blocks Leo Okawa Ericson
2021-04-25  3:48 ` [PATCH 0/1] " Timothy
  -- strict thread matches above, loose matches on Subject: below --
2021-03-25 18:25 leo
2021-04-25  3:49 ` Timothy
2021-03-25 17:19 Leo Okawa Ericson
2021-03-29  5:03 ` Kyle Meyer
2021-04-02 12:44   ` Leo Okawa Ericson
2021-04-25  3:48     ` 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=20210325174341.104985-1-git@relevant-information.com \
    --to=git@relevant-information.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=leo@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).