[O] htmlize and #+INCLUDE:

2012-11-01 Thread Fabrice Popineau
Hi all, Is there something special to do for htmlize to process an #+INCLUDE'd source file ? Up to now, it seems to ignore it. I'm using the new exporter. Besides this, as far as I Can see, I have to use : #+BEGIN_SRC java but #+INCLUDE: file java Why to use a colon in one case and not in the

Re: [O] htmlize and #+INCLUDE:

2012-11-01 Thread Nicolas Goaziou
Hello, Fabrice Popineau fabrice.popin...@gmail.com writes: Is there something special to do for htmlize to process an #+INCLUDE'd source file ? No. Besides this, as far as I Can see, I have to use : #+BEGIN_SRC java but #+INCLUDE: file java It's #+INCLUDE: file src java Why to use a

Re: [O] htmlize and #+INCLUDE:

2012-11-01 Thread Fabrice Popineau
Is there something special to do for htmlize to process an #+INCLUDE'd source file ? No. Do you mean that it should work out of the box or that it is not working at all? Because for me: - I can htmlize src blocks (with BEGIN_SRC) - I can highlight src blocks with syntaxhighlighter (by

Re: [O] htmlize and #+INCLUDE:

2012-11-01 Thread Nicolas Goaziou
Fabrice Popineau fabrice.popin...@gmail.com writes: Given the fact that '#+INCLUDE: file src java' is expanded into an src block, I assume that htmlize should apply there too. Am I wrong? I think you're correct. A quick test shows me fontification is fine. Do you have an ECM to show the

Re: [O] htmlize and #+INCLUDE:

2012-11-01 Thread Fabrice Popineau
Thanks for the confirmation. There is no problem. It was me doing it wrong. It works ok now. I just have to chose between syntaxhighlighter, google code prettify or htmlize. I tend to prefer htmlize (probably more flexible as I can hack elisp code) but there is thing about using my current theme