emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Léo Ackermann" <leo.komba@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Large source block causes org-mode to be unusable
Date: Mon, 21 Jun 2021 20:27:52 +0200	[thread overview]
Message-ID: <CAFhsWEgAb_im1WpXp3xsfFxcoahKyycM4GaqRin0SUXxD0gMzg@mail.gmail.com> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 918 bytes --]

Dear all,

I am working in an org-file of reasonable size (<2000 lines): my first
paper written in org-mode. Everything fine (and fast) until I started to
add `#+BEGIN_proof / #+END_proof` within my .org to make my .pdf export
prettier. This caused the editing of the proofs to be very slow: navigation
within the proof is fast but adding/removing any char takes around 4s per
It seems that the fontify function is responsible for that (see
screenshot). As far as I understand, this function tries to fontify the
whole block as soon as a single char is modified. In my case, it then tries
to fontify a whole proof (~4 pages in my .pdf, with many LaTeX formulas)
several times per second...

Is there a way to make this fontify function to act "around my cursor" ?


Here the profiler's report when adding a single char
[image: image.png]
- Emacs 27.2 (doom emacs 2.0.9) (I just updated them)

[-- Attachment #1.2: Type: text/html, Size: 1189 bytes --]

[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 115679 bytes --]

             reply	other threads:[~2021-06-21 18:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 18:27 Léo Ackermann [this message]
2021-06-21 18:43 ` Large source block causes org-mode to be unusable John Hendy
2021-06-21 18:57 ` Sébastien Miquel
2021-06-21 19:22 ` John Kitchin
2021-06-21 19:36   ` John Hendy
2021-06-21 20:41     ` Tom Gillespie
2021-06-22  4:48       ` Tim Cross
2021-06-22  7:54     ` Eric S Fraga
2021-06-22 11:20       ` Léo Ackermann
2021-06-22 12:13         ` Eric S Fraga
2021-06-22 12:32           ` Léo Ackermann
2021-06-22 13:03             ` Eric S Fraga
2021-06-22 13:32               ` Léo Ackermann
2021-06-23 16:40             ` Maxim Nikulin
2021-06-23 19:42               ` Gennady Uraltsev
2021-06-24  7:54                 ` Eric S Fraga
2021-06-26 14:10                   ` Léo Ackermann
2021-06-28  8:28                     ` Sébastien Miquel
2021-06-28 10:42                       ` Eric S Fraga
2021-06-28 10:40                     ` Eric S Fraga
2021-06-22  6:10 ` 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=CAFhsWEgAb_im1WpXp3xsfFxcoahKyycM4GaqRin0SUXxD0gMzg@mail.gmail.com \
    --to=leo.komba@gmail.com \
    --cc=emacs-orgmode@gnu.org \


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