Thomas Morley <thomasmorle...@gmail.com> writes: > Though, why it is that arbitrary? > > Look at this variation and the attached image: > > \version "2.19.29" > #(define test-nmbrs > (let ((nmbrs (circular-list 1 2 3 4))) > (lambda (grob) > (let ((n (car nmbrs))) > (set! nmbrs (cdr nmbrs)) > (grob-interpret-markup grob (number->string n)))))) > > { > \repeat unfold 8 { > \once \override TextScript.stencil = #test-nmbrs > c''4^\markup "foo" > } > }
Well, it is exactly 2 variants of 1, 2, 3, 4 each. I suspect that the order of grob evaluation at some point when a system is printed depends on the order of memory addresses. Find that point and you'll likely also have the culprit for various other stuff behaving non-deterministically, like what is drawn on top of what and other things frequently turning up in "make check". -- David Kastrup _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user