emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Stefan Vollmar <vollmar@nf.mpg.de>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: htmlize slows org export down?
Date: Sun, 14 Jun 2009 08:09:16 +0200	[thread overview]
Message-ID: <C510CF50-C29E-4AB2-8F11-A9B9C519ACD6@gmail.com> (raw)
In-Reply-To: <87C7186D-FC37-4136-8D39-888AA67340FA@nf.mpg.de>


On Jun 13, 2009, at 10:33 PM, Stefan Vollmar wrote:

> Hello,
>
> I am currently writing a tutorial on Python for beginners, and I  
> have numerous paragraphs like this:
>
> #+BEGIN_SRC python
> from xturtle import *
> ...
> raw_input()
> #+END_SRC
>
> Using version 1.36 of htmlize.el (already compiled) this will be  
> rendered beautifully when exporting to HTML. However, it seems that  
> each of these SRC-blocks with syntax highlighting slows the export  
> down considerably. OK - the whole export still takes less than 5  
> seconds (yes, I know...) - but it is so much faster without the  
> syntax highlighting (and 5 seconds is a long time for a modern  
> machine).

Yes, this can be slow.

> Is there a way to speed this up? Split the document? Use some sort  
> of caching?

I don't know a real way to speed this up.  But you could use

C-u C-u C-c C-e h

to have a background process doing the exporting

Or you could develop the document using begin_example, and
then switch to _src only when it is ready.  You can even write

#+begin_example python

to make the conversion easier.  Or use a function
in org-export-preprocess-hook
to turn all the src block into example blocks, and
remove that hook only when you are done.

- Carsten

>
> Many thanks in advance.
> Warm regards,
> Stefan
> -- 
> Dr. Stefan Vollmar, Dipl.-Phys.
> Max-Planck-Institut für neurologische Forschung
> Gleuelerstr. 50, 50931 Köln, Germany
> Tel.: +49-221-4726-213  FAX +49-221-4726-298
> Tel.: +49-221-478-5713  Mobile: 0160-93874279
> Email: vollmar@nf.mpg.de   http://www.nf.mpg.de
>
>
>
>
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

      reply	other threads:[~2009-06-14  6:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-13 20:33 htmlize slows org export down? Stefan Vollmar
2009-06-14  6:09 ` Carsten Dominik [this message]

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=C510CF50-C29E-4AB2-8F11-A9B9C519ACD6@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=vollmar@nf.mpg.de \
    /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).