From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: org-src-fontify-natively makes things very, very slow
Date: Mon, 21 Mar 2011 23:23:18 +0100 [thread overview]
Message-ID: <80wrjsun8p.fsf@somewhere.org> (raw)
In-Reply-To: 87lj089ze7.fsf@pinto.chemeng.ucl.ac.uk
Hi Eric,
Eric S Fraga wrote:
> going back to the original subject of this thread (although thanks all for
> your inputs on yasnippet ;-), I have started working on a new document and
> am finding the slowdown of navigation (next-line) very annoying. In this
> document, I have two gnuplot source blocks. Navigating through them, I get
> the following results from elp:
>
> next-line 54 5.9466770000 0.1101236481
> previous-line 44 0.4350030000 0.0098864318
> org-encrypt-entries 1 0.000424 0.000424
> org-scan-tags 1 0.000368 0.000368
> org-make-tags-matcher 1 5.1e-05 5.1e-05
> org-activate-plain-links 1 2.4e-05 2.4e-05
> org-raise-scripts 1 2.1e-05 2.1e-05
> org-fontify-meta-lines-and-blocks 1 1.9e-05 1.9e-05
> org-font-lock-hook 1 1.9e-05 1.9e-05
> org-outline-level 5 1.9e-05 3.8e-06
> org-mode-flyspell-verify 14 1.8e-05 1.285...e-06
> org-inlinetask-fontify 1 1.5e-05 1.5e-05
> org-activate-footnote-links 1 1.5e-05 1.5e-05
> org-unfontify-region 1 1.2e-05 1.2e-05
> org-do-emphasis-faces 1 1.2e-05 1.2e-05
> org-activate-angle-links 1 1.2e-05 1.2e-05
> org-activate-dates 1 1.1e-05 1.1e-05
> org-fontify-entities 1 1.1e-05 1.1e-05
>
> From these timings, the font locking doesn't seem to be the issue but maybe
> the overlays are. However, commenting out the code that Sébastien Vauban
> indicated:
>
>> Maybe this is (partly?) due to the overlay I added:
>>
>> #+begin_src emacs-lisp
>> (overlay-put (make-overlay beg1 block-end)
>> 'face 'org-block-background))
>> #+end_src
See http://patchwork.newartisans.com/patch/581/ for a full diff. You can see I
only add *one* overlay: for the background face.
> (well, commenting out the whole condition that includes this code) makes no
> difference at all.
I'm surprised. Good to hear, but as some were finger pointing the overlays,
and as I added one for every block... But, OK, better like that!
For the sake of completeness, know that I first tried to add the background
fontification as a text property, but that made the other properties disappear
(annihilating the native fontification in fact). No a solution, or I did not
try the right way -- which is entirely possible, seen my poor knowledge on
this subject (I have to admit I succeeded by trials and errors).
> So, I turned off =org-src-fontify-natively= and things are back to
> normal: next-line is as fast as previous-line. I can put up without the
> fontification so this is what I am doing now.
>
> However, as it's a pity to lose the native fontification, it would be
> nice to solve this problem in another way. Can anybody suggest any
> other thing to try?
Not that I can think of now. Sorry for not being of any help here.
Best regards,
Seb
--
Sébastien Vauban
next prev parent reply other threads:[~2011-03-21 22:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 13:59 org-src-fontify-natively makes things very, very slow Julian Burgos
2011-03-17 18:28 ` Eric S Fraga
2011-03-17 20:34 ` Sébastien Vauban
2011-03-18 0:11 ` Julian Burgos
2011-03-18 8:38 ` Eric S Fraga
2011-03-18 12:44 ` Julian Burgos
2011-03-19 9:20 ` Sébastien Vauban
2011-03-19 12:28 ` suvayu ali
2011-03-19 20:37 ` Eric S Fraga
2011-03-19 20:34 ` Eric S Fraga
2011-03-20 4:23 ` Le Wang
2011-03-20 19:41 ` Eric S Fraga
2011-03-21 2:37 ` Le Wang
2011-03-21 13:57 ` Eric Schulte
2011-03-21 17:06 ` Eric S Fraga
2011-03-21 22:23 ` Sébastien Vauban [this message]
2011-03-22 9:18 ` Ulf Stegemann
2011-03-29 14:49 ` Matt Lundin
2011-03-29 16:49 ` Eric S Fraga
2011-03-30 7:34 ` Sébastien Vauban
2011-04-28 20:59 ` Carsten Dominik
2011-04-28 23:32 ` Eric S Fraga
2011-04-30 19:45 ` Eric S Fraga
2011-05-01 13:37 ` Carsten Dominik
2011-03-29 14:12 ` Matt Lundin
2011-03-29 16:44 ` Eric S Fraga
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=80wrjsun8p.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).