From: "Thomas S. Dye" <tsd@tsdye.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [Babel] [Ann] varied updates and improvements
Date: Sat, 1 Jan 2011 11:09:49 -1000 [thread overview]
Message-ID: <9EEC164E-4A7C-4E95-91BC-B543C5A7A034@tsdye.com> (raw)
In-Reply-To: <306D1534-5DF6-4B6F-9AAB-8B28379BF62E@tsdye.com>
[-- Attachment #1.1: Type: text/plain, Size: 1993 bytes --]
Aloha all,
Sorry for the noise. I'm not sure how I was using version 7.01trans
with release_7.4.93, but now that I'm using version 7.4 with that
release, the code below works as expected.
Tom
On Jan 1, 2011, at 10:41 AM, Thomas S. Dye wrote:
> Aloha all,
>
> Code block caching doesn't seem to notice if the value of a variable
> argument has changed. Here is what I get with Org-mode version
> 7.01trans (release_7.4.93.g40264e.dirty) when I run both code blocks
> (I'm expecting caller to recognize that random has changed).
>
> #+srcname: random
> #+begin_src R :cache yes
> runif(3)
> #+end_src
>
> #+results[bbaaac2c187b718287fb9e9b60dc3d096eca28c0]: random
> | 0.292331680655479 |
> | 0.547373940004036 |
> | 0.770326626254246 |
>
>
> #+srcname: caller
> #+begin_src emacs-lisp :var x=random :cache yes
> x
> #+end_src
>
> #+results[9e659075e616e3fc068e697bd3aff9d0bfa0f5d8]: caller
> : 0.707728253444657
>
> Tom
>
> On Oct 21, 2010, at 4:18 AM, Eric Schulte wrote:
>
>> Improved Caching
>> -----------------
>> Code block caches now notice if the value of a variable argument
>> to the code block has changed, if this is the case the cache is
>> invalidated and the code block is re-run. The following example
>> can provide intuition for the new behavior.
>>
>> #+srcname: random
>> #+begin_src R :cache yes
>> runif(1)
>> #+end_src
>>
>> #+results[a2a72cd647ad44515fab62e144796432793d68e1]: random
>> 0.4659510825295
>>
>> #+srcname: caller
>> #+begin_src emacs-lisp :var x=random :cache yes
>> x
>> #+end_src
>>
>> #+results[bec9c8724e397d5df3b696502df3ed7892fc4f5f]: caller
>> 0.254227238707244
>
>
>
> Thomas S. Dye, Ph.D.
> T. S. Dye & Colleagues, Archaeologists, Inc.
> Phone: (808) 529-0866 Fax: (808) 529-0884
> http://www.tsdye.com
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[-- Attachment #1.2: Type: text/html, Size: 5264 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2011-01-01 21:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 14:18 [Babel] [Ann] varied updates and improvements Eric Schulte
2011-01-01 20:41 ` Thomas S. Dye
2011-01-01 21:09 ` Thomas S. Dye [this message]
2011-01-01 21:01 ` Thomas S. Dye
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=9EEC164E-4A7C-4E95-91BC-B543C5A7A034@tsdye.com \
--to=tsd@tsdye.com \
--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).