From: Grant Rettke <gcr@wisdomandwonder.com>
To: "Charles C. Berry" <ccberry@ucsd.edu>
Cc: William Denton <wtd@pobox.com>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Bug? org-export-babel-evaluate setting breaks :exports results
Date: Sat, 1 Oct 2016 14:10:34 -0500 [thread overview]
Message-ID: <CAAjq1mdA8LeZ7UqehMDSb+zjqH8+h4BT=bV_6DR6cTY6C9n6rQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.OSX.2.20.1609291330500.1548@charles-berrys-macbook.local>
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 <ccberry@ucsd.edu> 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
next prev parent reply other threads:[~2016-10-01 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 17:23 Bug? org-export-babel-evaluate setting breaks :exports results William Denton
2016-09-29 20:34 ` Charles C. Berry
2016-10-01 19:10 ` Grant Rettke [this message]
2016-10-04 1:22 ` William Denton
2016-10-04 2:49 ` Grant Rettke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAjq1mdA8LeZ7UqehMDSb+zjqH8+h4BT=bV_6DR6cTY6C9n6rQ@mail.gmail.com' \
--to=gcr@wisdomandwonder.com \
--cc=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=wtd@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).