Hello,
I currently work on a mass setting by Palestrina. The music is stored in
variables sopranoK, altoK, tenorK, bassK, sopranoVerseK, …, sopranoG,
altoG, etc. etc. for the different parts and movements. Now since I need
a separate \score block for each movement, but these score blocks will
Simon Albrecht simon.albre...@mail.de writes:
Hello,
I currently work on a mass setting by Palestrina. The music is stored
in variables sopranoK, altoK, tenorK, bassK, sopranoVerseK, …,
sopranoG, altoG, etc. etc. for the different parts and movements. Now
since I need a separate \score
for me:
\version 2.18.0
scoreSetup =
#(define-music-function
(parser location letter)
(string?)
#{
\score {
{ a b c d }
}
#})
\scoreSetup K
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/composing-Scheme-identifiers-tp160030p160040.html
Sent from
Paul Morris p...@paulwmorris.com writes:
Simon Albrecht-2 wrote
scoreSetup =
#(define-music-function
(parser location letter)
(string?)
#{
\score {
\new Staff = bassus \with { instrumentName = bassus }
% this is supposed to give the same result as @code{\bassK} for example…
{ \scoreSetup ... }
as long as what you want in \scoreSetup does not include output or
header definitions.
That's true, but it's still nice to be able to do it (and learn how to do
it).
Thanks again,
-Paul
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/composing-Scheme
