From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: Selectively export RESULTS Date: Fri, 02 Mar 2012 12:33:58 -0700 Message-ID: <87399qn6ft.fsf@gmx.com> 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 Return-path: Received: from eggs.gnu.org ([208.118.235.92]:34715) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S3YFk-0001h1-9A for emacs-orgmode@gnu.org; Fri, 02 Mar 2012 14:34:57 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S3YFP-0003Gn-Nb for emacs-orgmode@gnu.org; Fri, 02 Mar 2012 14:34:55 -0500 Received: from mailout-us.gmx.com ([74.208.5.67]:45348 helo=mailout-us.mail.com) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1S3YFP-0003GO-I0 for emacs-orgmode@gnu.org; Fri, 02 Mar 2012 14:34:35 -0500 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: Matthew Landis Cc: emacs-orgmode@gnu.org Matthew Landis writes: > Eric Schulte gmx.com> writes: > >> >> Matthew Landis isciences.com> writes: >> >> Have you tried this? The cache header argument has special handling of >> code blocks with sessions to handle such cases. > > Fair enough! I hadn't tried it. But I did just try this example: > > ------------------------------------- > #+TITLE: Super simple example using cache header arguments > #+PROPERTIES: eval no > The above line should be #+PROPERTY: singular. That explains why file-wide settings aren't working for you. > > Here is a really simple example. > > #+begin_src R :session :results silent :exports code :cache yes > x <- rnorm(100) > cat('ran this code block') > #+end_src > > here is code block two. > > #+begin_src R :session :results graphics :exports both :file hist.png :cache yes > hist(x, main = 'A new title' ) > #+end_src > > #+results[1987d49b46ffd8b7263dc04e7c7b5d25f90342aa]: > [[file:hist.png]] > --------------------------------- > Thanks for the example, after working through it I now know what is causing this issue. The first code block will always be run for two reasons. 1. it is run in a session, which means that Babel can not guess at to what state it could be changing internal to the session, so it defaults to the safest option which is allowing the code block to run 2. since this code block returns no results, there is no place for Babel to store the hash key holding the information on the code block and arguments used to produce the results. Remember that Org-mode is nothing more than the text in the file, so without this stored hash, there is no way for Babel to know that the code block was previously run, or that it may have results. For these reasons I would suggest either fixing the properties issue above, which will allow you to set eval to "no" before export when you are content with your current results, or I would suggest that you switch from session based evaluation to explicitly passing the values through Org-mode, which will allow babel to cache results. I will update the ":cache" section of the manual so that it mentions the issues around mixing ":session" and ":cache" header arguments. Best, > > RESULTS: > On 1st export to html, both code blocks are run, and #+results block is *not* > created. > > On 2nd export, both code blocks are run again, counter to my desires. > > IF I run the code blocks interactively first using C-c C-c, the #+results block > is created for the code block 2. After that, subsequent exports run code block > 1 but not code block 2. Again, this is counter to my desires because I want > code block 1 to be ignored as well. I understand why code block 1 is rerun, > because I have :results silent, but I'd rather not have to change that. > Generally, code block 1 is producing large R data.frames which don't need to be > viewed anywhere. > >> Are you requesting a new option to :cache, such that even if the code >> block has changes the old results are used anyway? > > Sort of. I think I'm asking for a file wide option to decide whether to run any > code blocks, or just do the export based on whatever is currently existing in > the #+results blocks. > > As in this example, I tried #+PROPERTIES: eval no but it is ignored. It would > be great if I could set an eval argument at the top of the file to be either > 'no' (don't run any code blocks) 'yes' (run all code blocks) or 'block' respect > block level eval settings > > Maybe such functionality exists in some other way - I claim only beginners > knowledge of org-babel. > > > > > -- Eric Schulte http://cs.unm.edu/~eschulte/