While waiting for acknowledgement, I have come across several online examples of this.
Their severity depends on how dense the local layout is. Neighboring things may push the faulty arpeggio that bit too far. And less severe cases may go unnoticed, e.g. the Ravel; the tight layout may look appropriate, but it is fortuitous. The constrain-hidden-positions workaround is effective in all these cases. (Regression: the first three cases run with 2.10.33 and ragged-right.) Issue 601 comment 2 http://code.google.com/p/lilypond/issues/detail?id=601#c2 Issue 821 http://code.google.com/p/lilypond/issues/detail?id=821 LSR 410 http://lsr.dsi.unimi.it/LSR/Item?id=410 NR 2.2 keyboard headword (Ravel) http://lilypond.org/doc/v2.12/Documentation/user/lilypond/Keyboard-and-other-multi_002dstaff-instruments Cheers, Robin _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
