From: Rainer M Krug <r.m.krug@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: [babel] Evaluating all source blocks in a document?
Date: Wed, 30 Jun 2010 13:35:04 +0200 [thread overview]
Message-ID: <AANLkTinmJFzclHobY-9o_JpFoguEhH88_1uGPyK569BR@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 976 bytes --]
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.
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.
Cheers,
Rainer
--
NEW GERMAN FAX NUMBER!!!
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology,
UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Natural Sciences Building
Office Suite 2039
Stellenbosch University
Main Campus, Merriman Avenue
Stellenbosch
South Africa
Cell: +27 - (0)83 9479 042
Fax: +27 - (0)86 516 2782
Fax: +49 - (0)321 2125 2244
email: Rainer@krugs.de
Skype: RMkrug
Google: R.M.Krug@gmail.com
[-- Attachment #1.2: Type: text/html, Size: 1245 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next reply other threads:[~2010-06-30 11:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 11:35 Rainer M Krug [this message]
2010-06-30 13:33 ` [babel] Evaluating all source blocks in a document? Russell Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTinmJFzclHobY-9o_JpFoguEhH88_1uGPyK569BR@mail.gmail.com \
--to=r.m.krug@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.