From: Russell Adams <RLAdams@AdamsInfoServ.Com>
To: emacs-orgmode@gnu.org
Subject: Re: [babel] Evaluating all source blocks in a document?
Date: Wed, 30 Jun 2010 08:33:10 -0500 [thread overview]
Message-ID: <20100630133310.GG25163@thinkpad.adamsinfoserv.com> (raw)
In-Reply-To: <AANLkTinmJFzclHobY-9o_JpFoguEhH88_1uGPyK569BR@mail.gmail.com>
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
OTOH this may not make it easier to debug, the babel error window
doesn't list line numbers or blocks where the error occurred. Perhaps
that should be a feature request to log what src block or org file
line number the errors occurred in.
> 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.
I haven't tried tangling yet, is there a good tutorial somewhere?
Thanks.
------------------------------------------------------------------
Russell Adams RLAdams@AdamsInfoServ.com
PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/
Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
next prev parent reply other threads:[~2010-06-30 13:33 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 [this message]
2010-06-30 14:03 ` Rainer M Krug
2010-06-30 14:55 ` Erik Iverson
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=20100630133310.GG25163@thinkpad.adamsinfoserv.com \
--to=rladams@adamsinfoserv.com \
--cc=emacs-orgmode@gnu.org \
/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).