emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: "Léo Ackermann" <leo.komba@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Large source block causes org-mode to be unusable
Date: Mon, 21 Jun 2021 13:43:36 -0500	[thread overview]
Message-ID: <CA+M2ft-YYD7tqbWsb0FsQvOgP6MZwr2n7sKS6mG0hS3xwwQkmg@mail.gmail.com> (raw)
In-Reply-To: <CAFhsWEgAb_im1WpXp3xsfFxcoahKyycM4GaqRin0SUXxD0gMzg@mail.gmail.com>


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

Seems known, assuming this is the same thing. I have not experienced the
phenomenon or used proof blocks, so I'm just going by google-fu matching
(which finds a lot):

https://emacs.stackexchange.com/questions/46561/org-mode-9-too-slow-with-long-code-blocks
https://emacs.stackexchange.com/questions/62376/slow-markdown-mode-as-emacs-spends-lots-of-time-fontifying
https://emacs.stackexchange.com/questions/46110/help-needed-to-debug-very-slow-markdown-mode
https://www.reddit.com/r/emacs/comments/c28svb/has_emacs_always_been_this_slow_at_highlighting/
https://lists.gnu.org/archive/html/emacs-orgmode/2015-07/msg00215.html

As with all things like this, I'd work through the old information first to
understand the true problem, if any improvements/workarounds exist, etc.
Then this lands in some bucket of outcomes:
- it's a novel find and therefore a bug (due diligence searching says this
is not the case)
- it's known bad, but not addressed (due to time or inability), but it can
be worked around (nuggets exist in the links above as well as other results
if you search "emacs fontify proof block slow")
- a true "fix" is possible, in which case this would require pinpointing
the exact problem and asking for alternatives or proposing a better/faster
way to fontify


Hope that helps,
John

P.S. This looks independent to Org, so I'm not sure if this is the best
place for the eventual resolution as this may have nothing to do with Org?
I'm no emacs guru, but from my skim I'm guessing org just pulls in some
other package vs. having it's own fontification engine.

On Mon, Jun 21, 2021 at 1:31 PM Léo Ackermann <leo.komba@gmail.com> wrote:

> 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
> char.
> 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" ?
>
> Best,
> Leo
>
> --
> Here the profiler's report when adding a single char
> [image: image.png]
>  Spec.
> - Emacs 27.2 (doom emacs 2.0.9) (I just updated them)
>
>
>

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

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

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

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 18:27 Léo Ackermann
2021-06-21 18:43 ` John Hendy [this message]
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:
  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=CA+M2ft-YYD7tqbWsb0FsQvOgP6MZwr2n7sKS6mG0hS3xwwQkmg@mail.gmail.com \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=leo.komba@gmail.com \
    --subject='Re: Large source block causes org-mode to be unusable' \
    /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

Code repositories for project(s) associated with this 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).