Nicolas Goaziou <m...@nicolasgoaziou.fr> writes: >> Okay, I've done it this way. Took a bit of fiddling since I need the >> project-alist to work in different configurations (i.e. interactively, >> in batch and in batch on a CI machine). Also, the timestamp stuff >> confused me -- org was skipping publication, even though the output file >> had been deleted. > > You can force re-pulication.
Yes, I did. I was confused by the skipping though -- I was expecting make like behaviour -- where the output was checked. Still, it's fixed now. >> #+BIND: org-latex-custom-lang-environments ((clojure "tawny")) >> #+BIND: org-latex-listings t >> >> isn't working at the moment. Source listings are coming out in verbatim. >> Can I set this in the project-alist. From looking at org-latex-src-block >> it would appear not. > > On the development branch, you can add ":latex-listings t" property in > your project definition. In maint branch, you may dynamically bind > `org-latex-listings' around project publishing function call. Okay. Currently, it appears to be that the org-latex-publish-to-pdf isn't respecting :publishing-directory in the project-alist, so I am publishing to latex and compiling by hand from there. I had to do this anyway, because in batch, emacs swallows the latex output which makes errors very hard to detect. Thanks for the help. Phil