From: cberry@tajo.ucsd.edu
To: emacs-orgmode@gnu.org
Subject: Re: Selectively export RESULTS
Date: Fri, 02 Mar 2012 11:42:03 -0800 [thread overview]
Message-ID: <87zkbykcxg.fsf@tajo.ucsd.edu> (raw)
In-Reply-To: 87mx7ynbbm.fsf@gmx.com
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
|
|
| #+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
next prev parent reply other threads:[~2012-03-02 19:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 5:04 Selectively export RESULTS cberry
2012-02-29 7:05 ` Thomas S. Dye
2012-02-29 16:50 ` cberry
2012-02-29 17:06 ` Eric Schulte
2012-02-29 20:24 ` cberry
2012-03-02 17:24 ` Matthew Landis
2012-03-02 17:48 ` Eric Schulte
2012-03-02 18:33 ` Matthew Landis
2012-03-02 19:33 ` Eric Schulte
2012-03-02 20:12 ` Matthew Landis
2012-03-02 20:20 ` Eric Schulte
2012-03-03 10:43 ` Sebastien Vauban
2012-03-03 14:52 ` Achim Gratz
2012-03-03 23:01 ` Sebastien Vauban
2012-03-04 10:37 ` Achim Gratz
2012-03-04 20:44 ` Sebastien Vauban
2012-03-02 19:42 ` cberry [this message]
2012-03-02 20:26 ` Eric Schulte
2012-03-02 21:08 ` cberry
2012-03-02 21:26 ` Nick Dokos
2012-03-02 21:35 ` cberry
2012-03-02 23:01 ` Nick Dokos
2012-03-02 17:59 ` Christophe Pouzat
2012-03-02 18:53 ` Matthew Landis
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=87zkbykcxg.fsf@tajo.ucsd.edu \
--to=cberry@tajo.ucsd.edu \
--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).