lilypond-devel
[Top][All Lists]
Advanced

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

Re: [doc fact-check] variables in lilypond scheme


From: Nicolas Sceaux
Subject: Re: [doc fact-check] variables in lilypond scheme
Date: Sun, 29 Oct 2006 10:34:10 +0100
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (darwin)

Graham Percival <address@hidden> writes:

> Should variables in define-music-function have #s ?
>
> padText = #(define-music-function (parser location padding) (number?)
> #{
>
> % Both of these lines work.  Which should be in the docs?
> %  \once \override TextScript #'padding = $padding
>   \once \override TextScript #'padding = #$padding
> #})
>
> \relative c''' {
>   c4^"piu mosso" b a b
>   \padText #1.8
>   c4^"piu mosso" d e f
>   \padText #2.6
>   c4^"piu mosso" fis a g
> }

I would write #$padding iso $padding, but cannot come with a convincing
rationale (except that IMHO \identifer style variable should be better
used for music expressions, and plain scheme variable for other types,
like numbers, like padding).

nicolas




reply via email to

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