From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Schmitt Subject: Re: export_file_name problem with new exporter Date: Thu, 13 Dec 2012 14:50:03 +0100 Message-ID: References: ,<8738zadrpn.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:44603) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tj9Au-0008K4-L0 for emacs-orgmode@gnu.org; Thu, 13 Dec 2012 08:50:13 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tj9As-0001nQ-TC for emacs-orgmode@gnu.org; Thu, 13 Dec 2012 08:50:08 -0500 Received: from mail1-relais-roc.national.inria.fr ([192.134.164.82]:59043) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tj9As-0001jG-Nk for emacs-orgmode@gnu.org; Thu, 13 Dec 2012 08:50:06 -0500 In-reply-to: <8738zadrpn.fsf@gmail.com> 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: Nicolas Goaziou Cc: Alan Schmitt , emacs-orgmode Nicolas Goaziou writes: > There is no #+EXPORT_FILE_NAME: keyword. But there is > an :EXPORT_FILE_NAME: node-property for subtree export. There could be > a #+FILE_NAME: keyword (much like :EXPORT_AUTHOR: and #+AUTHOR). Though, > it is too dangerous to my liking. > > For example, publishing expects the output file to be generated in the > working directory. Using a different export path per file could lead to > much confusion. > > Hence I'd rather not implement it. I understand it. What I actually would like is to be able to specify a different "working directory". Right now it defaults to the directory where the org file is, but it's often not satisfactory (especially when compilation creates additional files). Would this be difficult to add? Thanks, Alan