From: "Sébastien Miquel" <firstname.lastname@example.org> To: "Léo Ackermann" <email@example.com>, firstname.lastname@example.org Subject: Re: Large source block causes org-mode to be unusable Date: Mon, 21 Jun 2021 18:57:27 +0000 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <CAFhsWEgAb_im1WpXp3xsfFxcoahKyycM4GaqRin0SUXxD0gMzg@mail.gmail.com> Hi Léo, Léo Ackermann writes: > 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... You can try setting org-highlight-latex-and-related to '(latex) instead of '(native). Even with this setting, latex fontification in special blocks is slow. The reason being that the whole block has the `font-lock-multiline' property, hence every char insertion triggers refontification of the whole block. In the function `org-do-latex-and-related', I commented out the second condition of the `cond' form, which makes calls to `face-at-point'. This yields a significant speedup, and was enough to make things bearable in my cases. You can also try to simplify the latex regexp. If you try these, I'd be interested to hear how much of an improvement theymake. Regards, -- Sébastien Miquel
next prev parent reply other threads:[~2021-06-21 18:58 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 2021-06-21 18:57 ` Sébastien Miquel [this message] 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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).