Hello,
"Berry, Charles" writes:
> Maybe remove the `inline-only' option as a first step.
>
> I have no use for org-export-use-babel, but one thing it does do is
> prevent processing of headers which could be helpful if tricky header
> constructions cause export to fail.
Fair
> On Aug 20, 2017, at 3:21 AM, Nicolas Goaziou wrote:
>
> Hello,
>
> Vikas Rawal writes:
>
>> I am on the latest version on org mode ELPA. It is dated August 18,
>> 2017, so should include the commit you mention.
>
>
>
>> I am on the latest version on org mode ELPA. It is dated August 18,
>> 2017, so should include the commit you mention.
>
> `org-export-use-babel' is from "master" branch. ELPA provides "maint”.
Got it.
>> But this would prevent exporting all code blocks including inline blocks.
>>
>>
Hello,
Vikas Rawal writes:
> I am on the latest version on org mode ELPA. It is dated August 18,
> 2017, so should include the commit you mention.
`org-export-use-babel' is from "master" branch. ELPA provides "maint".
> But this would prevent exporting all
>>
>> I don’t see org-export-use-babel in available options. I cannot customise it.
>>
>> '(org-export-use-babel (quote inline-only))
>>
>> Seems to have no effect. Is that so because, as you say later, users are not
>> supposed to touch this option?
>
> No. You must have an older version
> On Aug 19, 2017, at 7:24 PM, Vikas Rawal
> wrote:
>
>
>>
>> There is a bug in the documentation -- `org-export-babel-evaluate' is
>> obsolete. It should say `org-export-use-babel’.
>
> I don’t see org-export-use-babel in available options. I cannot
>
> There is a bug in the documentation -- `org-export-babel-evaluate' is
> obsolete. It should say `org-export-use-babel’.
I don’t see org-export-use-babel in available options. I cannot customise it.
'(org-export-use-babel (quote inline-only))
Seems to have no effect. Is that so because,
> On Aug 19, 2017, at 6:10 PM, Vikas Rawal
> wrote:
>
>>
>>
>> The first problem is that you have babel code *inside* a macro. Since
>> macros are run after babel executes, nothing will happen.
>
> From the manual: "Org expands macros at the very beginning
>
>
> The first problem is that you have babel code *inside* a macro. Since macros
> are run after babel executes, nothing will happen.
From the manual: "Org expands macros at the very beginning of the export
process.”
These macros run fine if I allow code evaluation. Macro replacement
> On Aug 19, 2017, at 1:36 PM, Vikas Rawal
> wrote:
>
>
>> On 20-Aug-2017, at 12:57 AM, Nicolas Goaziou wrote:
>>
>> Hello,
>>
>> Vikas Rawal writes:
>>
>>> My org-version (latest on org ELPA) is:
> On 20-Aug-2017, at 12:57 AM, Nicolas Goaziou wrote:
>
> Hello,
>
> Vikas Rawal writes:
>
>> My org-version (latest on org ELPA) is: Org mode version 9.0.9
>> (9.0.9-82-gb862c2-elpa @ /Users/vikas/.emacs.d/elpa/org-20170814/)
>>
>>
Hello,
Vikas Rawal writes:
> My org-version (latest on org ELPA) is: Org mode version 9.0.9
> (9.0.9-82-gb862c2-elpa @ /Users/vikas/.emacs.d/elpa/org-20170814/)
>
> The following is not working:
>
> #+PROPERTY: header-args :eval inline-only
>
> ":eval
My org-version (latest on org ELPA) is: Org mode version 9.0.9
(9.0.9-82-gb862c2-elpa @ /Users/vikas/.emacs.d/elpa/org-20170814/)
The following is not working:
#+PROPERTY: header-args :eval inline-only
":eval never-export” works; but ":eval inline-only" does not.
I can deal with this by
13 matches
Mail list logo