From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Masterson Subject: Re: Org-Publish of a PDF ?? Date: Thu, 13 Dec 2018 00:08:58 +0000 Message-ID: References: <87efam7f3u.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41569) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gXEZ1-0006KT-MK for emacs-orgmode@gnu.org; Wed, 12 Dec 2018 19:09:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gXEYt-0006nd-LN for emacs-orgmode@gnu.org; Wed, 12 Dec 2018 19:09:12 -0500 Received: from mail-oln040092012069.outbound.protection.outlook.com ([40.92.12.69]:40034 helo=NAM05-BY2-obe.outbound.protection.outlook.com) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gXEYq-0006gX-6x for emacs-orgmode@gnu.org; Wed, 12 Dec 2018 19:09:05 -0500 In-Reply-To: <87efam7f3u.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me> (Richard Lawrence's message of "Wed, 12 Dec 2018 19:51:49 +0100") Content-Language: en-US List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Richard Lawrence Cc: Org Mode List Richard Lawrence writes: > David Masterson 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.) Hmm. That's a possibility. Then, I assume, that, after EXPORT_FILE_NAME is made, the PDF file will be made in the same location. I'll have a look at the exporter options more. I wonder if there is an EXPORT_DIR..? -- David