documentation:

-d or --diff-version-update is missing
-t is missing (only --to= is there)
-l loglevel should mention that levels must be specified UPPERCASE

bugs:

running without parameters produces 8 errors messages:

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
convert-ly.py: error: : Unable to open file
convert-ly.py: warning: There were 8 errors.

(I'd expect the help text to display)

for any option - or file - you add there is a reduction of one error. 

so invoking 

convert-ly -e abc.ly abc.ly  abc.ly abc.ly abc.ly abc.ly abc.ly abc.ly

does not produce any warnings!

------------------------------------
in my cmd I have LANG=en_US.UTF-8
the following command doesn't accept utf-8 characters in the file name:

D:\Data\lytest>convert-ly -e bääh.ly
convert-ly.py (GNU LilyPond) 2.17.5

convert-ly.py: error: b├Á├Áh.ly: Unable to open file
convert-ly.py: error: : Unable to open file
convert-ly.py: error: : Unable to open file
...
...
convert-ly.py: warning: There were 6 errors.



------------------------------
when converting a file containing these lines:

{ a b c d }
\version "2.15.0"

with convert-ly -e     abc.ly    the new version is 2.17.5 (seems correct to
me)
with convert-ly -e -d abc.ly    the new version is 2.16.0

although no conversion has been applied.
shouldn't 2.15.0 be the version after conversion with -d? maybe I'm not
understanding correctly

thanks for taking time to look at this and discuss what should be done!

Eluze



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/confused-by-convert-ly-2-17-5-tp135108.html
Sent from the Bugs mailing list archive at Nabble.com.

_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to