From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kaushal Modi Subject: Re: Cannot get the EXPORT_FILE_NAME override to work Date: Thu, 04 May 2017 18:28:15 +0000 Message-ID: References: <871ss44lud.fsf@alphaville.usersys.redhat.com> <87fugk34st.fsf@alphaville.usersys.redhat.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=f403045e9d1c586e01054eb6f022 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49698) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1d6LUL-0007hX-9z for emacs-orgmode@gnu.org; Thu, 04 May 2017 14:28:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1d6LUK-0007kZ-Ex for emacs-orgmode@gnu.org; Thu, 04 May 2017 14:28:29 -0400 Received: from mail-lf0-x229.google.com ([2a00:1450:4010:c07::229]:35154) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1d6LUK-0007jm-70 for emacs-orgmode@gnu.org; Thu, 04 May 2017 14:28:28 -0400 Received: by mail-lf0-x229.google.com with SMTP id j1so12971847lfh.2 for ; Thu, 04 May 2017 11:28:28 -0700 (PDT) In-Reply-To: <87fugk34st.fsf@alphaville.usersys.redhat.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" To: Nick Dokos , emacs-orgmode@gnu.org --f403045e9d1c586e01054eb6f022 Content-Type: text/plain; charset=UTF-8 On Thu, May 4, 2017 at 1:34 PM Nick Dokos wrote: > I meant that this works with the property set in the subtree. > Ah, I understand now. So add the EXPORT_FILE_NAME property to each subtree, and then do > > C-c C-e C-s h h > > *for each subtree of interest*. Got it. So the EXPORT_FILE_NAME property is exclusive to subtree scope exporting. Even though a tag is present on only one subtree, exporting by selecting that tag will not do the same thing. (I assumed, hoped that would happen :)) > You could probably org-map your way > through the subtrees and export each one by calling > > (org-export-as 'html t) > > N.B. the subtreep setting in this call. > org-map is a golden suggestion! I'll dive into that. All said, looks like ox-publish misses an ":export_file_name" option. Don't you think? -- Kaushal Modi --f403045e9d1c586e01054eb6f022 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Thu, May 4,= 2017 at 1:34 PM Nick Dokos <ndokos@= gmail.com> wrote:
I meant = that this works with the property set in the subtree.
=
Ah, I understand now.

So add the EXPORT_FILE_NAME property to each subtree, and then do

=C2=A0 C-c C-e C-s h h

*for each subtree of interest*.

Got it. So= the EXPORT_FILE_NAME property is exclusive to subtree scope exporting. Eve= n though a tag is present on only one subtree, exporting by selecting that = tag will not do the same thing. (I assumed, hoped that would happen :))
=C2=A0
You could probably org-ma= p your way
through the subtrees and export each one by calling

=C2=A0 =C2=A0(org-export-as 'html t)

N.B. the subtreep setting in this call.

org-map is a golden suggestion! I'll dive into that.

All said, looks like ox-publish misses an ":export_file_name&q= uot; option. Don't you think?=C2=A0
-= -

Kaushal = Modi

--f403045e9d1c586e01054eb6f022--