emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Nick Dokos <ndokos@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Cannot get the EXPORT_FILE_NAME override to work
Date: Thu, 04 May 2017 18:28:15 +0000	[thread overview]
Message-ID: <CAFyQvY1SQFayfgGojNQJZsyvGpK+2PtWGfgM5_g01SXU+aShCA@mail.gmail.com> (raw)
In-Reply-To: <87fugk34st.fsf@alphaville.usersys.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 848 bytes --]

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
>
>   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

[-- Attachment #2: Type: text/html, Size: 1577 bytes --]

  reply	other threads:[~2017-05-04 18:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-04 15:30 Cannot get the EXPORT_FILE_NAME override to work Kaushal Modi
2017-05-04 15:36 ` Kaushal Modi
2017-05-04 16:40 ` Nick Dokos
2017-05-04 17:02   ` Kaushal Modi
2017-05-04 17:33     ` Nick Dokos
2017-05-04 18:28       ` Kaushal Modi [this message]
2017-05-04 19:56         ` Kaushal Modi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFyQvY1SQFayfgGojNQJZsyvGpK+2PtWGfgM5_g01SXU+aShCA@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).