Mats Bengtsson schreef:
The second problem is new for this release. When I call the program
using the
native Python package, it doesn't find the lilypond executable, for
some strange reason:
I've verified that the lilypond bin directory is at the top of the
path and it works to
call lilypond from the command line, so the PATH must get lost
somewhere along
the way.
Looking again, I realized that the problem was the line
os.environ['PATH'] = bindir + ':' + os.environ['PATH']
since ':' doesn't work as a path separator in Windows. I have no idea why
it has worked earlier, though. Maybe I used to have an extra copy of
C:\Program Files\LilyPond\usr\bin\ in my PATH (but I cannot recall having
changed it recently). Anyway, I'll submit a patch that instead does
os.environ['PATH'] = os.path.join(bindir,os.environ['PATH'])
which should be safe on all platforms.
One additional problem remains, namely the classical CR/LF problem when
LilyPond tries
to parse the file snippet-names generated by lilypond-book. It's the line
(string-split (ly:gulp-file f) #\nl)
I think it's easier to write snippet-names in binary. I've committed a
change for that.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
