emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Erik Iverson <eriki@ccbr.umn.edu>
To: Torsten Wagner <torsten.wagner@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [org-babel] Does org-babel needs some simplification?
Date: Mon, 28 Jun 2010 23:28:55 -0500	[thread overview]
Message-ID: <4C297687.5080806@ccbr.umn.edu> (raw)
In-Reply-To: <4C296DDA.1080109@gmail.com>

Hello!

<snip>
> 
> Whenever I come back to org-babel, it takes me a huge amount of time to
> find myself back again in the syntax. Often I spend a day or two heavily
> reading the website and manual again to figure out how to make it working.
> 
> There are so many options. tangle files, results, scripting mode,
> sessions, noweb, lot, etc.
> 
> Just yesterday, I fighted again to make a simple python script running
> as desired to generate an automatic report. I did this dozen of times
> and even by using some old report as template I still struggle with it.
> Comparing old reports I noticed that I did it in many different ways.
> Tangeling all snipplets, using noweb syntax, with and without session
> support, etc.

<snip>

I have not used it for Python, but for R coding I've found it incredibly 
intuitive.  However, that might be because R has long supported literate 
programming through Sweave, complete with noweb syntax and code tangling.

I personally don't think it's too complex.  One thing that could help is a 
gentle introduction written by users of each language that babel supports.  I 
have started something like that with R already on my blog, see 
http://blogisticreflections.wordpress.com/2010/05/23/introduction-to-using-r-with-org-babel-part-1/ 


I think the best thing to do is to figure out a system that works for you, and 
document it (in org-mode of course!) so that there are notes the next time you 
come back to the file, or need to produce a new file.

Of course, the authors of babel might have plans to somehow simplify syntax, but 
I just wanted to point out that, like anything, with some repetition, you can 
commit the main ideas to memory and then consult the manual when needed.  I 
found that spending a couple hours running all the possible options in the 
manual with R while taking notes went a long way in helping me understand how it 
it all works.

Best Regards,
Erik

  reply	other threads:[~2010-06-29  4:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29  3:51 [org-babel] Does org-babel needs some simplification? Torsten Wagner
2010-06-29  4:28 ` Erik Iverson [this message]
2010-06-29 18:07   ` Eric Schulte
2010-06-29  4:36 ` Carsten Dominik
2010-06-29  7:29 ` Thomas S. Dye
2010-06-29 18:01 ` Eric Schulte
2010-06-30 19:30 ` Daniel Brunner
2010-06-30 21:56   ` Jonathan Arkell
2010-07-01  0:37   ` Bernt Hansen
2010-07-01  2:36 ` Torsten Wagner
2010-07-01 20:53   ` 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=4C297687.5080806@ccbr.umn.edu \
    --to=eriki@ccbr.umn.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=torsten.wagner@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).