> the custom function helps for readability and reuse of score snippets.
Hmm....let's see.
Your preferred version:
%%%%%%%%%%
\version "2.19.24"
%=============================================
% WRITE SCORE
%
%=============================================
#(define-markup-command (writeScore layout props music) (ly:music?)
(let ((score (ly:make-score music))
(score-layout (ly:output-def-clone $defaultlayout)))
;; possibly, change some settings in the \layout block
%(ly:output-def-set-variable! score-layout 'indent 0)
;; add the \layout block to the score
(ly:score-add-output-def! score score-layout)
(interpret-markup layout props (markup #:score score) )
))
musicA = { c' d' e' }
musicB = { c'''' d'''' e'''' }
\markup {
"this should be aligned" \writeScore #musicA
"with this " \writeScore #musicB
}
%%%%%%%%%%
My preferred version:
%%%%%%%%%%
\version "2.19.24"
\paper { indent = 0 }
musicA = { c' d' e' }
musicB = { c'''' d'''' e'''' }
\markup {
"this should be aligned" \score { \musicA }
"with this " \score { \musicB }
}
%%%%%%%%%%
I don't see any benefit in terms of readability in the version with the
custom function. Reuse of score snippets is identical. No gain either.
I'm not able to attribute being more concise to either version.
The whole argument is somewhat nitpicking though. If you prefer your
custom function that's fine.
Kind regards,
Michael
--
Michael Gerdau email: m...@qata.de
GPG-keys available on request or at public keyserver
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
