emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Olaf.Hamann" <O.Hamann@gmx.net>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Emacs-orgmode mailing list <emacs-orgmode@gnu.org>
Subject: Re: [Babel] Deep interest in LP feature of org-mode
Date: Mon, 14 Mar 2011 17:15:05 +0100	[thread overview]
Message-ID: <4D7E3F09.3040706@gmx.net> (raw)
In-Reply-To: <87mxkxya8q.fsf@gmail.com>

Thank you for your quick reply and the precise answers, Eric.

Comparing org-export vs. org-tangle I've mixed up how I used text 
* for myself I often use it simply for creating codefiles (tangling)  - 
org-export would be sufficient
* for tasks in office there is need for creating a nice doc file, too 
(weaving) - org-babel for code creation
Thank you for making that clear to me.

I will revisit my nebulous feature request of calling blocks inside 
blocks - there is no actual need, as you identified.


      reply	other threads:[~2011-03-14 16:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 15:30 [Babel] Deep interest in LP feature of org-mode Olaf.Hamann
2011-03-14 15:47 ` Eric Schulte
2011-03-14 16:15   ` Olaf.Hamann [this message]

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:

  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=4D7E3F09.3040706@gmx.net \
    --to=o.hamann@gmx.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@gmail.com \


* 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


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).