A change that convert-ly -ed would have been able to do unattended _if_
one had bothered running it on the file.
I don't like processes running unattended on my code ;-)
And yes, I actually prefer updating manually, to understand the changes.
Now I am using 2.15.26 for my daily work, because I updated my own
shortcuts/extensions ...
and now this is a place to give you a warm *thank you David* (and who
else worked on it) for the changes to the parser!
I have to touch pre-2.15-code, but it is an amazing cleanup!
And a warm *thank you lily-developers* for a much more stable 2.15-run
than the 2.13!
This might be wrong for others ... but I can use current dev, with 2.13
there where issues preventing it.
The \version header is there for a reason. Any suggestions where this
information needs to be for people to actually notice it?
At least, the version info on LSR could be more prominent - it relies on
2.12, not 2.14 (=current stable)?
And if I simply download a snippet, I receive a *.ly without a \version
line (its only in the comments).
Cheers, Jan-Peter
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
