From: Erik Iverson <eriki@ccbr.umn.edu>
To: Rainer M Krug <r.m.krug@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] Evaluating all source blocks in a document?
Date: Wed, 30 Jun 2010 09:55:21 -0500 [thread overview]
Message-ID: <4C2B5AD9.1080202@ccbr.umn.edu> (raw)
In-Reply-To: <AANLkTik242L2OvFqqSum5spi8FrzauLOieGtGSs9-eHR@mail.gmail.com>
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.
next prev parent reply other threads:[~2010-06-30 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 11:35 [babel] Evaluating all source blocks in a document? Rainer M Krug
2010-06-30 13:33 ` Russell Adams
2010-06-30 14:03 ` Rainer M Krug
2010-06-30 14:55 ` Erik Iverson [this message]
2010-07-01 7:05 ` Rainer M Krug
2010-06-30 16:35 ` Eric Schulte
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=4C2B5AD9.1080202@ccbr.umn.edu \
--to=eriki@ccbr.umn.edu \
--cc=emacs-orgmode@gnu.org \
--cc=r.m.krug@gmail.com \
/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).