Carl Sorensen <c_soren...@byu.edu> writes:
> On 11/12/11 2:17 PM, "Nick Payne" <nick.pa...@internode.on.net> wrote:
>
>>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 =
>>#$padright
>
> I believe you now use just $padright instead of #$padright
Actually, $padright behaves more or less identical to previously in this
context. Namely, it is a gamble on Lilypond assigning a useful
syntactical class to the given expression. But you don't want a magic
syntactical class here, you just want a Scheme expression.
#$padright expressed this intent correctly previously, and now #padright
does the same.
Basically, the rule of thumb now is: if you would not have used $
outside of #{ ... #}, don't use it inside.
--
David Kastrup
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
