Schneelocke writes:
> I don't know. Does the windows shell pass arguments the same way that
> a Unix shell does? It's just a random idea, but I wouldn't be too
> surprised if it did not handle things like quotes itself and instead
> expected the invoked program to take care of these.
I remember. It is the way that python is invoked through PYEXT. Try
python ...LilyPond/usr/bin/convert-ly.py "fu bar.ly"
that should work.
In lilypond.nsi.in, I have
# %1 is the PYTHON command, so must be quoted bo the space
WriteRegExpandStr HKCR "Python\shell\open\command" ""
'"$INSTDIR\usr\bin\python.exe" "%1" %2 %3 %4 %5 %6 %7 %8 %9'
If I change this to
WriteRegExpandStr HKCR "Python\shell\open\command" ""
'"$INSTDIR\usr\bin\python.exe" "%1" "%2" %3 %4 %5 %6 %7 %8 %9'
then
convert-ly.py "fu bar.ly"
will work, but
convert-ly.py test.ly "fu bar.ly"
will fail. If I change it to
WriteRegExpandStr HKCR "Python\shell\open\command" ""
'"$INSTDIR\usr\bin\python.exe" "%1" "%2" "%3" "%4" "%5" "%6" "%7" "%8" "%9"'
then
convert-ly.py test.ly
will complain about 7 files called `' that do not exist. Patches
thoughtfully considered.
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
_______________________________________________
lilypond-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
