Re: "header-args :eval inline-only" not working

["Berry, Charles" <ccberry@ucsd.edu>]

> On Aug 20, 2017, at 3:21 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> 
> Hello,
> 
> Vikas Rawal <vikaslists@agrarianresearch.org> 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 code blocks including inline blocks.
>> 
>> Isn’t it?
>> 
>> There seems no way of separately controlling inline and other blocks.
> 
> There is. You put :eval never-export on all src blocks and :eval t on
> inline code. Note, however, that inline code might call indirectly src
> blocks, so this can lead to odd situations.
> 

There is also :cache, but it has some gotchas, too.

> What you are missing, probably, is some way to set this globally. Alas,
> `org-export-use-babel' or `org-export-babel-evaluate' is not the answer.
> As suggested in the thread you mentioned earlier, we might as well get
> rid of `org-export-use-babel' altogether. It seems to confuse many users
> and isn't very useful.
> 
> WDYT?

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.


Chuck