From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Ben Alexander <bva@alexanderonline.org>
Cc: org-mode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Org-babel and LaTeX letter
Date: Wed, 07 Sep 2011 16:36:38 +0100 [thread overview]
Message-ID: <87fwk89xj0.fsf@ucl.ac.uk> (raw)
In-Reply-To: <D7D4CD98-E887-4064-8D61-6D39FF93243F@alexanderonline.org> (Ben Alexander's message of "Wed, 7 Sep 2011 12:11:40 +0300")
Ben Alexander <bva@alexanderonline.org> writes:
[...]
> Now perhaps is a good time to ask what the different workflows are for
> export, publish, babel and tangle. They seem to have overlapping
> functionality. My basic concept is:
>
> export : Your complete (or partial) org file in another form, like
> paper or on the web. For when emacs isn't around and you don't want
> to forget what your orgmode file says, or for giving a copy of the
> data in your org file to someone who doesn't appreciate
> emacs. #+begin_latex blocks belong to this export.
I agree.
> publish : export more than one org file. I've no idea what use case
> makes publish different than export.
Example: a web site. The nice thing about publish is it only converts
those files which have changed (at least in my setup but that setup was
defined a while ago now so I cannot remember if that's the default).
> babel : use for including chunks of code in an org file. Base use
> case simply allows you to easily edit them in a native emacs mode
> while still having them organized into your run-of-the-mill org file.
> Also allows code blocks to be printed more nicely (in color? with line
> numbers?) which doesn't happen in 'export' Secondary use case allows
> you to execute the code blocks #+begin_src and #+results: blocks
> belong to babel. I plan on using ledger in babel blocks to store my
> often executed queries, even though most of the 'code' is on the
> command line.
Well, I would suggest that your "secondary" use case is actually the
primary use case? And especially so when combined with the ability to
use inputs from org tables or to chain blocks so that results of one are
inputs to another.
> tangle : use case - lets you have lots of code blocks organized in an
> orgmode file become a complete, compilable program. Normally the
> orgmode syntax would cause a complier to choke, so tangle removes the
> orgmode structure. Added bonus: lets different programs co-operate in
> a single orgmode file. Like a makefile on steroids? #+begin_src
> blocks can belong to tangle, too.
Your first use case for *babel* above fits in here. More to the point,
you can write truly descriptive text related to the program (including,
for instance, equations, diagrams, etc.) without the restrictions
imposed by normal commenting rules in the particular language(s) used.
> While the orgmode documentation does a great job of explaining how to
> configure the details of each process, I feel like I'm missing the
> how do I pick the feature that solves the problem I have right now'
> part. Probably because each feature is flexible enough to be used in
> overlapping ways.
Yes, indeed!
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.7 (release_7.7.261.g2178)
prev parent reply other threads:[~2011-09-07 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 12:01 Org-babel and LaTeX letter Ben Alexander
2011-09-06 15:17 ` Eric Schulte
[not found] ` <m1ipp5iuom.fsf@tsdye.com>
2011-09-07 9:11 ` Ben Alexander
2011-09-07 15:36 ` Eric S Fraga [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:
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=87fwk89xj0.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=bva@alexanderonline.org \
--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).