From: Phillip Lord <phillip.lord@russet.org.uk>
To: Thorsten Jolitz <tjolitz@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Emacs and lilypond
Date: Mon, 07 Mar 2016 14:29:01 +0000 [thread overview]
Message-ID: <87vb4ybbv6.fsf@russet.org.uk> (raw)
In-Reply-To: <87k2lg51uv.fsf@gmail.com> (Thorsten Jolitz's message of "Sat, 5 Mar 2016 17:24:56 +0100")
Thorsten Jolitz <tjolitz@gmail.com> writes:
>
> I once used Lilypond with Org Babel to create something like an "Org-mode
> Bandbook", that is an Org document that contains all of the songs a band
> plays, as well as contact info of the band members, and the bands tour
> and rehearsal schedule:
>
> ,----
> | https://github.com/tj64/org-bandbook
> `----
>
> I based it on the great Openbook project from Mark Veltzer:
>
> ,----
> | https://github.com/veltzer/openbook
> `----
>
> There are (syntax) transformation functions for both directions - from
> Openbook files to Org-mode files and vice versa. And I made use of
> Lilyponds (musical) transformation facilities, making it easy to print
> such a bandbook for different instrumentalists (C-Version, Bb-Version,
> Eb-Version etc.).
>
> IIRC I left it in a working state, but the results had a very plain
> latex textbook look.
> If I have a practical use case for it, I will continue to develop it and
> look for a nice latex style, in the meantime I would be happy if others
> become interested in the project and contribute.
>
> The nice thing is that all the hard work is done by others:
> - the Openbook project converts sheet music to lilypond
> - Org-mode replaces Lilypond Book and allows to create very
> sophisticated documents around the scores
>
> I would say that building on the current state of the project, creating
> a really beautiful Bandbook (for C and transposing instruments) that is
> easy to modify and maintain, would require mostly good Org-mode and
> Latex skills, not so much Elisp or Lilypond skills (as long as the songs
> are from Openbook or so.)
>
> But with regards to the original question: using Org Babel, its just
> about editing plain Lilypond code in source blocks, and I did not get so
> involved that I noticed any shortcomnings of lilypond-mode.el. All the
> compilation stuff was handled nicely by ob-lilypond in the background.
That looks like a fairly nice option, thanks for the info.
Phil
next prev parent reply other threads:[~2016-03-07 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 22:12 Emacs and lilypond Phillip Lord
2016-03-05 16:24 ` Thorsten Jolitz
2016-03-07 14:29 ` Phillip Lord [this message]
2016-03-05 17:44 ` Robert Thorpe
2016-03-05 19:00 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vb4ybbv6.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=help-gnu-emacs@gnu.org \
--cc=tjolitz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.