Re: Segfault from unusual time signatures

2014-10-26 Thread Dan Eble
Urs Liska googlemail.com> writes: > > Am 26.10.2014 21:39, schrieb David Kastrup: > > Urs Liska googlemail.com> writes: > > > >> Am 26.10.2014 21:19, schrieb Dan Eble: > >>> % This input caused a segfault on OS X Yosemite with Lilypond 2.19.15. > >>> \version "2.19.0" > >>> \new Staff { > >>>

rename single-digit time signature style

2014-10-26 Thread Dan Eble
% The time signature style "single-digit" is poorly named because it % can display multiple digits. "single-number" would be a better % name. \version "2.19.0" \new Staff { \override Staff.TimeSignature.style = #'single-digit \time 10/1 d'1 } ___

Re: Segfault from unusual time signatures

2014-10-26 Thread Urs Liska
Am 26.10.2014 21:39, schrieb David Kastrup: Urs Liska writes: Am 26.10.2014 21:19, schrieb Dan Eble: % This input caused a segfault on OS X Yosemite with Lilypond 2.19.15. \version "2.19.0" \new Staff { \relative d' { \time 8/1024 d128 | \time 9/1 d1 } } Compiled wi

Re: Segfault from unusual time signatures

2014-10-26 Thread David Kastrup
Urs Liska writes: > Am 26.10.2014 21:19, schrieb Dan Eble: >> % This input caused a segfault on OS X Yosemite with Lilypond 2.19.15. >> \version "2.19.0" >> \new Staff { >>\relative d' { >> \time 8/1024 d128 | >> \time 9/1 d1 >>} >> } >> >> > > Compiled without problem on a

Re: Segfault from unusual time signatures

2014-10-26 Thread Urs Liska
Am 26.10.2014 21:19, schrieb Dan Eble: % This input caused a segfault on OS X Yosemite with Lilypond 2.19.15. \version "2.19.0" \new Staff { \relative d' { \time 8/1024 d128 | \time 9/1 d1 } } Compiled without problem on a build from current master (Debian Linux) Urs ___

"trying to freeze in time" from unusual time signatures

2014-10-26 Thread Dan Eble
% Produces "programming error: trying to freeze in time". % There are also extra bar lines in the output. \version "2.19.0" \new Staff { \relative d' { \time 1/9 d4*4/9 \time 8/1024 d128 \time 10/6 d1*10/6 \time 9/1 d1 } } _

Segfault from unusual time signatures

2014-10-26 Thread Dan Eble
% This input caused a segfault on OS X Yosemite with Lilypond 2.19.15. \version "2.19.0" \new Staff { \relative d' { \time 8/1024 d128 | \time 9/1 d1 } } ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/l

Re: Memory leak(?) with large numerator in time signature

2014-10-26 Thread David Kastrup
Dan Eble writes: >> I'm not top posting. > > \version "2.19.0" > << > \time 9/1 f'1 >>> Probably an artifact of LilyPond's own "Rational" implementation's limited precision. At some point of time, we should replace it with GUILE rationals. -- David Kastrup

Loop with zero time signature

2014-10-26 Thread Dan Eble
> I'm not top posting % Lilypond seems loop on this, but memory consumption does not grow. \version "2.19.0" << \time 0/1 \partial 4 f'4 >> ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Memory leak(?) with large numerator in time signature

2014-10-26 Thread Dan Eble
> I'm not top posting. \version "2.19.0" << \time 9/1 f'1 >> ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

MusicXML test suite: Bug in 41f-StaffGroups-Overlapping.xml

2014-10-26 Thread Andreas Wenger
The test description is wrong: "In this case, one group (with a square bracket) goes from staff 2 to 4) and another group (with a curly bracket) goes from staff 3 to 5." It should be "one group ... goes from staff 1 to 4", since group 1 starts already before part P1. _