Hi,
The good news is that when you run lilypond from the command line, it
behaves like a command line program (i.e. echoing output to stdout/stderr).
This seems to work every second release or so.
The bad news is that lilypond-book fails. The first problem is the old
usual
Python problem:
C:\D
Mats Bengtsson schreef:
The bad news is that lilypond-book fails. The first problem is the old
usual
Python problem:
C:\Documents and Settings\mabe\My Documents\lily>lilypond-book --pdf -o
out a.lytex
lilypond-book.py (GNU LilyPond) 2.9.20
Reading a.lytex...
Running latex...Traceback (most re
Han-Wen Nienhuys wrote:
can you tell me what
import sys
print sys.platform
says?
mingw32
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
Mats Bengtsson schreef:
import sys
print sys.platform
says?
mingw32
ok, I have substituted os.system for that platform.
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
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
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 lilyp
Han-Wen Nienhuys wrote:
I think it's easier to write snippet-names in binary. I've committed
a change for that.
Great! Using that and a minor fix of you ossystem_system that I just
submitted,
lilypond-book --pdf seems to work out of the box on Windows, for the
first time
since we left Cyg
