From mboxrd@z Thu Jan 1 00:00:00 1970 From: cberry@tajo.ucsd.edu Subject: Re: Selectively export RESULTS Date: Fri, 02 Mar 2012 11:42:03 -0800 Message-ID: <87zkbykcxg.fsf@tajo.ucsd.edu> References: <87ty2aw7ps.fsf@tajo.ucsd.edu> <87ty29eg8n.fsf@tajo.ucsd.edu> <87boohbmch.fsf@gmx.com> <8762epz8uh.fsf@tajo.ucsd.edu> <87mx7ynbbm.fsf@gmx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([208.118.235.92]:51005) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S3YMs-0002ws-NA for emacs-orgmode@gnu.org; Fri, 02 Mar 2012 14:42:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S3YMq-00051L-HB for emacs-orgmode@gnu.org; Fri, 02 Mar 2012 14:42:18 -0500 Received: from plane.gmane.org ([80.91.229.3]:41772) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S3YMq-00051B-AL for emacs-orgmode@gnu.org; Fri, 02 Mar 2012 14:42:16 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1S3YMo-0003kA-Lg for emacs-orgmode@gnu.org; Fri, 02 Mar 2012 20:42:14 +0100 Received: from tajo.ucsd.edu ([137.110.122.165]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 02 Mar 2012 20:42:14 +0100 Received: from cberry by tajo.ucsd.edu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 02 Mar 2012 20:42:14 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Eric Schulte writes: > Matthew Landis writes: > >> tajo.ucsd.edu> writes: >> >>> >>> Eric Schulte 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