[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] [PATCH] Allow passing post-process to org-publish-org-to for use
Re: [O] [PATCH] Allow passing post-process to org-publish-org-to for use by org-export-to
Wed, 12 Feb 2014 07:23:06 -0800
Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (Gojō) APEL/10.8 EasyPG/1.0.0 Emacs/24.3 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO)
At Wed, 12 Feb 2014 14:02:12 +0100,
Nicolas Goaziou wrote:
> Erik Hetzner <address@hidden> writes:
> > I have been looking at publishing to HTML using pandoc. Because pandoc
> > requires post-processing to transform the org-mode markdown output to
> > other formats, it is necessary to use the post-process parameter of
> > org-export-to-file.
> > I think this patch makes sense; let me know what you think.
> Thanks for your patch.
> Though, it is not necessary. `post-process' is meant for processing
> after an asynchronous export (e.g., prepare a buffer in the current
> You're looking after a filter. See
> (info "(org) Advanced configuration")
> for more information.
Thanks very much for your response (and ox.el)! I looked at filters,
but concluded they were not appropriate, because pandoc operates on
the file as a whole, and writes to a file, and can return binary
content (for example, if it is generating PDFs). It seemed equivalent
to the way that the latex exporter uses pdflatex to generate a PDF,
and the latex exported uses a post-process function.
I could be wrong, though. It would also be convenient to have access
to the info plist; in fact, I was going to write another email about
having access to the info plist in a post-process filter.
Is there a way to define a filter that operates on the entire content,
is guaranteed to run after everything else, and can handle binary
Sent from my free software system <http://fsf.org/>.