emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Thorsten <gruenderteam.berlin@googlemail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: [babel] Suggestions: GRASS GIS und Lilypond
Date: Tue, 15 Feb 2011 11:15:42 -0600	[thread overview]
Message-ID: <AANLkTikKjse6WDJpn+RSV=6nSfZ39WAfZryq85mVwoRq@mail.gmail.com> (raw)
In-Reply-To: <86aahx90c5.fsf@googlemail.com>


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

On Tue, Feb 15, 2011 at 2:19 AM, Thorsten <
gruenderteam.berlin@googlemail.com> wrote:

> John Hendy <jw.hendy@gmail.com> writes:
>
> > I've used Lilypond and think it's amazing. But... what advantage is
> > having it in org? Just curious... integration in foldable headlines
> > and src blocks? For my uses, I can't think of a purpose unless, I
> > guess, I was doing in-document scores or bars like in a wedding
> > program or something. What was your idea -- I'm interested.
> >
> > John
>
> I thought about writing a music book with the typesetting done by LaTex
> and Lilypond. I know it should work just like combining R and LaTex with
> Sweave, but the last time I tried I had problems - integration in Org
> could make it easy. And, since nowadays books are shared on the web for
> free and the author starves, one might want to reuse the content in the
> setting of an online music school. Orgmode's html export would make this
> easy.
>
>
Cool -- this was along my thoughts. I like it! I agree it can't be that hard
to integrate. It's a pretty simple markup.

John


> Thorsten
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> 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
>

[-- Attachment #1.2: Type: text/html, Size: 2179 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:[~2011-02-15 17:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15  1:02 [babel] Suggestions: GRASS GIS und Lilypond Thorsten
2011-02-15  2:57 ` John Hendy
2011-02-15  8:19   ` Thorsten
2011-02-15 17:15     ` John Hendy [this message]
2011-02-15  9:11 ` Rainer M Krug
2011-02-15  9:59 ` Christian Moe
2011-02-15 10:08   ` Bastien
2011-02-16 21:21   ` Shelagh Manton
2011-02-17 18:40     ` Martyn Jago
2011-02-20 20:37       ` Shelagh Manton
2011-02-20 20:42         ` Shelagh Manton
2011-02-21 13:01           ` Martyn Jago
2011-02-15 18:46 ` Eric Schulte
2011-02-16  9:14   ` Rainer M Krug
2011-02-18 22:39 ` Thorsten

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='AANLkTikKjse6WDJpn+RSV=6nSfZ39WAfZryq85mVwoRq@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=gruenderteam.berlin@googlemail.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).