emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "David O'Toole" <dto1138@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: meta model for literate programming [pdf] Re: hypermedia programming with babel
Date: Mon, 5 Jul 2010 17:55:06 -0400	[thread overview]
Message-ID: <AANLkTikOf4Ogo0mZnRTfLQ6yj8cxCHfyoEJ9E-QdfnYF@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1996 bytes --]

An interesting paper!

http://www.cosc.canterbury.ac.nz/research/reports/HonsReps/1999/hons_9902.pdf

On Mon, Jul 5, 2010 at 4:15 PM, Eric Schulte <schulte.eric@gmail.com> wrote:

> Hi David,
>
> "David O'Toole" <dto1138@gmail.com> writes:
>
> > Since discovering org babel, I've been doing a lot of reading and
> > brainstorming, and have collected some thoughts/code/plans in several
> > places:
> >
> >  1. http://github.com/dto/org-babel-lisp
> >
> > Some very basic compatibility. I'm not experienced enough with either
> > babel or slime, perhaps someone can help me flesh this code out. I
> > have papers on file with FSF, please feel free to take
> > org-babel-lisp.el and do whatever you want.
> >
>
> This looks like a good start, you could look to ob-clojure.el for an
> example of a slime-driven lisp Babel file.
> http://repo.or.cz/w/org-mode.git/blob_plain/HEAD:/lisp/ob-clojure.el
>
> >
> >  2. http://github.com/dto/hypo
> >
> > My thoughts and some code toward a reproducible-results sort of digital
> > asset management system, with relevance to games.
> > Github's formatter messes it up. To read the raw file, use this link:
> > http://github.com/dto/hypo/raw/master/hypo.org
> >
> > I've made TODO items for the icons discussion. I want to be able to
> > define/contribute my own competing theme.
>
> That looks like a great application for literate programming.  It might
> be nice to link to this project from the Babel uses page at
> http://orgmode.org/worg/org-contrib/babel/uses.php
>
> > How can I help next?
>
> Babel in general is in need of some language-specific introductory
> tutorials, with the goal of laying out the basic usage plenty of
> examples covering simple use case e.g.
> - author a shell script which can be tangled out to an executable
> - simple processing of data in tables, or execution of code blocks with
>  the output captured in the buffer
>
> There is also plenty of room for help with documentation, testing,
> etc...
>
> Thanks! -- Eric
>

[-- Attachment #1.2: Type: text/html, Size: 3112 bytes --]

[-- Attachment #2: Type: text/plain, Size: 201 bytes --]

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

                 reply	other threads:[~2010-07-05 21:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=AANLkTikOf4Ogo0mZnRTfLQ6yj8cxCHfyoEJ9E-QdfnYF@mail.gmail.com \
    --to=dto1138@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).