From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: emacs-orgmode@gnu.org
Subject: Re: Struggling with new exporter
Date: Wed, 24 Sep 2014 12:44:21 +0100 [thread overview]
Message-ID: <87vbod6y5m.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <8738bif2au.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Tue, 23 Sep 2014 23:35:21 +0200")
Nicolas Goaziou <mail@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
prev parent reply other threads:[~2014-09-25 4:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 19:50 Struggling with new exporter Phillip Lord
2014-09-22 20:15 ` Nicolas Goaziou
2014-09-23 8:55 ` Phillip Lord
2014-09-23 21:35 ` Nicolas Goaziou
2014-09-24 11:44 ` Phillip Lord [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=87vbod6y5m.fsf@newcastle.ac.uk \
--to=phillip.lord@newcastle.ac.uk \
--cc=emacs-orgmode@gnu.org \
/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).