Pierre Perol-Schneider <pierre.schneider.pa...@gmail.com> writes: > Hi James, > > 2014-06-30 18:21 GMT+02:00 James <pkx1...@gmail.com>: > >> >> So are you saying we need to update the documentation? >> > > Yes, I think it could be a good thing to add somehow explanations for > repeats in parallelMusic mode. > But I'll send an email to the bug list regarding this. > > >> Remember that tagging LSR example with Docs doesn't put it in the Notation >> Reference. For snippets to be included in the NR they need to be explicitly >> in $LILYPOND_GIT/Documentation/snippets/.. and then referenced by the >> appropriate Texinfo entry in the Manual's *.tely files. >> > > Ok. > Well, up to now I use to tagg snippets I found intersting (very few in > fact), counting on the LSR mods (Harm?) to decide wether it should be added > to the manual or not. But I know I should send it to lilypond-devel.
I think that this is a case where it is close to impossible to write comprehensible advice regarding when to use what workaround for which reason. So I decided to fix this instead. Tracker issue: 3984 (http://code.google.com/p/lilypond/issues/detail?id=3984) Rietveld issue: 111800043 (http://codereview.appspot.com/111800043) Issue description: Let \parallelMusic cope with \repeat .. \alternative \parallelMusic's recursive decent only worked for comparatively simple cases. It now should be able to deal with complex constructs gracefully. However, this fix does not have regtests. I would appreciate it if you could cook up a few short but difficult use cases for placing in the regtests. -- David Kastrup _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
