lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Suggestion: Keep original breaks


From: Carl Sorensen
Subject: Re: Suggestion: Keep original breaks
Date: Wed, 27 Nov 2013 15:25:29 +0000
User-agent: Microsoft-MacOutlook/14.3.8.130913

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.

>
>The solution to "It gets complicated when we don't cram everything into
>LilyPond where it does not belong" is not to cram everything into
>LilyPond where it does not belong, but to stop the alternatives from
>being complicated.

I completely agree with this.  And I'm delighted to see how much David's
work on improving the front end has helped to simplify LilyPond and the
same time as it's greatly improved the functionality.

David, keep pushing us to do the right thing.

Urs, keep pushing us to make things easier for the user.

When we make it easier for the user by doing the right thing, LilyPond is
way ahead.

Thanks,

Carl




reply via email to

[Prev in Thread] Current Thread [Next in Thread]