From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Lawrence Subject: Re: Export LaTeX file to different directory? Date: Mon, 13 Dec 2010 20:14:11 -0800 Message-ID: <871v5lgfe4.fsf@berkeley.edu> References: <20101213104732.GA283@pc201.uni-germanistik.gwdg.de> <87aak9h68a.fsf@berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from [140.186.70.92] (port=42864 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PSMEh-00071j-DY for emacs-orgmode@gnu.org; Mon, 13 Dec 2010 23:11:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PSMEg-0008Iw-KJ for emacs-orgmode@gnu.org; Mon, 13 Dec 2010 23:11:35 -0500 Received: from lo.gmane.org ([80.91.229.12]:47621) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PSMEg-0008FW-EN for emacs-orgmode@gnu.org; Mon, 13 Dec 2010 23:11:34 -0500 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PSMEe-0004hx-HN for emacs-orgmode@gnu.org; Tue, 14 Dec 2010 05:11:32 +0100 Received: from c-67-164-33-170.hsd1.ca.comcast.net ([67.164.33.170]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 14 Dec 2010 05:11:32 +0100 Received: from richard.lawrence by c-67-164-33-170.hsd1.ca.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 14 Dec 2010 05:11:32 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Jeff Horn writes: > If you want to publish a single project, one that dumps all the files > in the tmp directory, it would publish all files in the source > directory (definitely not what the OP had in mind, I think). If you > publish "only this file," it might work. Yes, there is a "Publish current file" option in the export dispatcher, though I've never used it myself. Using this option with the right combination of :base-directory, :publishing-directory, and :exclude/:include in org-publish-project-alist might do the trick, depending on the OP's exact scenario. Richard