Re: Allow more export options to be controlled per-subtree

[Kaushal Modi <kaushal.modi@gmail.com>]

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

On Thu, Sep 28, 2017 at 2:47 PM Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:

> Besides the fact that it is not available, is there any incentive to do
> so?


While talking to Amos (now CC'ed on this email) off-list on Gitter chat
regarding the ox-hugo package, he had this test case[1] where he sets
"#+OPTIONS:
*:nil" to prevent the interpretation of Org emphasis chars in that table,
which exports to this Markdown[2], and finally this[3].

Now, we can have a single Org file with multiple sub-trees and each
sub-tree exports to a separate Markdown file. It would not be practical to
globally set "#+OPTIONS: *:nil".

With this proposal implemented, if cases like the Org table linked above
exist, we can disable emphasis interpretation localized only to that single
subtree.

This proposal will basically allow each Org sub-tree to get all the export
options the whole Org file gets; making sub-tree export a more prime
feature.


> AFAIC this variable could not exist.
>

I didn't understand that.

[1]:
https://raw.githubusercontent.com/kaushalmodi/ox-hugo/master/test/site/content-org/single-posts/export-without-emphasize.org
[2]:
https://raw.githubusercontent.com/kaushalmodi/ox-hugo/master/test/site/content/posts/export-without-emphasize.md
[3]: https://ox-hugo.netlify.com/test/posts/export-without-emphasize/

-- 

Kaushal Modi

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