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

2017-09-30 Thread Kaushal Modi
On Sat, Sep 30, 2017, 1:44 AM Amos Bird wrote: > Hi Kaushal, > > I did, it only works if I export the subtree instead of the whole buffer. > Yes, then I misunderstood. I thought you were trying to export just the subtree. The EXPORT_* subtree properties apply only when you are exporting that subt

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

2017-09-29 Thread Amos Bird
#+OPTIONS: latex:t toc:nil H:3 Hi Kaushal, I did, it only works if I export the subtree instead of the whole buffer. Regards, Kaushal Modi writes: > Hi Amos, > > Regarding your question in the other thread, did you try the below > suggestion? > > On Thu, Sep 28, 2017, 3:19 PM Nicolas Goaziou

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

2017-09-29 Thread Kaushal Modi
Hi Amos, Regarding your question in the other thread, did you try the below suggestion? On Thu, Sep 28, 2017, 3:19 PM Nicolas Goaziou wrote: > > By the way, it is already possible to prevent emphasis in a subtree > export: > > * Subtree > :PROPERTIES: > :EXPORT_OPTIONS: *:nil >

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

2017-09-28 Thread Kaushal Modi
On Thu, Sep 28, 2017 at 3:19 PM Nicolas Goaziou wrote: > I already answered to this problem. Use \star instead of *. It seems > sub-optimal to prevent any emphasis markup because of a single > problematic character. > OK. > I mean this variable doesn't solve any problem. If one doesn't want Or

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

2017-09-28 Thread Nicolas Goaziou
Kaushal Modi writes: > 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

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

2017-09-28 Thread Kaushal Modi
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"

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

2017-09-28 Thread Nicolas Goaziou
Hello, Kaushal Modi writes: > I see that many export options like org-export-with-emphasize, > org-export-with-sub-superscripts cannot be set on per-subtree basis using > properties. [...] > I believe that can be fixed by doing: > > (:with-emphasize "WITH_EMPHASIZE" "*" org-export-with-emp

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

2017-09-28 Thread Kaushal Modi
On Thu, Sep 28, 2017 at 1:28 PM Kaushal Modi wrote: > .. and so on, and then one can have > > :EXPORT_WITH_EMPHASIZE: t > > or > > :EXPORT_WITH_EMPHASIZE: > > in the subtree property. > > Is there a reason why this support wasn't added in the first place? > (Or does a method already exist to allo

[O] Allow more export options to be controlled per-subtree

2017-09-28 Thread Kaushal Modi
Hello, I see that many export options like org-export-with-emphasize, org-export-with-sub-superscripts cannot be set on per-subtree basis using properties. In ox.el, I see: (defconst org-export-options-alist '((:title "TITLE" nil nil parse) (:date "DATE" nil nil parse) (:author "AUTHOR