Thank you Jonas !
Jean-Christophe
> On Oct 25, 2017, at 21:51, Jonas Bernoulli wrote:
>
> This was discussed here: https://github.com/hniksic/emacs-htmlize/issues/7.
This was discussed here: https://github.com/hniksic/emacs-htmlize/issues/7.
I tried to export to html and org told me to first install htmlize (
https://github.com/hniksic/emacs-htmlize).
I tried to find an emacs-htmlize in the package list, and found nothing, so I
went to the github page and since saw it was a seemingly normal el package
called htmlize I checked agai
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 wi
Fabrice Popineau 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 problem?
Regards,
> > 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
Hello,
Fabrice Popineau 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 colon in one case
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 ot
Hi Bastien
I actually wrote an ant script that controls the off-line publishing.
It's fairly simple, assuming ELPA packages installed in ~/.emacs.d/elpa
Another important thing to note is that font-lock-mode is not enabled by default
in --batch mode. So I ended up writing an extra .el file that
Bastien writes:
> Dmitri Makarov writes:
>> It should be easy to include such a command in a makefile or build.xml and
>> automatically locate the latest installation of necessary packages rather
>> than explicitly specifying the path.
That's what BTEST_POST is there for in the build system, you
Hi Dmitri,
Dmitri Makarov writes:
> If anyone interested, it's easy to explicitly load the required ELPA
> packages in batch mode. For example, the following command loads htmlize
> for publishing org files in batch mode
>
> emacs --batch -l ~/.emacs.d/init.el --eval "(progn (add-to-list 'load-
If anyone interested, it's easy to explicitly load the required ELPA packages
in batch mode. For example, the following command loads htmlize for publishing
org files in batch mode
emacs --batch -l ~/.emacs.d/init.el --eval "(progn (add-to-list 'load-path
\"~/.emacs.d/elpa/htmlize-20120616.171
Hi all,
I'm having a problem with offline exports.
If I run emacs in --batch mode like this
emacs -batch -l ~/.emacs.d/init.el -eval '(org-publish-all)'
it doesn't seem to load the packages installed by the ELPA package manager.
In particular it doesn't load htmlize package and also loads the bu
13 matches
Mail list logo
