Re: Problem with music function in 2.15.18

[David Kastrup]

Nick Payne <address@hidden> writes:

> There's a music function I use in virtually every guitar score I've
> done with Lilypond, to move glissandi that I use to indicate that a
> finger should be kept on a string when moving frets. I just downloaded
> and installed 2.15.18 (Linux amd64 version running on Ubuntu 10.04),
> and the parameters to the function no longer seem to be being
> recognised as the correct type. The short example below shows the
> problem.
>
> \version "2.15.18"
>
> \language "english"
>
> guide = #(define-music-function (parser location padleft padright
> shift missacc) (number? number? pair? boolean?) #{
>     \once \override Glissando #'bound-details #'left #'padding = #$padleft
>     \once \override Glissando #'bound-details #'right #'padding =

You know what convert-ly is for?  If you have a working source, _don't_
bump its version string manually.  That makes a mockery of its intent.

Instead, run convert-ly -e on the file.  It will not just update the
version string, but also the corresponding syntax.

Your version string currently lies and claims that the file has been
updated to version 2.15.18 when it hasn't.  Put the version down to the
last version that has worked, then run convert-ly.

Don't worry that the result looks too easy to be true.  Just try it.

-- 
David Kastrup