how lilypond-book deals with multiple LP releases on disk

2008-11-10 Thread Mark Polesky
Hi, I'm finally trying lilypond-book (on Windows XP), coming up against some frustrations. For some reason, the documentation has left me confused, but I think I'm figuring stuff out anyway. Problem is, I currently have both LilyPond 2.10.33 AND LilyPond 2.11.63 on my system, and when I run lily

Re: how lilypond-book deals with multiple LP releases on disk

2008-11-10 Thread Trevor Daniels
course, the one I want to use. Trevor - Original Message - From: "Mark Polesky" <[EMAIL PROTECTED]> To: "lilypond-user" Sent: Tuesday, November 11, 2008 6:08 AM Subject: how lilypond-book deals with multiple LP releases on disk Hi, I'm finally tryi

Re: how lilypond-book deals with multiple LP releases on disk

2008-11-10 Thread Mark Polesky
Trevor Daniels wrote: > Have you tried temporarily renaming the LilyPond > 2.10.33 directory in Program Files? I already had my directories set up that way. my 2.11.63 has always been: C:\Program Files\LilyPond my 2.10.33 has always been: C:\Program Files\LilyPond_2_10_33 I thought that would

Re: how lilypond-book deals with multiple LP releases on disk

2008-11-11 Thread Trevor Daniels
Mark Polesky wrote Tuesday, November 11, 2008 7:26 AM Trevor Daniels wrote: Have you tried temporarily renaming the LilyPond 2.10.33 directory in Program Files? I already had my directories set up that way. my 2.11.63 has always been: C:\Program Files\LilyPond my 2.10.33 has always been: C

Re: how lilypond-book deals with multiple LP releases on disk

2008-11-11 Thread John Mandereau
On 2008 22:08 -0800, Mark Polesky wrote: > I'm finally trying lilypond-book (on Windows XP), > coming up against some frustrations. For some reason, > the documentation has left me confused, but I > think I'm figuring stuff out anyway. Problem is, I > currently have both LilyPond 2.10.33 AND Lily

Re: how lilypond-book deals with multiple LP releases on disk

2008-11-12 Thread Mark Polesky
John Mandereau wrote: > ... or make sure LilyPond 2.11.63 > directory comes before 2.10.33 directory in your PATH. That's what it was. 2.10.33 was listed first. Changed it, now it works as expected. Thanks so much! - Mark ps. Windows users -- if you don't know where the PATH is, right-click on M