From: Grant Rettke <gcr@wisdomandwonder.com>
To: Angus M <anguscmelville@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: long code blocks making Org Mode very slow
Date: Thu, 16 Jul 2015 20:10:52 -0500 [thread overview]
Message-ID: <CAAjq1md2j_PBQo0McG7d+wM2r54Jk_Sm259doK7mOAZoDunawg@mail.gmail.com> (raw)
In-Reply-To: <loom.20150715T141602-750@post.gmane.org>
Post a Gist of your file so I can try it out.
What is you value of `org-src-fontify-natively'?
Grant Rettke
--
gcr@wisdomandwonder.com | http://www.wisdomandwonder.com/
“Wisdom begins in wonder.” --Socrates
“All creativity is an extended form of a joke.” --Kay
((λ (x) (x x)) (λ (x) (x x)))
“Life has become immeasurably better since I have been forced to stop
taking it seriously.” --Thompson
On Wed, Jul 15, 2015 at 7:22 AM, Angus M <anguscmelville@gmail.com> wrote:
> I've just discovered that the slow-response is definitely related to font
> locking. If I type M-x font-lock-mode to toggle it off then the typing lag
> problem is solved.
>
> According to the Emacs documentation:
> 'In Emacs 21 and later, turning on font-lock-mode automatically activates
> the new Just-In-Time fontification provided by jit-lock-mode.'
>
> It would appear, therefore, that just-in-time fontification is not taking
> place in the code block with the whole code block being fontified at once -
> and hence the delay.
>
> Any help to confirm this hypothesis and how to enable just-in-time
> fontification in the code block would be appreciated.
>
> Angus M
>
>
next prev parent reply other threads:[~2015-07-17 1:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 18:15 long code blocks making Org Mode very slow Angus M
2015-07-14 19:41 ` Sebastien Vauban
2015-07-14 21:06 ` Angus M
2015-07-14 21:44 ` Nick Dokos
2015-07-14 23:39 ` Angus M
2015-07-15 12:22 ` Angus M
2015-07-17 1:10 ` Grant Rettke [this message]
2015-07-21 11:09 ` Angus M
2015-07-22 1:20 ` Grant Rettke
2015-07-22 10:09 ` Angus M
2015-07-22 12:41 ` Nick Dokos
2015-07-22 23:09 ` Grant Rettke
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAjq1md2j_PBQo0McG7d+wM2r54Jk_Sm259doK7mOAZoDunawg@mail.gmail.com \
--to=gcr@wisdomandwonder.com \
--cc=anguscmelville@gmail.com \
--cc=emacs-orgmode@gnu.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/org-mode.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).