From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Problem when EXPORT_FILE_NAME contains a subdirectory Date: Thu, 30 May 2013 14:39:03 +0200 Message-ID: <87obbsfxqw.fsf@gmail.com> References: <87y5ax5y0a.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:43029) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ui28H-0005Km-Vp for emacs-orgmode@gnu.org; Thu, 30 May 2013 08:39:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ui28C-0007IE-SE for emacs-orgmode@gnu.org; Thu, 30 May 2013 08:39:05 -0400 Received: from mail-we0-x235.google.com ([2a00:1450:400c:c03::235]:61329) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ui28C-0007I7-LE for emacs-orgmode@gnu.org; Thu, 30 May 2013 08:39:00 -0400 Received: by mail-we0-f181.google.com with SMTP id u57so183529wes.40 for ; Thu, 30 May 2013 05:39:00 -0700 (PDT) In-Reply-To: <87y5ax5y0a.fsf@gmail.com> (Martin Marier's message of "Wed, 29 May 2013 16:31:17 -0400") 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: Martin Marier Cc: emacs-orgmode@gnu.org Hello, Martin Marier writes: > When trying to export a subtree as PDF in a subdirectory, I get this > error: > ! I can't write on file `test.log'. > > This is using this source: > > * head 1 > :PROPERTIES: > :EXPORT_FILE_NAME: pdf/test.pdf > :END: > Moo Moo Moo. > * head 2 > > This used to work fine with the old exporter. It I remove the > subdirectory : > :EXPORT_FILE_NAME: test.pdf > > Everything works as expected. Is this intended behavior? Is there a > work around that would let me export to a subdirectory? I just fixed a bug around the same area: when providing a relative path, pdf file was produced but not found and process returned an error. Though, the error message wasn't the same. Could you test it again with an updated Org anyway? Regards, -- Nicolas Goaziou