From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Erik Hetzner <egh@e6h.org>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] Allow passing post-process to org-publish-org-to for use by org-export-to
Date: Wed, 12 Feb 2014 23:55:52 +0100 [thread overview]
Message-ID: <87ppmsos93.fsf@gmail.com> (raw)
In-Reply-To: <874n44s6cl.wl%egh@e6h.org> (Erik Hetzner's message of "Wed, 12 Feb 2014 07:23:06 -0800")
Erik Hetzner <egh@e6h.org> writes:
> 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).
Then you're correct: filters won't help.
> 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.
Not really. If you look at `org-latex-publish-to-pdf' you will see that
publishing is done differently: the binary file is generated, then
published as an attachment.
> 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
> content? Thanks.
Sort of. `org-export-filter-final-output-functions' will get you the
final string, along with the info plist. You can use it to apply
modifications and generate the binary file. The original output can then
be discarded.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-02-12 22:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 7:00 [PATCH] Allow passing post-process to org-publish-org-to for use by org-export-to Erik Hetzner
2014-02-12 13:02 ` Nicolas Goaziou
2014-02-12 15:23 ` Erik Hetzner
2014-02-12 22:55 ` Nicolas Goaziou [this message]
2014-02-13 3:08 ` Erik Hetzner
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=87ppmsos93.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=egh@e6h.org \
--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).