From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Hendy Subject: Re: exporting documents w/ babel results w/o evaluating babel blocks Date: Fri, 20 May 2016 11:14:48 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37498) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b3n4d-0000ef-0y for emacs-orgmode@gnu.org; Fri, 20 May 2016 12:14:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b3n4b-000670-MI for emacs-orgmode@gnu.org; Fri, 20 May 2016 12:14:50 -0400 Received: from mail-vk0-x235.google.com ([2607:f8b0:400c:c05::235]:33816) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b3n4b-00066L-HU for emacs-orgmode@gnu.org; Fri, 20 May 2016 12:14:49 -0400 Received: by mail-vk0-x235.google.com with SMTP id c189so149790114vkb.1 for ; Fri, 20 May 2016 09:14:49 -0700 (PDT) In-Reply-To: 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" To: Ken Mankoff Cc: "emacs-orgmode@gnu.org" On Fri, May 20, 2016 at 10:57 AM, Ken Mankoff wrote: > Hi List, > > I'm repeating a question here from a recent bug report because I have a feeling official-looking bug reports might get read less than normal questions. Sorry for the re-post. > > As of an Org git commit a few weeks ago, Org exporting (and therefore Org) has become basically unusable for me. I used to be able to export code block results without evaluating the block during the export. I can no longer do this. > > The following headers used to support the above behavior: > > #+BEGIN_SRC python :exports results :results output > #+BEGIN_SRC python :exports results :results file > (and possibly with ":session foo" also) Well, you're exporting them at least *once*, right? If not, where are the results coming from? Perhaps my use case is similar. I often write up an org doc with a pretty heavy setup heading containing my main data reading in, manipulation, statistics, etc. Maybe up to 100k total rows in a data frame in R. Once I run that block the first time I'm working on the document I just put =:eval no= in the src block options. I do the same as I'm tweaking plots. Every code block I create has :eval yes initially and once I'm satisfied with the results I just change to :eval no and the generated results (for me, typically a #+results line containing a link to a pdf plot generated by my code block) are still included. Does this help at all? Sorry if I'm not understanding > > Is anyone running the current git head? And if so, can you export a document that consists of the following, or something similar to the following (i.e. do you use ":cache t" or ":cache nil")? > > #+BEGIN_SRC python :results output :exports results :session foo > print("hello, world") > #+END_SRC > #+RESULTS: > : hello, world > > If you can export this without running the code, what settings are you using? In particular, what is the value of =org-export-babel-evaluate=? Mine is set to t. Interestingly, when I export the above after deleting the results bit, no new results are generated. When I C-c C-c, they are replaced. When I add :eval no, it does't appear to run the code. Hope that helps, John > > Thanks, > > -k. >