From mboxrd@z Thu Jan 1 00:00:00 1970 From: Suvayu Ali Subject: Re: export_file_name problem with new exporter Date: Fri, 7 Dec 2012 13:50:19 +0100 Message-ID: <20121207125019.GM4294@kuru.dyndns-at-home.com> References: <20121207122921.GL4294@kuru.dyndns-at-home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([208.118.235.92]:48635) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TgxNw-00020O-G2 for emacs-orgmode@gnu.org; Fri, 07 Dec 2012 07:50:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TgxNq-0003qQ-JZ for emacs-orgmode@gnu.org; Fri, 07 Dec 2012 07:50:32 -0500 Received: from mail-ea0-f169.google.com ([209.85.215.169]:37525) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TgxNq-0003qG-9t for emacs-orgmode@gnu.org; Fri, 07 Dec 2012 07:50:26 -0500 Received: by mail-ea0-f169.google.com with SMTP id a12so198759eaa.0 for ; Fri, 07 Dec 2012 04:50:25 -0800 (PST) Content-Disposition: inline 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Alan Schmitt Cc: emacs-orgmode@gnu.org On Fri, Dec 07, 2012 at 01:38:50PM +0100, Alan Schmitt wrote: > Suvayu Ali writes: > > > On Fri, Dec 07, 2012 at 11:27:40AM +0100, Alan Schmitt wrote: > >> Hello, > >> > >> I have "#+EXPORT_FILE_NAME: ~/tmp/jsseccloud.tex" in an org file, but > >> when I export it (either to beamer or to latex), it's using the name of > >> the file instead of the given file name. > >> > >> Am I doing something wrong here? > >> > > > > As far as I am aware, that works for subtree export only. > > Ah, this is problematic. I need to change the file name for two reasons: > - the org file name has spaces in it, and latexmk fails when processing > it > - processing the file creates a bunch of files that clobber my org > directory, so I want the created files to be out of the way > > If someone has suggestions on how to deal with these issues, I'd gladly > try them. > You could try the publishing facilities in Org. (info "(org)Publishing") -- Suvayu Open source is the future. It sets us free.