Hi Jan-Peter,
thanks for the explanation. Right now I am fiddling around with Christophers
idea of splitting up the files in content-files and layout-files. I had this
before and just changed… Oh, well. It sounds logical to me though. and working
with functions is just copy and paste for me, because I don't now the code and
couldn't find an error nor tweak the options.
Thanks also to the others, that gave their comments. Now I have to ponder the
answers. I fear though, I will be back again with more questions… ;-)
best regards,
Kai
Am 25.6.2012 um 11:40 schrieb Jan-Peter Voigt:
>
>> Hi David, what do you mean by assignments? I'm not a native speaker and not
>> familiar with programming. Is assignments a fix set of command?
>>
>> Kai
>>
> Hello Kai,
> it's the assignment of a variable in lily-syntax:
>
> --snip--
> % allowed
> musik = \relative c'' { bes a c b }
>
> % not allowed
> \score {
> musik = \relative c'' { bes a c b }
> }
> --snip--
>
> that means, that a construct [var = value] (without []) may never be inside
> { ... } or << ... >>
>
> You might trick that:
> --snip--
>
> parserDefine = #(define-music-function (parser location name mus)(symbol?
> not-null?)
>
> (ly:parser-define! parser name mus)
>
> (make-music 'SequentialMusic 'void #t))
>
> --snip--
> and then use
> \parserDefine #'musik \relative c'' { c e d b }
>
>
> parserDefine now is a music-function and can be used anywhere. This way the
> variable musik can be assigned and afterwords called via \musik
>
> ... but I woudn't recommend it! This might have *side-effects* and can lead
> to badly organized code!
>
> HTH
> Cheers, Jan-Peter
>
>
> _______________________________________________
> lilypond-user mailing list
> [email protected]
> https://lists.gnu.org/mailman/listinfo/lilypond-user
Mit freundlichen Grüßen
K. Lautenschläger
---
[email protected]
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
