emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: cberry@tajo.ucsd.edu
To: emacs-orgmode@gnu.org
Subject: Re: Selectively export RESULTS
Date: Wed, 29 Feb 2012 12:24:22 -0800	[thread overview]
Message-ID: <8762epz8uh.fsf@tajo.ucsd.edu> (raw)
In-Reply-To: 87boohbmch.fsf@gmx.com

Eric Schulte <eric.schulte@gmx.com> writes:

>>> Does this do what you want?
>>
>> No. 
>>
>> When I put point under the headline and type C-c @ C-c C-e d, it prompts
>> me to evaluate each of the blocks, and when I answer 'no' to each, it
>> produces a document that omits the previously computed results.
>>
>> What I want is to grab *existing* results blocks and use them. 
>>
>> And if at a later date some of those results blocks have changed, when I
>> again put point under the headline and type C-c @ C-c C-e d, I'd like
>> the newer blocks to be updated.
>>
>> The computations in some blocks run for many minutes, so it is
>> impractical to recompute them every time I want to tweak the format of a
>> document that depends on them.
>>
>
> Hi Chuck,

Thanks for your reply.

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

With org-confirm-babel-evaluate set to t, it prompts for confirmation of
each and every block/call it encounters, which is a bit tiresome. I can
set this to nil, but the potential for causing mischief by
unintenionally evaluating blocks whose results were OK and needed for a
quick report worries me.

Its pretty clear that the machinery needed to capture results is all
there. If I can find time, I'll trace thru what is going on when cache
yes is set and see if I can  do so more directly.

Chuck
> Best,
>
> Footnotes: 
> [1]  http://orgmode.org/manual/cache.html

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

  reply	other threads:[~2012-02-29 20:25 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 [this message]
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
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=8762epz8uh.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).