From: "Charles C. Berry" <ccberry@ucsd.edu>
To: Ken Mankoff <mankoff@gmail.com>
Cc: emacs-org <emacs-orgmode@gnu.org>
Subject: Re: Bug: org-export-babel-evaluate causes everything to be exported [8.3.4 (release_8.3.4-824-ga02fe8)]
Date: Fri, 20 May 2016 10:29:07 -0700 [thread overview]
Message-ID: <alpine.OSX.2.20.1605201022540.611@charles-berrys-macbook.local> (raw)
In-Reply-To: <m2oa81x91p.fsf@gmail.com>
On Fri, 20 May 2016, Ken Mankoff wrote:
>
> On 2016-05-20 at 07:12, Ken Mankoff <mankoff@gmail.com> wrote:
>> On 2016-05-19 at 23:33, Charles C. Berry <ccberry@ucsd.edu> wrote:
>>> On Thu, 19 May 2016, Ken Mankoff wrote:
>>
>> (setq org-export-babel-evaluate t)
>>
>> #+BEGIN_SRC octave :exports results :cache nil
>> "hello, world"
>> #+END_SRC
>> #+RESULTS:
>> : hello, world
>>
>> Yes, the above appears to work.
Really? I do not see the hash in your results block.
>
> But it doesn't work with sessions. Can you advise what settings to have how I can have the following code in an Org document:
>
> #+BEGIN_SRC python :results output :exports results :session foo :cache nil
> print("hello, world")
> #+END_SRC
> #+RESULTS:
> : hello, world
>
> And easily export that document without evaluating the code?
`:cache yes'
Of course, you must eval at least once with `:cache yes' to set the hash.
Chuck
p.s. I like to use stuff like
: import time
: print(time.strftime("%H:%M:%S"))
in src blocks to do :cache experiments
next prev parent reply other threads:[~2016-05-20 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 0:13 Bug: org-export-babel-evaluate causes everything to be exported [8.3.4 (release_8.3.4-824-ga02fe8)] Ken Mankoff
2016-05-20 0:18 ` Ken Mankoff
2016-05-20 3:33 ` Charles C. Berry
2016-05-20 11:12 ` Ken Mankoff
2016-05-20 11:28 ` Ken Mankoff
2016-05-20 17:29 ` Charles C. Berry [this message]
2016-05-20 17:44 ` Ken Mankoff
2016-05-20 17:48 ` Charles C. Berry
2016-05-20 23:03 ` Ken Mankoff
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=alpine.OSX.2.20.1605201022540.611@charles-berrys-macbook.local \
--to=ccberry@ucsd.edu \
--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).