From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Ken Mankoff <mankoff@gmail.com>
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 17:59:21 +0100 [thread overview]
Message-ID: <87a8jkoec6.fsf@ucl.ac.uk> (raw)
In-Reply-To: <878addc2b6b14ce99e907921f0985d24@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> (Ken Mankoff's message of "Fri, 20 May 2016 16:45:03 +0000")
On Friday, 20 May 2016 at 16:45, Ken Mankoff wrote:
> Eric: You're running something newer (by date) than the commit which
> changed the behavior, which was:
>
> ec615b1 - Fix `org-export-babel-evaluate' handling (2016-04-28)
>
> But with all the branches in git, I don't know if you have that commit
> or not. Anyway, I'm not sure why it works for you. It doesn't appear
> to work for John and I the way it used to. Do you have a global "eval:
> no" set somewhere?
I do have that commit incorporated in the version I am running from what
I see in the git log.
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.
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.92.1, Org release_8.3.4-775-g3308a5
next prev parent reply other threads:[~2016-05-20 18:31 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 [this message]
2016-05-20 17:06 ` Ken Mankoff
[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=87a8jkoec6.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=mankoff@gmail.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).