ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Robert Blackstone <blackstone.robert@gmail.com>
To: ntg-context@ntg.nl
Subject: ConTeXt and LilyPond problem
Date: Tue, 28 Jun 2016 13:19:50 +0200	[thread overview]
Message-ID: <A6217310-854F-459C-94DF-169999EB002F@gmail.com> (raw)
In-Reply-To: <mailman.1.1467108001.8379.ntg-context@ntg.nl>


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


On 28 Jun 2016, at 12:00 , Mojca Miklavec <mojca.miklavec.lists@gmail.com> wrote
> 
> On 27 June 2016 at 16:11, Robert Blackstone wrote:
>> Dear All,
>> 
>> I am trying to get the combination of ConTeXt and LilyPond working.
>> I copied the example that I found on http://wiki.contextgarden.net/LilyPond
>> , changing the setups a little (I don't have the font  Adobe Jenson Pro).
>> 
>> Processing it with mkiv from april this year and earlier produces a pdf with
>> both zapf texts and in between the text: [[output file missing.
>> 
>> The log-file says:
>> ---------------------
>> t-filter  . cached output file
>> 'lilytemp/LilyPond-ConTeXt-example-27-06-16-templilypond-0.pdf' missing.
>> Rerunning filter
>> sh: lilypond: command not found
>> t-filter  > file
>> 'lilytemp/LilyPond-ConTeXt-example-27-06-16-templilypond-0.pdf' cannot be
>> found
>> ---------------------
>> 
> 
> You first need to get lilypond working from Terminal, otherwise asking
> any other question on the ConTeXt mailing list won't really help much.
> 
> I created a shell script "lilypond" somewhere in PATH, containing [ ......] 
> and then it just consumes processor forever without producing any
> result. I'm not eager to start debugging right now, but just to let
> you know that getting lilypond to work from terminal is a prerequisite
> for getting the module to work.
> 
> Mojca

Thanks Mojca,

I have tried to get lilypond working from Terminal but without success. No idea why. Whatever I do Terminal replies with : cannot execute binary file.
I will now try to get some advice from the LilyPond list. 

Best regards,
Robert Blackstone






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

[-- Attachment #2: Type: text/plain, Size: 485 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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2016-06-28 11:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1467108001.8379.ntg-context@ntg.nl>
2016-06-28 10:46 ` Robert Blackstone
2016-06-28 11:19 ` Robert Blackstone [this message]
     [not found] <mailman.193.1467116172.6154.ntg-context@ntg.nl>
2016-06-29  8:47 ` Robert Blackstone
2016-07-03  8:49   ` Axel Kielhorn
2016-06-27 14:11 Robert Blackstone
2016-06-27 15:08 ` Jean-Pierre Delange
2016-06-27 20:36 ` Mojca Miklavec
2016-07-02 16:03   ` Henning Hraban Ramm

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=A6217310-854F-459C-94DF-169999EB002F@gmail.com \
    --to=blackstone.robert@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).