From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kaushal Modi Subject: Re: Allow more export options to be controlled per-subtree Date: Thu, 28 Sep 2017 18:59:19 +0000 Message-ID: References: <87d16aoe2w.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="f403045da19c1979e5055a448238" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59566) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dxe21-00047T-BY for emacs-orgmode@gnu.org; Thu, 28 Sep 2017 14:59:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dxe20-0000N3-0e for emacs-orgmode@gnu.org; Thu, 28 Sep 2017 14:59:33 -0400 Received: from mail-yw0-x234.google.com ([2607:f8b0:4002:c05::234]:54522) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dxe1z-0000L5-Rv for emacs-orgmode@gnu.org; Thu, 28 Sep 2017 14:59:31 -0400 Received: by mail-yw0-x234.google.com with SMTP id w9so1691455ywi.11 for ; Thu, 28 Sep 2017 11:59:31 -0700 (PDT) In-Reply-To: <87d16aoe2w.fsf@nicolasgoaziou.fr> 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: Nicolas Goaziou Cc: Amos Bird , emacs-org list --f403045da19c1979e5055a448238 Content-Type: text/plain; charset="UTF-8" On Thu, Sep 28, 2017 at 2:47 PM Nicolas Goaziou 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 --f403045da19c1979e5055a448238 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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 t= o 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 m= ultiple 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 singl= e subtree.

This proposal will basical= ly allow each Org sub-tree to get all the export options the whole Org file= gets; making sub-tree export a more prime feature.
=C2=A0=
AFAIC this variable could not exist.<= br>

I didn't understand that.

[2]:=C2=A0https://raw.g= ithubusercontent.com/kaushalmodi/ox-hugo/master/test/site/content/posts/exp= ort-without-emphasize.md

=
--

Kaushal Modi

--f403045da19c1979e5055a448238--