bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: New install problem


From: Floris van Manen
Subject: Re: New install problem
Date: Tue, 26 Jul 2011 17:33:17 +0200

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'

then use:
llp test.ly



On Jul 26, 2011, at 13:56, James Lowe wrote:

> hello,
> 
> )-----Original Message-----
> )From: address@hidden
> )[mailto:address@hidden On
> )Behalf Of Floris van Manen
> )Sent: 26 July 2011 08:45
> )To: Trevor Bača
> )Cc: address@hidden bug
> )Subject: Re: New install problem
> )
> )
> )On Jul 25, 2011, at 20:20, Trevor Bača wrote:
> )
> )
> )> /Applications/LilyPond.app/Contents/Resources/bin/lilypond that runs
> )for me under Lion.
> )
> )This is a good workaround indeed
> 
> OK I'm confused now.  Isn't the above supposed to be THE path to the exe?
> 
> What have I missed here. Why does one work and the other not?
> 
> Also I never used LP on the CLI with Mac OS, I used LilyPad and ctrl-r (to 
> compile).
> 
> So what happens in this case?
> 
> The assumption is that users put the LilyPond.app file in the Applications 
> Directory (that may be a bad assumption, but *most* users will) and then 
> double click the icon from there to get LilyPad and work on that.
> 
> Does that fail?
> 
> James
> 
> 
> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]