Re: convert-ly version

[Wilbert Berendsen]

Op dinsdag 19 februari 2008, schreef Mats Bengtsson:
> Wilbert Berendsen wrote:
> > Hi,
> >
> > it seems that convert-ly changes the version of the converted document to
> > the latest version convertrules.py contains a rule for.
> >
> > Would it not be better if it changes the version to the current version
> > of lilypond/convert-ly? So the document looks really up-to-date (even it
> > only the \version number changed).
>
> This is usually done (by hand) every time a new major stable version is
> released. One argument against your proposal is that if you run
> convert-ly -e *.ly then you can look at the modification time of each file
> to see if it was changed or not, whereas if we implement your proposal then
> all files will be updated even though nothing except for the \version line
> has changed. 

Ok, that's very valid.

I'm perfectly fine with the current behaviour (I run convert-ly from my 
LilyKDE IDE, using stdin and stdout, and when there is no output, I don't 
replace the editor buffer with the empty output.).

Maybe a --force option could be added to force output of the file, with the 
\version set to the current version. But it's not important.

best regards,
Wilbert Berendsen

-- 
http://www.wilbertberendsen.nl/
LilyKDE: http://lilykde.googlecode.com/