Paul Scott <[email protected]> writes: > On Tue, Oct 17, 2017 at 08:14:06PM +0200, David Kastrup wrote: >> Paul Scott <[email protected]> writes: >> >> > On Tue, Oct 17, 2017 at 08:03:44PM +0200, David Kastrup wrote: >> >> >> >> That is the whole _point_ of a warning: LilyPond is able to complete >> >> the job which _may_ mean that it works perfectly but it cannot be >> >> sure. For example, because it does not know for which version some >> >> file has been written. >> > >> > I am trying to use version statements correctly and efficiently. >> > Why doesn't my example work or how should I do it differenly? >> >> LilyPond expects a \version statement in the main file. Put one there. >> convert-ly can do this for you (probably leave off the -d option). > > In all my projects the .ily file with the \version statement is the > main file with the music in it. There is .ly file for each > instrument/part which includes the .ily file. I haven't had to put a > \version statement in each .ly file until 2.19.80.
Yes. This behavior caused problems, so it was changed. Updating a .ily file does not magically update .ly files including them, and .ily files can easily be from a different source than the .ly files. LilyPond does not require a \version statement for every file of a session (but checks them when available), but the main file now should have one or a warning will get produced. -- David Kastrup _______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
