From mboxrd@z Thu Jan 1 00:00:00 1970 From: Erik Iverson Subject: Re: [babel] Evaluating all source blocks in a document? Date: Wed, 30 Jun 2010 09:55:21 -0500 Message-ID: <4C2B5AD9.1080202@ccbr.umn.edu> References: <20100630133310.GG25163@thinkpad.adamsinfoserv.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from [140.186.70.92] (port=42324 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OTyhH-0005Vf-Q8 for emacs-orgmode@gnu.org; Wed, 30 Jun 2010 10:55:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OTyhC-0007ae-AH for emacs-orgmode@gnu.org; Wed, 30 Jun 2010 10:55:31 -0400 Received: from walleye.ccbr.umn.edu ([128.101.116.11]:2857) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OTyhB-0007aS-UM for emacs-orgmode@gnu.org; Wed, 30 Jun 2010 10:55:26 -0400 In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Rainer M Krug Cc: emacs-orgmode@gnu.org Hello, > On Wed, Jun 30, 2010 at 01:35:04PM +0200, Rainer M Krug wrote: > > Hi > > > > I use Org-babel for literate programming in R, but the tangling > takes quite > > long. Therefore my question: as it is possible to evaluate a > single code > > block, is it possible to evaluate ALL code blocks i a document? > that would > > make debugging much easier. > > M-x org-babel-execute-buffer > C-c C-v C-b should be a shortcut for that in org-mode now, according to my reference card. > > Thanks - that seems to be what I am looking for, but after trying it > out, I realized the following: for each block, e new R session is > opened. This does not work for literate programming, as different blocks > belong to each other, i.e. one block opens a function, the next one > closes it. In addition, I want to evaluate the results, i.e. created > objects, in R - therefore the session should stay open. So my guess: > tangle and debug. > > OTOH this may not make it easier to debug, the babel error window > doesn't list line numbers or blocks where the error occurred. > Have you tried the :session argument? It submits the code block to a running R session. I use it for what you're doing with success. You can set it per code block, or buffer-wide, try for example: #+PROPERTY: session *R* > > Perhaps that should be a feature request to log what src block or > org file > line number the errors occurred in. > > > That would be nice. > > > > Also: is it possible, to get some kind of automatic headings for > the tangled > > code blocks? That would make it easier to identify in which code > block the > > source code in the tangled file comes from. Try (setq org-babel-tangle-w-comments t) and see if that does what you're thinking. It will give headings for the source block, but I don't recall what information they contain.