Re: Length-1 tuplets crash LilyPond (with strict-note-spacing & tupletFullLength)

[David Kastrup]

Simon Albrecht <address@hidden> writes:

> On 16.09.2015 23:04, Trevor Bača wrote:
>> \version "2.19.27"
>>
>> \layout {
>>      \context {
>>          \Score
>>          \override SpacingSpanner #'strict-note-spacing = ##t
>>          tupletFullLength = ##t
>>      }
>> }
>>
>> \new Staff {
>>      \time 1/8
>>      \times 2/3 {
>>          c'8.
>>      }
>>      \time 5/8
>>      \times 2/3 {
>>          c'8.
>>          c'8.
>>          c'8.
>>          c'8.
>>          c'8.
>>      }
>> }
> <snip>
>> The bug is present under 2.19.26 and 2.19.27; I haven't tested under early
>> versions.
>
> Up to 2.19.20, there is no error, but the output is bad (see attached).
> From 2.19.22, the error occurs.

This is a failed assertion, so I expect the difference in behavior for
released versions to be accountable to issue 2787, version 2.19.21.

In other words, I expect the code to be equally bad before version
2.19.22 but be silent about it unless compiled with
--disable-optimising.

-- 
David Kastrup