From: Eric Schulte <schulte.eric@gmail.com>
To: Martyn Jago <martyn.jago@btinternet.com>
Cc: emacs-orgmode@gnu.org, mail@christianmoe.com
Subject: Re: [BABEL][PATCH] ob-lilypond basic mode - was ob-lilypond
Date: Wed, 06 Jul 2011 07:20:09 -0600 [thread overview]
Message-ID: <8762nf5xu6.fsf@gmail.com> (raw)
In-Reply-To: 1F2BF18C-4151-4461-9FE3-4FC6E3F909F4@btinternet.com
Hi Martyn,
I just applied this patch.
If you don't mind packaging future patches using the git format-patch
command that would be my preference, as it preserves author information
and allows you to write your own commit message.
Thanks! -- Eric
Martyn Jago <martyn.jago@btinternet.com> writes:
> Hi
>
> I've added functionality to make ob-lilypond act in a consistent
> org-babel way by default (think ob-dot).
>
> The previous modus operandi is now known as arrange-mode and is
> selected by setting ly-arrange-mode to t
>
> More details including examples are at
> http://github.com/mjago/ob-lilypond
>
> Patch:
>
> Included examples are as follows...
>
> - Export org file with lilypond fragments to pdf using eps (high
> quality vector graphics)
>
> - org
> source: https://github.com/mjago/ob-lilypond/raw/master/examples/basic-
> mode/pdf-example/pdf-example.org
>
> - resultant
> pdf: https://github.com/mjago/ob-lilypond/blob/master/examples/basic-mo
> de/pdf-example/pdf-example.pdf?raw=true
>
> - Export org file with lilypond fragments to html using png
>
> - org
> source: https://github.com/mjago/ob-lilypond/raw/master/examples/basic-
> mode/html-example/html-example.org
>
> - resultant
> html: https://raw.github.com/mjago/ob-lilypond/master/examples/basic-mo
> de/html-example/html-example.html
>
> Regards
>
> Martyn
>
> On 1 Jul 2011, at 13:01, Christian Moe wrote:
>
> On 6/30/11 8:10 PM, Eric Schulte wrote:
>
> Martyn Jago<martyn.jago@btinternet.com> writes:
>
> (...)
>
> Great, I've just moved this into the Org-mode core and added it to
> the
>
> list of Babel languages.
>
> Great!
>
> One distinction that has occurred to me (especially following
> comments on
>
> the mailing list) is that of "babel language" and "babel language
> work-flow".
>
> In other words, I can visualise refactoring ob-lilypond to be no
> more than
>
> a specification of the Lilypond syntax, and working in parallel, on
> a
>
> work-flow implementation for Lilypond that is "opinionated" in terms
> of
>
> adjusting org-babel settings away from their defaults / removing
> work-flow
>
> noise etc. ( org-lilypond.el ) ? Would this make sense, and if so
> where would
>
> it live (aligned to org-babel / a native Emacs mode perhaps)?
>
> I hope that makes sense.
>
> That sounds like a good idea. Ideally ob-lilypond should include
> just
>
> those elements expected by the code block interface, namely
> functions
>
> for session/external evaluation, for expanding variables in code
> block
>
> bodies, and for returning results to Org-mode. I think that it
> would be
>
> a good idea to develop an external org-lilypond to support a more
>
> comprehensive workflow.
>
> I like this.
> I certainly see that the already complex task of making arrangements
> like those in Martyn's examples should be made as easy as possible.
> As for the comparatively simple use cases I brought up, once they're
> supported by ob-lilypond I'd be perfectly happy to throw header
> arguments at them.
> Yours,
> Christian
--
Eric Schulte
http://cs.unm.edu/~eschulte/
next prev parent reply other threads:[~2011-07-06 13:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 13:00 ob-lilypond Martyn Jago
2011-06-27 18:53 ` ob-lilypond Eric Schulte
2011-06-28 9:38 ` ob-lilypond Martyn Jago
2011-06-28 10:07 ` ob-lilypond Bastien
2011-06-28 10:21 ` ob-lilypond Bastien
2011-06-28 20:45 ` ob-lilypond Eric Schulte
2011-06-28 23:07 ` ob-lilypond Bastien
2011-06-29 0:41 ` ob-lilypond Eric Schulte
2011-06-29 17:07 ` ob-lilypond Martyn Jago
2011-06-29 21:15 ` ob-lilypond Eric Schulte
2011-06-30 6:38 ` ob-lilypond Martyn Jago
2011-06-30 18:10 ` ob-lilypond Eric Schulte
2011-07-01 12:01 ` ob-lilypond Christian Moe
2011-07-06 8:13 ` [BABEL][PATCH] ob-lilypond basic mode - was ob-lilypond Martyn Jago
2011-07-06 13:20 ` Eric Schulte [this message]
2011-07-01 13:43 ` ob-lilypond Martyn Jago
2011-07-01 19:27 ` ob-lilypond Eric Schulte
2011-07-02 13:04 ` ob-lilypond Martyn Jago
2011-06-28 13:38 ` ob-lilypond Cameron Horsburgh
2011-06-28 16:46 ` ob-lilypond Martyn Jago
2011-06-28 12:11 ` ob-lilypond Christian Moe
2011-06-28 13:18 ` ob-lilypond David O'Toole
2011-06-28 17:06 ` ob-lilypond Martyn Jago
2011-06-28 18:51 ` ob-lilypond Christian Moe
2011-06-28 19:00 ` ob-lilypond Michael Brand
2011-06-28 20:00 ` ob-lilypond Christian Moe
2011-06-28 21:19 ` ob-lilypond Martyn Jago
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=8762nf5xu6.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@christianmoe.com \
--cc=martyn.jago@btinternet.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).