hello, On 6 January 2012 11:23, <m...@apollinemike.com> wrote: > On Fri, 6 Jan 2012 11:14:34 +0000, Graham Percival wrote: >> >> On Fri, Jan 06, 2012 at 10:21:19AM +0000, lilyp...@googlecode.com wrote: >>> >>> >>> We'd need to be careful over that. Think it's no problem from a >>> pure Lilypond perspective - I'd doubt many windows users would run >>> lily from the command line. However, I believe they would run -book >>> from the command line, and that needs to find the python module in >>> the path statement, I think. >> >> >> Good point! Does anybody feel like checking into this? >> >> I still think it's best to just explain which directories need to >> be in the PATH rather than modifying it ourselves, but we'll need >> to know this information when it comes time to write that >> documentation. >> >> Cheers, >> - Graham > > > I think that all you need is: > > PATH_TO_LILYPOND\usr\bin > > In most set-ups this'd be: > > C:\Program Files\LilyPond\usr\bin > > Cheers, > MS >
Yes this is the default. The installer lets you choose the location, but Windows' users will be used to the 'C:\Program Files\LilyPond\usr\bin' nomenclature. I'd say 99% of all users will use the default path, and those that choose to move it will know that they need to adjust their PATH accordingly. If you look here: http://lilypond.org/doc/v2.14/Documentation/usage/lilypond_002dbook It links to Command Line Usage which says if you use mac then you need to go here http://lilypond.org/doc/v2.14/Documentation/web/macos-x and so we can make a similar entry in Usage and point them to http://lilypond.org/doc/v2.14/Documentation/web/windows ! which is what we've had all along - we just never linked to it from Usage like we do Mac OS X. Voila! I can do that. Just let me know if that is the route we are going down now. -- -- James _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
