From: Jambunathan K <kjambunathan@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: Proposed New Syntax For Calling Code Blocks was
Date: Sat, 11 Sep 2010 02:42:22 +0530 [thread overview]
Message-ID: <81bp85fgll.fsf@gmail.com> (raw)
In-Reply-To: <817hits755.fsf_-_@gmail.com> (Jambunathan K.'s message of "Sat, 11 Sep 2010 01:28:14 +0530")
Eric
I have typed enough. You or the Mailing list wouldn't get any more
unsolicited mails from me on this little idea of mine.
Some concluding remarks.
As I see it, the crux of my articles is in highlighting the unique and
(much needed role) that Babel could play or plays within the org
ecosystem.
In my view (which could be incomplete, flawed or warped),
1. Babel is predominantly a macro environment for 'mashing up of'
textual content within an orgmode document.
2. The syntax/grammar of Babel macro calls should not deviate
significantly from existing Orgmode syntax and more specifically it
shouldn't invent new syntax (so that parsing becomes spaghettish).
3. The noweb/literate programming face of Babel may not be of much
interest to 'compositional' demands of Orgmode users and
vice-versa. i.e, One predominantly writes articles or does literate
programming. Not both simultaneously. Text mashups are interesting
for set of first set of users and noweb expansion to the second set.
Just sharing my thoughts ... More of what my mental model of Babel is
...
Jambunathan K.
next prev parent reply other threads:[~2010-09-10 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-09 15:09 Problem with Babel and sessions Christopher Witte
2010-09-10 18:06 ` Proposed New Syntax For Calling Code Blocks was: " Eric Schulte
2010-09-10 19:58 ` Proposed New Syntax For Calling Code Blocks was Jambunathan K
2010-09-10 21:12 ` Jambunathan K [this message]
2010-09-13 12:05 ` Proposed New Syntax For Calling Code Blocks was: Problem with Babel and sessions Christopher Witte
2010-09-18 12:24 ` Eric Schulte
2010-09-14 19:03 ` Sébastien Vauban
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=81bp85fgll.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@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).