From: Torsten Wagner <torsten.wagner@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>,
Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: [babel] noweb does not work (as expected)
Date: Tue, 10 Nov 2009 10:40:50 +0900 [thread overview]
Message-ID: <200911101040.50959.torsten.wagner@googlemail.com> (raw)
In-Reply-To: <2B2D9FBC-E90A-47EC-B4AA-9460A9E5CD40@tsdye.com>
> Hi Torsten,
Hi Tom,
> It's not clear to me what outcome you desire. Tangling should result
> in a source file that can serve as input to a compiler or
> interpreter. The combination of :noweb and :session lets you write
> literate programs that are sent directly to an interpreter, which
> presumably creates some useful output along the way (my example makes
> some graphs after a lot of data reshaping), but might be used just to
> set up an environment in the interpreter, which then can be
> manipulated directly in the session buffer.
Actually I'm looking for a way to execute several of my source code buffers in
a comfortable and semiautomatic way to do exactly what you described. Joggling
around with my measurement data... bend badly statistics until it fit to my
world ;) and finally create a plot, table or even a single number. The blocks
should be aware of each other (same session) and I like to have a single local
place to control the order in which the source code blocks are executed and be
able to tweak around with some variables or add quickly.
Thus, this sound really like :noweb and :session will do this.
However, sometimes I would prefer to see the code all tangled together in one
chunk. This might be esp. interesting for several purposes.
a) Give the pure code to someone else,
b) Make a somehow stand-alone-version without org-babel e.g. to execute it
over and over again on another org-babel free machine,
c) Debugging and bug searching might be easier since you can clearly see the
interfaces between the source code blocks without to much org-mode in between.
I guess at the moment I could create two blocks ... one :noweb, :nosession for
the interactive work on the project and one with :tangle which put all this
together into a single file. I never tried :tangle and :noweb together.
Actually, they should not conflict so fare. However, at the worg-page all
options are given as mutual exclusive.
I will give at a trial... as soon as I make my file working under both methods.
Best regards,
Torsten
next prev parent reply other threads:[~2009-11-10 1:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 3:47 [babel] noweb does not work (as expected) Torsten Wagner
2009-11-09 4:33 ` Thomas S. Dye
2009-11-09 7:38 ` Torsten Wagner
2009-11-09 16:32 ` Thomas S. Dye
2009-11-10 1:40 ` Torsten Wagner [this message]
2009-11-09 4:41 ` Dan Davison
2009-11-09 7:16 ` Torsten Wagner
2009-11-09 16:04 ` Dan Davison
2009-11-10 1:51 ` Torsten Wagner
2009-11-10 5:33 ` Eric Schulte
2009-11-10 3:02 ` [babel] (solved) " Torsten Wagner
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=200911101040.50959.torsten.wagner@googlemail.com \
--to=torsten.wagner@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.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).