On 11/27/13 8:04 AM, "David Kastrup" <address@hidden> wrote:
Urs Liska <address@hidden> writes:
But also in this case I would come back and suggest including functions
like
originalBreak =
#(define-music-function (parser location)()
( #{ \tag #'keep-original-breaks \break #} ))
in LilyPond so they are available without having to put them in
private libraries.
No. This is a special use case for a special, tool-bound workflow. It
is totally valid to want the mechanisms in place for making it easy and
straightforward to implement this special use case.
But special use cases themselves belong in special include files.
Again, if LilyPond is lacking mechanisms for conveniently including
special-case include files, that is something worth fixing.
Would you be opposed to having a file original-breaks.ly that defined
originalBreak as part of the distribution?
We have a precedent of doing some of this already. For example, we have
predefined-guitar-fretboards.ly, predefined-ukulele-fretboards.ly, and
predefined-mandolin-fretboards.ly that provide special use cases for the
predefined fretboard general case.
If the general case were added, and a special include were included, then
it seems like we'd have both David's wish for keeping things general and
Urs's wish for having an easily-used tool for the specific use case.