Re: [O] Bug? org-export-babel-evaluate setting breaks :exports results

[Grant Rettke]

This setting is one of the gems for developing a personal workflow.

My workflow is to never evaluate during export because I want the
document to serve as the "master" or the "one source of truth" that is
stored in version control.

The other perspective is never to store it which is what some people want, too!
Sincerely,

Grant Rettke


On Thu, Sep 29, 2016 at 3:34 PM, Charles C. Berry <address@hidden> wrote:
> On Thu, 29 Sep 2016, William Denton wrote:
>
>> I'm working on a big Org file on a slow machine, so I set
>> org-export-babel-evaluate to nil so exporting to PDF just generates the file
>> from what's in the buffer, without doing any calculating.
>>
>
> Actually it does a lot LESS than that.
>
> The docstring notes that:
>
> "When set to nil no code will be evaluated as part of the export
> process and no header argumentss will be obeyed."
>
> and advises:
>
> "Users who wish to avoid evaluating code on export should use the header
> argument ‘:eval never-export’."
>
> which sounds like what you wanted.
>
> Chuck