emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: Martyn Jago <martyn.jago@btinternet.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: ob-lilypond
Date: Thu, 30 Jun 2011 11:10:32 -0700	[thread overview]
Message-ID: <87ei2b8a1z.fsf@gmail.com> (raw)
In-Reply-To: <loom.20110630T080817-717@post.gmane.org> (Martyn Jago's message of "Thu, 30 Jun 2011 06:38:33 +0000 (UTC)")

Martyn Jago <martyn.jago@btinternet.com> writes:

> Hi
>> If Shelagh hasn't actually authored any of ob-lilypond.el (or at least      
>> hasn't authored more than 10 lines of) then we could simply remove her
>> name from the authors list and include it into the Org-mode core.  This
>> however may not be the best long-term solution if you anticipate her
>> increased participation later-on in the project.  Please let me know
>> (soon) if you would like me to make this change.
> I've modified the author status in my repository.

Great, I've just moved this into the Org-mode core and added it to the
list of Babel languages.

>> Ultimately this points to the more general issue of how to include Babel
>> language-specific tests into the Org-mode test suite s.t. they can be
>> executed independently of the core of the test suite.
>> Thanks -- Eric
> My unit-tests don't currently require the Lilypond to be initialised "as a babel
> language" nor a Lilypond executable AFAICT, so currently they possibly don't
> need to be run "independently". I'll investigate this further. 

That's good to hear.  Are you up for trying to merge them into the rest
of the Org-mode test suite?  This should be as simple as placing any
org-mode example files you have in


placing the .el file defining your tests into


and renaming all of your tests so that they start with the prefix

I fully understand if you don't have the time to do this, and I should
be able to take a shot at it some time in the not-too-distant future.

> 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.

Thanks -- Eric

> Regards
> Martyn

Eric Schulte

  reply	other threads:[~2011-06-30 18:10 UTC|newest]

Thread overview: 32+ 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                 ` Eric Schulte [this message]
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
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
  -- strict thread matches above, loose matches on Subject: below --
2015-03-25 12:49 ob-lilypond pls
2015-03-26  9:20 ` ob-lilypond pls
2015-03-29 21:27   ` ob-lilypond Nick Dokos
2015-03-30  9:20     ` ob-lilypond Patrick L. Schmidt
2015-03-26  9:26 ob-lilypond Patrick L. Schmidt

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:

  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=87ei2b8a1z.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=martyn.jago@btinternet.com \


* 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


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).