Re: Selectively export RESULTS

[cberry@tajo.ucsd.edu]

cberry@tajo.ucsd.edu writes:

inline correction below.

> Eric Schulte <eric.schulte@gmx.com> writes:
>
>> Matthew Landis <landis@isciences.com> writes:
>>
>>>  <cberry <at> tajo.ucsd.edu> writes:
>>>
>>>> 
>>>> Eric Schulte <eric.schulte <at> gmx.com> writes:
>>>> 
>>>> >>> Does this do what you want?
>>>
>>>> >
>>>> > Have you looked at the :cache header argument [1], from my understanding
>>>> > of your use case it should be exactly what you are after.
>>>> >
>>>> 
>>>> Its a step in the right direction.
>>>> 
>>>> It seems I have to set :cache yes on every block I use before I invoke
>>>> it. My attempt to use a buffer-wide PROPERTY setting for cache did not
>>>> pan out. 
>>>> 
>>
>> Were these technical problems with the implementation of :cache, or
>> logistical problems specific to your organization of code blocks?
>>
> [rest deleted]
>
> Eric,
>
> your response is threaded as a reply to Matthew, but here you have
> replied to my comment about buffer wide PROPERTY setting of :cache.
>
> Here is an example of the difficulty I face:
>
> ,----
> | #+property: :cache yes
> | 

Of course that should have been 


#+property: cache yes

but the result below is the same.

Chuck

> | 
> | #+name: Ablock
> | #+begin_src emacs-lisp :results value :exports both 
> |   (current-time-string)
> | #+end_src
> | 
> | #+results[2ca40f0dc0f23e5743133e229d9e8f31b31830c5]: Ablock
> | : Wed Feb 29 11:57:19 2012
> | 
> | 
> | * headline 1
> |   :PROPERTIES:
> |   :cache:   no
> |   :END:
> | 
> | #+CALL: Ablock() :exports results
> | 
> `----
>
> When I place point under the headline and issue 
>
>      C-c @ C-c C-e a
>
> I get 
>
> ,----
> |                               headline 1
> |                               ==========
> | 
> | Author: 
> | Date: 2012-03-02 11:28:54 PST
> | 
> | 
> | 
> | 
> | Fri Mar  2 11:28:52 2012
> | 
> `----
>
> showing that Ablock() actually was executed.
>
> If the :cache setting under 'headline 1' is omitted then no update of
> the time string is performed.
>
> I understand that this behavior might be considered a *feature*, not a
> *bug*. 
>
> Either way, having an easy way to copy results into other parts of a
> document would help me out.
>
> Best,
>
> Chuck

-- 
Charles C. Berry                            Dept of Family/Preventive Medicine
cberry at ucsd edu			    UC San Diego
http://famprevmed.ucsd.edu/faculty/cberry/  La Jolla, San Diego 92093-0901