From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Robert Klein <kleinrob@mpip-mainz.mpg.de>
Cc: emacs-orgmode@gnu.org, Eric Schulte <eric.schulte@gmx.com>
Subject: Re: Publishing using the new exporter
Date: Sat, 06 Oct 2012 13:17:40 +0200 [thread overview]
Message-ID: <87a9vz7stn.fsf@gmail.com> (raw)
In-Reply-To: <50609817.705@mpip-mainz.mpg.de> (Robert Klein's message of "Mon, 24 Sep 2012 19:27:51 +0200")
Hello,
> Another issue I encountered, when publishing(!) to pdf, the resulting
> pdfs didn't have any images. This is probably caused by the images
> beind created in :base-directory and the pdf being created in
> :publishing-directory
Indeed.
Eric: Is there any mechanism to force (automatically) Babel code to
generate files in a given publishing directory instead of the current
directory (notwithstanding :dir argument)?
Ideally, I would like to provide publishing-directory as an optional
argument to `org-export-blocks-preprocess', since it is the only
interface between the export engine and Babel.
Any opinion on this?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2012-10-06 11:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 9:57 Publishing using the new exporter Robert Klein
2012-09-24 10:25 ` Nicolas Goaziou
2012-09-24 15:57 ` Nick Dokos
2012-09-24 17:25 ` Achim Gratz
2012-09-24 17:27 ` Robert Klein
2012-09-25 7:16 ` Robert Klein
2012-09-25 10:58 ` Nicolas Goaziou
2012-09-25 20:54 ` Nicolas Goaziou
2012-10-06 11:17 ` Nicolas Goaziou [this message]
2012-10-06 14:52 ` Robert Klein
2012-10-06 17:48 ` Nicolas Goaziou
2012-10-07 13:21 ` Robert Klein
2012-10-08 12:55 ` Nicolas Goaziou
2012-10-08 16:05 ` Robert Klein
2012-10-08 16:49 ` Nicolas Goaziou
2012-10-08 17:36 ` Robert Klein
2012-10-08 17:46 ` Suvayu Ali
2012-10-09 5:06 ` Robert Klein
2012-10-09 10:07 ` Robert Klein
2012-10-10 16:59 ` Nicolas Goaziou
2012-10-10 19:15 ` Robert Klein
2012-10-11 21:55 ` Nicolas Goaziou
2012-10-15 9:35 ` Robert Klein
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=87a9vz7stn.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=eric.schulte@gmx.com \
--cc=kleinrob@mpip-mainz.mpg.de \
/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).