hello,
On 16 August 2013 12:07, Eluze <elu...@gmail.com> wrote: > following the instructions in AU: > > "Alternatively, if you want to specify a different name for the upgraded > file, preserving the original file and name unchanged, use > > convert-ly myfile.ly > mynewfile.ly > " > > I get (under windows 7) > > > close failed: [Errno 9] Bad file descriptor > > with an older version there is: > > convert-ly.py (GNU LilyPond) 2.14.2 > Processing `myfile.ly'... > Applying conversion: convert-ly.py: error: : Unable to open file > convert-ly.py: error: : Unable to open file > convert-ly.py: error: : Unable to open file > convert-ly.py: error: : Unable to open file > convert-ly.py: error: : Unable to open file > convert-ly.py: error: : Unable to open file > convert-ly.py: error: : Unable to open file > > anything known about that? > > Eluze > > > > -- > View this message in context: > http://lilypond.1069038.n5.nabble.com/convert-ly-from-the-commandline-under-windows-corrupted-tp149284.html > Sent from the Bugs mailing list archive at Nabble.com. > > See: http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/redirection.mspx?mfr=true Do any of these others work? I am guessing this is (yet another) imitation of the cmd environment and you need to use a different re-direct or some odd use of quotes. Out of curiosity (as you on Windows 7) if you run powershell Then get that PS env. then issue the convert command there does this work? James _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond