On 3/23/11 5:00 PM, "Erik Iverson" wrote:
>
>Try :eval never
>
>http://orgmode.org/org.html#eval
>
>Don't know if that will work, but it sounds promising.
Perfect! Thanks everyone for the help.
--
Ken Williams
Senior Research Scientist
Thomson Reuters
http://labs.thomsonreuters.com
On 3/23/11 1:16 PM, "Eric Schulte" wrote:
> writes:
>>Or perhaps, is there some command to evaluate all blocks in a document
>> that need to be re-evaluated, and save the results back to the buffer?
>>I
>> could do that every time before exporting, maybe.
>>
>
>Fortunately there is such a funct
ken.willi...@thomsonreuters.com wrote:
On 3/23/11 1:16 PM, "Eric Schulte" wrote:
writes:
Or perhaps, is there some command to evaluate all blocks in a document
that need to be re-evaluated, and save the results back to the buffer?
I
could do that every time before exporting, maybe.
Fort
writes:
> On 3/23/11 12:54 PM, "Williams, Ken (TR Corp Tech)"
> wrote:
>
>>
>>On 3/23/11 12:28 PM, "Eric Schulte" wrote:
>>
>>>Thanks for pointing this out, your example doesn't work for me either.
>>>I tracked this down to a problem of not finding the cached results of
>>>named code blocks. I
On 3/23/11 12:54 PM, "Williams, Ken (TR Corp Tech)"
wrote:
>
>On 3/23/11 12:28 PM, "Eric Schulte" wrote:
>
>>Thanks for pointing this out, your example doesn't work for me either.
>>I tracked this down to a problem of not finding the cached results of
>>named code blocks. I've just pushed up a
writes:
> On 3/23/11 12:28 PM, "Eric Schulte" wrote:
>
>>Thanks for pointing this out, your example doesn't work for me either.
>>I tracked this down to a problem of not finding the cached results of
>>named code blocks. I've just pushed up a simple fix for this issue, so
>>caching should now w
On 3/23/11 12:28 PM, "Eric Schulte" wrote:
>Thanks for pointing this out, your example doesn't work for me either.
>I tracked this down to a problem of not finding the cached results of
>named code blocks. I've just pushed up a simple fix for this issue, so
>caching should now work as expected.
writes:
> On 3/23/11 1:46 AM, "Rainer M Krug" wrote:
>
>>
>>When exporting to a pdf, I get the following matrix in the pdf:
>>
>> [,1][,2] [,3] [,4]
>>[1,] 0.5626863 0.8397120 0.9886886 0.2233873
>>[2,] 0.8697064 0.1101432 0.1372992 0.4114674
>>[3,] 0.3548678 0.5658843
Rainer M Krug writes:
> On Wed, Mar 23, 2011 at 3:50 AM, Eric Schulte wrote:
>> Hi Ken,
>>
>> In order for caching to work, the results of the code block must exist
>> in the org-mode file. For example, the following code block will be
>> evaluated when triggered either interactively or during
On 3/23/11 1:46 AM, "Rainer M Krug" wrote:
>
>When exporting to a pdf, I get the following matrix in the pdf:
>
> [,1][,2] [,3] [,4]
>[1,] 0.5626863 0.8397120 0.9886886 0.2233873
>[2,] 0.8697064 0.1101432 0.1372992 0.4114674
>[3,] 0.3548678 0.5658843 0.1608864 0.5809
On Wed, Mar 23, 2011 at 3:50 AM, Eric Schulte wrote:
> Hi Ken,
>
> In order for caching to work, the results of the code block must exist
> in the org-mode file. For example, the following code block will be
> evaluated when triggered either interactively or during export
>
> #+begin_src emacs-li
Hi Ken,
In order for caching to work, the results of the code block must exist
in the org-mode file. For example, the following code block will be
evaluated when triggered either interactively or during export
#+begin_src emacs-lisp :cache yes
(+ 2 2)
#+end_src
alternately, this block will no
Hi,
I'm having some trouble getting ":cache yes" to behave the way I think
it's supposed to. As a test, I have a simple example containing just a
title and one source block:
#+source: testcache
#+begin_src R :cache yes :exports both :results output
dat <- matrix(runif(12), 3, 4)
print(dat)
#+en
13 matches
Mail list logo
