Re: New install problem

[Floris van Manen]

On Jul 26, 2011, at 18:13, Graham Percival wrote:

> On Tue, Jul 26, 2011 at 05:33:17PM +0200, Floris van Manen wrote:
>> The path points to the command line version with the app folder.
>> As the problem is in the incompatibility of the visual wrapper with Lion, 
>> you can just compile the .ly file from the command line
>> 
>> if you define an alias you can save some typing:
>> alias llp='/Applications/LilyPond.app/Contents/Resources/bin/lilypond'
> 
> That is not the recommended method of using lilypond on the
> command-line in MacOS X.  The recommended method is printed on the
> MacOS X download page:
>  http://lilypond.org/macos-x.html
> 
> Cheers,
> - Graham


Well, that information includes:
>>>
Invoking individual scripts
The scripts — such as lilypond-book, convert-ly, abc2ly, and even 
lilyponditself — are included inside the .app file for MacOS X.
Scripts can also be run from the command line by invoking them directly:
path/to/LilyPond.app/Contents/Resources/bin/lilypond

The same is true for all other scripts in that directory, such as 
lilypond-bookand convert-ly.
<<<


I only added an alias to that path, which is sort of similar as creating a file 
to include that command line.
I'm lazy so an alias in a .profile is simple enough ...


There are however several included commands that will simple not work at all on 
OSX 10.6 and up.
Try the midi2ly for instance ...


.F