ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Lutz Haseloff <lutz.haseloff@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: LilyPond module, release 2009-05-19
Date: Wed, 20 May 2009 07:22:58 +0200	[thread overview]
Message-ID: <a09128560905192222t2b1798b7o3686a5b21bc09f91@mail.gmail.com> (raw)
In-Reply-To: <47EDEC75-A41E-47A8-89CE-C086F1320A3E@fiee.net>


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

Hi Hraban,

I use your module since it worked with lilypond 2.12 and I ever used it with
mkiv.
I had never a problem using it except to get started with lilypond :-)

Your new module works here with LuaTeX, Version beta-0.41.0-2009051922
(Web2C 7.5.7)
and ConTeXt  ver: 2009.05.20 00:02 MKIV very well.

Thank you very much for the module.

btw.

Hi Hans,

can you insert a line of code in ctxtools.rb?
after the line:
430        $dontaskprefixes.push(Dir.glob("mpx-*"))
I would like to have:
431        $dontaskprefixes.push(Dir.glob("*-lilypond-*"))

that would purge the lilypond temporary files as well.

Greetings Lutz

2009/5/19 Henning Hraban Ramm <hraban@fiee.net>

> I just uploaded a version of the LilyPond module that works with ConTeXt
> MkIV latest beta (only a small fix).
> Documentation PDF is still the old one, since I couldn't compile it.
>
> Does anyone use this module at all, except me?
>
> Greetlings from Lake Constance!
> Hraban
> ---
> http://www.fiee.net/texnique/
> http://wiki.contextgarden.net
> https://www.cacert.org (I'm an assurer)
>
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>

[-- Attachment #1.2: Type: text/html, Size: 2552 bytes --]

[-- Attachment #2: Type: text/plain, Size: 487 bytes --]

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

  parent reply	other threads:[~2009-05-20  5:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19 20:24 Henning Hraban Ramm
2009-05-19 20:27 ` Erich R Fickel
2009-05-20 19:20   ` Henning Hraban Ramm
2009-05-20  5:22 ` Lutz Haseloff [this message]
2009-05-20  7:30   ` Henning Hraban Ramm
2009-05-20  7:33 ` Piotr Kopszak
2009-05-20 12:29 ` 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=a09128560905192222t2b1798b7o3686a5b21bc09f91@mail.gmail.com \
    --to=lutz.haseloff@googlemail.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).