Mats Bengtsson wrote:
Please always try to run convert-ly on your old files before
reporting a problem with a newer version. If you want to follow
the quick upgrades in the development versions, you may have to
read the ChangeLog to be able to catch up with all the changes.
(In this particular cas
Please always try to run convert-ly on your old files before
reporting a problem with a newer version. If you want to follow
the quick upgrades in the development versions, you may have to
read the ChangeLog to be able to catch up with all the changes.
(In this particular case, I notice that the re
try convert-ly.
[EMAIL PROTECTED] writes:
> With Pedro's packages for Debian sid a test file:
>
> #(set-staff-size 20)
>
> \score {
> <<
> \context Staff = flute { a4 b c d }
> >>
> }
>
> which works in 2.1.12 when run with 2.1.13 gives:
>
> [EMAIL PROTECTED]:~/music/pima$ lilypon
With Pedro's packages for Debian sid a test file:
#(set-staff-size 20)
\score {
<<
\context Staff = flute { a4 b c d }
>>
}
which works in 2.1.12 when run with 2.1.13 gives:
[EMAIL PROTECTED]:~/music/pima$ lilypond ../test/dy2test.ly
lilypond (GNU LilyPond) 2.1.13
Running usr...
Now pro
With Pedro's packages for Debian sid a test file:
#(set-staff-size 20)
\score {
<<
\context Staff = flute { a4 b c d }
>>
}
I see that I left out \notes in this simple example but I was getting
the same failure with all the files I tested as I reduced the example
too far.
Paul