lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Moving from lilypond 2.18 to 2.19


From: David Kastrup
Subject: Re: Moving from lilypond 2.18 to 2.19
Date: Wed, 22 Nov 2017 17:33:43 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux)

Matt Wallis <address@hidden> writes:

> Here is a small example:
>
>    \include "english.ly"
>
>    global = {
>       \time 4/4
>       \tempo 4 = 96
>    }
>    \score {
>       \new Staff {
>         \clef treble
>         \global
>         \relative c' { c1 }
>       }
>       \midi { \global }
>    }
>
> ... that provokes this error in 2.19.80:
>    In procedure ly:add-context-mod in expression (ly:add-context-mod
>    mods (list # #)):
>    /opt/local/share/lilypond/2.19.80/scm/lily-library.scm:375:14: Wrong
>    type argument in position 1 (expecting Context_mod): #f
>
> ... but works fine in 2.18.2

You know: the minimal example would have been

\midi { \time 4/4 }

and that would have saved adding a lot of other explanation:

> The error is triggered by the use of \global in the midi block when
> global contains "\time 4/4". Incidentally, if the midi block contains
> a \key signature, but no \time, then it works fine in 2.19.80.
>
> I can understand that \time is irrelevant to midi (as is \key?), but
> I've used this lazily in the past because it works.

It is intended to work.  I am surprised that this has been overlooked
for so long.

> I'd be interested to know if you think the correct fix is to restore
> the original 2.18.2 behaviour, or to output an error message that
> identifies the line that causes the problem.

I'm currently writing two fixes.  One makes a better warning, the other
does not trigger it.

-- 
David Kastrup



reply via email to

[Prev in Thread] Current Thread [Next in Thread]