For this particular task, you should also show the user that he can
define at the top of the input, or in a header file if he uses one,
originalBreak = \break
and insert before music where we are done with the original breaks,
originalBreak = {} %\break
That is easy enough to understand, and easy to adapt to other tasks.
https://codereview.appspot.com/150670043/diff/1/Documentation/notation/spacing.itely
File Documentation/notation/spacing.itely (right):
https://codereview.appspot.com/150670043/diff/1/Documentation/notation/spacing.itely#newcode1857
Documentation/notation/spacing.itely:1857: @end lilypond
Why not store the common music in a variable, and show
\score {\music}
\discaredOriginalBreaks
\score {\music}
?
https://codereview.appspot.com/150670043/diff/1/ly/original-breaks.ly
File ly/original-breaks.ly (right):
https://codereview.appspot.com/150670043/diff/1/ly/original-breaks.ly#newcode36
ly/original-breaks.ly:36: origBreak =
Almost religiously, LilyPond avoids abbreviation.
Maybe originalBreak ?
https://codereview.appspot.com/150670043/
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
