On Fri, Apr 27, 2012 at 11:04:20AM +0200, David Kastrup wrote: > James <pkx1...@gmail.com> writes: > > > This also occurs on 2.14.2. We've had some changes made to > > articulate.ly recently for 2.15.x - phew! So this isn't a regression > > in LP code. > > articulate.ly is not really ported to the new way of working with > EventChord: it just converts the new representation to the old one at > invocation time and goes from there with the old code.
Although there is an open tracker against articulate.ly http://code.google.com/p/lilypond/issues/detail?id=1749 it is specialised and does not cover the behaviour reported by Nick and confirmed by James. I've created an issue tracker for this: http://code.google.com/p/lilypond/issues/detail?id=2501 Cheers, Colin. -- Colin Hall _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
