Re: Problem with Codas

[Carl Sorensen]

On 9/19/17 5:33 PM, "David Kastrup" <address@hidden> wrote:

>Shamus Hammons <address@hidden> writes:
>
>> On 09/17/2017 01:50 AM, David Kastrup wrote:
>>> Carl Sorensen <address@hidden> writes:
>>> 
>>>> On 9/16/17 8:09 AM, "Shamus Hammons" <address@hidden> wrote:
>>>>
>>>>> I have a dream, that one day Lilypond will make codas first class
>>>>> citizens instead of having to exist as a series of ugly hacks. In
>>>>>that
>>>>> day, I could simply write \coda (with maybe some options) and
>>>>>Lilypond
>>>>> would automagically do the right thing. Alas, that day is not today.
>>>>>:-(
>>>>
>>>> What do you consider the "right thing" to be with a coda?
>>> 
>>> \repeat coda 2 { %{ segno appears here %} common part }
>>>              \alternative { { %{ coda sign here %} first part }
>>>                             { %{ actual coda formatted here %} coda } }
>>
>> This looks perfectly reasonable to me. :-) How can I help make this
>>happen?
>
>This requires good LilyPond code for formatting the coda, and
>integration with the repeat structures.  The good formatting code can be
>done by someone versed in LilyPond/Scheme.

My original question was not about the input format, but rather about the
appropriate output formatting for the coda.

It seems like the reason the original code was "ugly hacks" and didn't
work was because the formatting problem was very difficult for some corner
cases.  I was hopping to get Shamus to describe the formatting rules he
would like to have for codas, because that (not the input structure) is
where the "automagic  layout" happens.

Thanks,

Carl