Re: Inconsistent "no \version statement" warning

[David Kastrup]

Dan Eble <address@hidden> writes:

> I don’t know who might care about this, but when Lilypond processes an
> empty file, it prints a warning about not finding a \version
> statement, yet when it processes a file containing only \include
> “english.ly”, it does not mention that there is no \version statement.

Looks like we should outcomment the \version statements in files
intended for inclusion by the user.  That way they will not mess with
the version of the session while still being accessible to convert-ly.

Or we make \include restore the version-seen status at its end (or let
it only be set in main input).

-- 
David Kastrup