emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: David Masterson <dsmasterson@outlook.com>,
	Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Org-Publish of a PDF ??
Date: Wed, 12 Dec 2018 19:51:49 +0100	[thread overview]
Message-ID: <87efam7f3u.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <SN1PR0701MB1853889E44D9BED8F0C77FAFA5A70@SN1PR0701MB1853.namprd07.prod.outlook.com>

Hi David,

David Masterson <dsmasterson@outlook.com> writes:

> When I publish my project, I find that my org files are first generated
> into tex and pdf files in directory1 and then the tex/pdf files are
> copied to directory2.  What I would like is for the tex/pdf files to be
> directly generated in directory2 with no "extras" in directory1.

I think you might be thinking about this the wrong way around.  I may be
wrong about this, as I'm not a heavy user of the publishing framework,
but here's my two cents.

As far as I understand it, the publishing framework is basically
designed around the idea of copying finished products to a desired
location (a directory, either locally or on a webserver).  It's built as
a layer on top of Org's exporters, not as a way to make those exporters
behave differently.  If you want to control the *build* process for the
PDF, as opposed to just where it finally ends up, you probably want to
set options for the latex exporter, not the publishing framework.

In particular, you might want something like:

#+EXPORT_FILE_NAME: builddir/file.tex

in the Org files you're exporting, where builddir is somewhere outside
of your directory1.  (I'm *pretty* sure that will work, but I haven't
tested it.)

Hope that helps!

-- 
Best,
Richard

next prev parent reply	other threads:[~2018-12-12 18:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-12  1:22 Org-Publish of a PDF ?? David Masterson
2018-12-12 18:51 ` Richard Lawrence [this message]
2018-12-13  0:08   ` David Masterson

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=87efam7f3u.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me \
    --to=richard.lawrence@berkeley.edu \
    --cc=dsmasterson@outlook.com \
    --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

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).