Pierre Perol-Schneider <pierre.schneider.pa...@gmail.com> writes: > 2011/11/28 David Kastrup <d...@gnu.org> >> Pierre Perol-Schneider <pierre.schneider.pa...@gmail.com> writes:
[...] >> The syntax has changed in 2.15.10. If you had updated your file using >> >> convert-ly -ed >> >> on the last working version of that file (with a \version string >> corresponding to a version that worked before the change) instead of >> manually changing the \version string, the changes would have been >> made automatically for you. > Oups... sorry ! Well, that's something you have to expect occasionally when following the unstable versions. It's not like you are the only one who gets surprised. As a rule of thumb: _never_ change a \version string yourself once you have written it. That's the business of convert-ly. Actually, if you write the \version string the first time, it might even be a good idea to specify the last version you think you know from reading its documentation, and then run convert-ly when Lilypond complains. I don't think we advertise this enough. -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
