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

2016-10-03 Thread Grant Rettke
On Mon, Oct 3, 2016 at 8:22 PM, William Denton wrote: > There's always something new to learn in Org---and something new to be > learned from this mailing list. Never evaluating on export or tangle is my favorite way, too:

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

2016-10-03 Thread William Denton
On 29 September 2016, Charles C. Berry 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. My sincere

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

2016-10-01 Thread 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

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

2016-09-29 Thread Charles C. Berry
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

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

2016-09-29 Thread William Denton
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. I have a mix of source blocks, and all of a sudden the code began to appear in the PDF when all I