On Tue, Oct 17, 2017 at 04:54:47PM +0200, David Kastrup wrote:
> Paul Scott <[email protected]> writes:
>
> > I may be downloading while changes are in progress.
> >
> > I just downloaded and installed 2.19.80 (what happened to 2.19.66 through
> > 2.19.79?)
> >
> > 2.19.80 doesn't seem to see my version statements:
> >
> > plentyr3.ly:1: warning: no \version statement found, please add
> >
> > \version "2.19.80"
> >
> > for future compatibility
> >
> > Under 2.19.80 documentation:
> >
> > Changes docs refer to 2.20 and the Notation manual still seems to be for
> > 2.19.65.
>
> 2.19.80 is a prerelease for 2.20: it is not released from master but the
> stable/2.20 branch. It still counts as developer release though, so the
> developer Notation manual gets updated
> <http://lilypond.org/doc/v2.19/Documentation/notation/index.html>. It
> states "LilyPond — Notation Reference v2.19.80 (development-branch)."
> which is not entirely correct regarding the branch used. But correcting
> that while the prerelease is in progress is likely more trouble than it
> would be worth: it would be too easy to forget changing it back.
Notation manual is now correct maybe a cache issue.
\include brings the version warning as follows:
To avoid changing the version on each of my many .ly files I put the
version in a .ily which has the music and is included in each .ly which sets
up the individual part.
Here is a minimal example of my version situation:
vtest.ly:
\version "2.19.80"
\relative{ c''4 }
called by:
vtesti.ily:
\include "vtest.ly"
i.e.:
paul@joy3:~/music/tcb$ lilypond vtesti.ily
GNU LilyPond 2.19.80
Processing `vtesti.ily'
Parsing...
vtesti.ily:1: warning: no \version statement found, please add
\version "2.19.80"
for future compatibility
...
Thank you,
Paul
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
