From: Ken Mankoff <mankoff@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: exporting documents w/ babel results w/o evaluating babel blocks
Date: Fri, 20 May 2016 13:06:44 -0400 [thread overview]
Message-ID: <m2h9dsmzff.fsf@client-75-102-66-133.mobility.psu.edu> (raw)
In-Reply-To: <87a8jkoec6.fsf@ucl.ac.uk>
Hi Eric,
On 2016-05-20 at 12:59, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> When I export, org asks whether to evaluate the code block and I
> respond with no. The existing results block is therefore exported but
> not changed. If I say yes, a new results block is generated and
> exported (and I can tell because it is different to what was there
> before).
>
> I have org-export-babel-evaluate set to t but also
> org-confirm-babel-evaluate to t.
Thanks for clarifying your workflow. That seems to work for a small example. But what would you do if you had a manuscript with 100 code blocks in it? And in general you're exporting it a lot without changing anything in code, just editing the non-code text. But occasionally you want to modify a code block (and its results) too?
In the above scenario, I used to edit the code, and =C-c C-c= it manually to get the updates into the results. When I exported the document (C-e l l), it would export in ~1 second (even a >100 page document) and not prompt me about executing code blocks.
-k
next prev parent reply other threads:[~2016-05-20 17:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 15:57 exporting documents w/ babel results w/o evaluating babel blocks Ken Mankoff
2016-05-20 16:14 ` John Hendy
2016-05-20 16:45 ` Ken Mankoff
2016-05-20 17:25 ` John Hendy
[not found] ` <878addc2b6b14ce99e907921f0985d24@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-05-20 16:59 ` Eric S Fraga
2016-05-20 17:06 ` Ken Mankoff [this message]
[not found] ` <b29fde01938940d3b115abd9b257dc57@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-05-20 17:11 ` Eric S Fraga
2016-05-20 17:23 ` John Hendy
2016-05-20 17:38 ` Ken Mankoff
2016-05-20 17:32 ` Ken Mankoff
2016-05-20 18:46 ` Nick Dokos
2016-05-20 21:20 ` Charles C. Berry
2016-05-21 19:01 ` Nick Dokos
2016-05-22 19:58 ` John Hendy
2016-05-22 21:52 ` Charles C. Berry
2016-05-23 18:27 ` Nick Dokos
2016-05-23 18:34 ` John Hendy
2016-05-23 20:08 ` Charles C. Berry
2016-05-24 1:34 ` Grant Rettke
2016-05-24 10:17 ` Andreas Kiermeier
2016-05-24 14:32 ` Ista Zahn
2016-05-24 15:09 ` Anthony Cowley
2016-05-24 15:48 ` Charles C. Berry
2016-05-24 15:53 ` Charles C. Berry
2016-05-20 23:06 ` Ken Mankoff
[not found] <0e207e1cbcc44453b29eea98ca5ebe05@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-05-20 16:13 ` Eric S Fraga
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=m2h9dsmzff.fsf@client-75-102-66-133.mobility.psu.edu \
--to=mankoff@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
/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).