emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ulf Stegemann <ulf-news@zeitform.de>
To: emacs-orgmode@gnu.org
Subject: Re: org-src-fontify-natively makes things very, very slow
Date: Tue, 22 Mar 2011 10:18:28 +0100	[thread overview]
Message-ID: <zf.upnmxkna4yj.fsf@zeitform.de> (raw)
In-Reply-To: <80wrjsun8p.fsf@somewhere.org>

Hi Sébastien, Eric,

I'm experiencing the same performance problems with recent org-mode.  My
observations are ...

Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> wrote:

> Eric S Fraga wrote:
>>
>> 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.

That's true. It does not make any difference performance-wise.

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

It's true that setting `org-src-fontify-natively' to nil boosts
performance but it's only half the story.  Editing something inside
blocks also has a significant negative influence on display performance.
Removing things like `#+BEGIN_letter' / `#+END_letter' from the file
gets things back to normal for me.

Ulf

  reply	other threads:[~2011-03-22  9:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-17 13:59 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
2011-03-22  9:18                       ` Ulf Stegemann [this message]
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=zf.upnmxkna4yj.fsf@zeitform.de \
    --to=ulf-news@zeitform.de \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: org-src-fontify-natively makes things very, very slow' \
    /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).