Re: Layout going screwy

[David Kastrup]

Raphael Mankin <raph@mankin.org.uk> writes:

> On 04/09/2024 11:15, David Kastrup wrote:
>> Raphael Mankin <raph@mankin.org.uk> writes:
>> 
>>> For reasons that not concern us I am  re-typing Cole Porter's Anything
>>> Goes. I get as far as the key change after bar 20 but then the layout
>>> goes wild: no bar numbers, line breaks fail, stray bar on the end.
>>>
>>> I have checked and double checked this, but I cannot see what is
>>> wrong. Any help will be appreciated.
>>>
>>> See attachments
>> I just placed a bar check | before each of your % Bar xxx comments
>> (why
>> keep this important information from LilyPond by hiding it away in a
>> comment) and got the first bar check warning between those lines:
>> |  %Bar 11
>>    r4 g8. a16 b8. a16. g4
>>    b4 c8 d8~ d4 r4
>>    c2. g4
>> |  % Bar14
>> It's easy to see that the a16. is not matched by anything else
>> producing
>> an odd multiple of a 1/32 note.
>
> I was looking for those,  but missed that one
>
> Thank you. An extra pair of eyes etc..

No extra pair of eyes.  I didn't bother combing through your source code
manually like you did.  I just added the bar checks where your comments
already indicated that a bar should be.  As I said: there is no point in
keeping the bar information from LilyPond since LilyPond is pretty good
at spotting inconsistencies.

When organisation of the source is important enough to you that you add
comments like

% Bar14

there is no point whatsoever not to write

| % Bar14 instead

or (as a coding pattern)

       |% 14

If you put the information in the source anyway, give LilyPond a chance
to utilize it.

-- 
David Kastrup