From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: [ANN] Add EXPORT_FILE_NAME keyword
Date: Wed, 21 Dec 2016 10:32:57 +0100
Message-ID: <87tw9xy6d2.fsf@nicolasgoaziou.fr>
References: <87zijqziaf.fsf@nicolasgoaziou.fr>
	<93ae6cda-6077-125c-7bdf-979f197d0573@verizon.net>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:56333)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1cJdGb-0005me-Pz
	for emacs-orgmode@gnu.org; Wed, 21 Dec 2016 04:32:58 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1cJdGY-0002SQ-Ls
	for emacs-orgmode@gnu.org; Wed, 21 Dec 2016 04:32:57 -0500
Received: from relay3-d.mail.gandi.net ([217.70.183.195]:59527)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <mail@nicolasgoaziou.fr>)
	id 1cJdGY-0002SB-FQ
	for emacs-orgmode@gnu.org; Wed, 21 Dec 2016 04:32:54 -0500
In-Reply-To: <93ae6cda-6077-125c-7bdf-979f197d0573@verizon.net> (Charles
	Millar's message of "Tue, 20 Dec 2016 19:25:18 -0500")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Charles Millar <millarc@verizon.net>
Cc: emacs-orgmode@gnu.org

Hello,

Charles Millar <millarc@verizon.net> writes:


> However, I tried to export a subheading with, e.g.
> #+EXPORT_FILE_NAME: /foo/baz,
> and
> the result is /foo/bar.pdf,     not /foo/baz.pdf

Where does "bar" come from?

> This is not the same result that using the PROPERTIES construct in
> a subheading, which will export with the subheading :EXPORT_FILE_NAME:
> /foo/baz, which does generate a short document named /foo/baz.pdf
>
> Should we be able to apply the new #+EXPORT_FILE_NAME: to a subheading
> or does it work only for an entire buffer?

As every keyword (i.e., #+KEYWORD syntax), it applies to the whole
document. However export properties (i.e., :PROPERTY: syntax) override
them.

> Org mode version 9.0.2 (release_9.0.2-132-gc130b2 @
> /usr/local/share/emacs/site-lisp/org-mode/lisp/)
> GNU Emacs 24.4.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5) of
> 2015-03-07 on trouble, modified by Debian
>
> 2. An editorial suggestion for the realted ORGNEWS item which
> currently reads:
>
> Simiralry to ~:EXPORT_FILE_NAME:~ property, this keyword allow to
> specify the name of the output file upon exporting the document. This
> has also an effect on publishing.
>
> be changed along the following lines?
>
> Similar to ~:EPORT_FILE_NAME:~ property, this keyword allows the user
> to specify the name of the output file upon exporting the document.
> This also has an effect on publishing (or "This also effects
> publishing."

Of course. Thank you.


Regards,

-- 
Nicolas Goaziou