ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: lilypond
Date: Mon, 27 Aug 2007 16:28:06 +0200	[thread overview]
Message-ID: <6faad9f00708270728r1f5dc470m8ce4ac96c7da799b@mail.gmail.com> (raw)
In-Reply-To: <7F1631B9-8C3B-430D-A1C9-2B4EA842CFA2@fiee.net>

On 7/6/07, Henning Hraban Ramm wrote:
> Am 2007-07-03 um 17:59 schrieb Wolfgang Werners-Lucchini:
>
> Sorry, the publicly available LilyPond module is outdated. Try the
> attached one.
>
> I delayed the publishing of my latest version because Ruby texexec
> had a bug that prevented lilypond from being called, I guess that's
> gone, but I had no time to check yet.

The module on the garden worked OK for me with lilypond 2.10.25, but
it failed (only slightly) when called with LuaTeX, that's why you need
an additional one-line patch.

> And I didn't adapt the module
> to LilyPond 2.11, too. (2.10.2x should work.)

To Steffen: if you're working with Mac (I'm not sure), the easiest way
is to install it with fink (of course you need to have fink installed
first.)
    fink install lilypond

Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2007-08-27 14:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-03 15:59 lilypond Wolfgang Werners-Lucchini
2007-07-06 20:25 ` lilypond Henning Hraban Ramm
2007-08-27 14:28   ` Mojca Miklavec [this message]
2007-08-27 10:28 ` lilypond Steffen Wolfrum
2007-08-26 22:35 lilypond Hans Hagen
2011-08-18 22:32 buffer names in MKII Mojca Miklavec
2011-08-18 21:29 ` Aditya Mahajan
2011-08-19  7:53   ` Henning Hraban Ramm
2011-08-19 15:08     ` Lilypond (Re: buffer names in MKII) Aditya Mahajan
2011-08-19 20:18       ` Lilypond Henning Hraban Ramm
2011-08-20  8:19         ` Lilypond Aditya Mahajan
2011-08-21  1:22           ` Lilypond David Wooten
2011-08-21 12:07           ` Lilypond Henning Hraban Ramm
2011-08-21 18:25             ` Lilypond Henning Hraban Ramm
2011-08-21 22:14             ` Lilypond Aditya Mahajan
2011-08-21 22:24               ` Lilypond Hans Hagen
2011-08-21 22:32                 ` Lilypond Aditya Mahajan
2011-08-22  1:53               ` Lilypond Aditya Mahajan
2011-08-22 13:59                 ` Lilypond Henning Hraban Ramm
2011-08-22 15:18                   ` Lilypond Aditya Mahajan
2014-06-08 22:31 Lilypond David Wooten
2014-06-10  9:53 ` Lilypond Henning Hraban Ramm
2014-06-10 18:26   ` Lilypond David Wooten
2014-06-11  8:51     ` Lilypond Henning Hraban Ramm
2014-06-12 17:00       ` Lilypond David Wooten
2014-06-12 17:37         ` Lilypond Henning Hraban Ramm
2014-06-12 20:21           ` Lilypond David Wooten

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=6faad9f00708270728r1f5dc470m8ce4ac96c7da799b@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --cc=ntg-context@ntg.nl \
    /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.
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 NNTP newsgroup(s).