emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: "Eric Schulte" <schulte.eric@gmail.com>
To: Ista Zahn <izahn@psych.rochester.edu>
Cc: Emacs-orgmode mailing list <emacs-orgmode@gnu.org>
Subject: Re: org-babel caching question
Date: Sun, 19 Sep 2010 15:50:00 -0600	[thread overview]
Message-ID: <87tylle714.fsf@gmail.com> (raw)
In-Reply-To: AANLkTimuMedHuXojBr6hMz2214kYokcCcwitR7ZVj7T6@mail.gmail.com

Hi Ista,

You're correct, currently the caching mechanism employed by Babel only
checks that the same code blocks are used to assign variable, and
doesn't check that the results of those code blocks are the same.

I'll look into what would be required to include variable values in
cache hash calculation.  Any fix to this will require changing when
variable references are resolved and will most likely involve slight
changes to many of the language-specific file, and therefore may take
some time to implement.

Thanks for raising this issue.

Best -- Eric

Ista Zahn <izahn@psych.rochester.edu> writes:

> Hi all,
> I am just starting to get org-babel figured out, but I've run into an
> issue that I could use help with. Basically, with :cache yes turned
> on, subsequent code blocks to not pick up changes in earlier code
> blocks. I would like to know if there is a way to make org babel pick
> up these changes. An example follows.
>
> ---8<------------------begin example------------------8<---
> Test org-babel caching mechanism
>
> * Instructions
> 1. Assign the value 1 to variable a in source block1.
> 2. Run org-babel-execute-buffer.
> 3. Change variable a by assigning it the value 2 in source block1.
> 4. Run org-babel-execute-buffer, and notice that a is still equal to
> 1, 2 in source block2, when it "should" be 2, 2.
>
> * Create R object "a"
> #+srcname block1
> #+begin_src R :session R1 :cache yes
> a <- 1
> #+end_src
>
> * Change the value of "a"
> #+srcname block2
> #+begin_src R :session R1 :cache yes
> a <- c(a, 2)
> #+end_src
>
> * Commentary
> It appears that the org-babel caching mechanism does not notice that
> input values have changed. This is inconvenient, because if I make a
> mistake in an earlier code block I have to turn caching off in order
> to get the values to be updated in subsequent code blocks. Is there
> any way to make babel check to see if the input values have changed?
>
> ---8<------------------end example------------------8<---

     prev parent reply	other threads:[~2010-09-19 21:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-18 16:17 org-babel caching question Ista Zahn
2010-09-19 21:50 ` Eric Schulte [this message]

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=87tylle714.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=izahn@psych.rochester.edu \
    /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

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).