From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Lawrence Subject: Re: Org-Publish of a PDF ?? Date: Wed, 12 Dec 2018 19:51:49 +0100 Message-ID: <87efam7f3u.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:36801) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gX9by-0003cN-Jx for emacs-orgmode@gnu.org; Wed, 12 Dec 2018 13:51:59 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gX9bv-0006GJ-Ua for emacs-orgmode@gnu.org; Wed, 12 Dec 2018 13:51:58 -0500 Received: from mail-qt1-x82e.google.com ([2607:f8b0:4864:20::82e]:37693) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gX9bv-0006DS-MW for emacs-orgmode@gnu.org; Wed, 12 Dec 2018 13:51:55 -0500 Received: by mail-qt1-x82e.google.com with SMTP id z16so21710308qtq.4 for ; Wed, 12 Dec 2018 10:51:55 -0800 (PST) In-Reply-To: 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: David Masterson , Org Mode List Hi David, 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.) Hope that helps! -- Best, Richard