[Lilypond-auto] Issue 2500 in lilypond: articulate.ly is not ported to the new way of working with > EventChord

[lilypond]

Status: Accepted
Owner: ----
Labels: Type-Enhancement

New issue 2500 by address@hidden: articulate.ly is not ported to the new  
way of working with > EventChord
http://code.google.com/p/lilypond/issues/detail?id=2500

On 27 April 2012 02:42, Nick Payne <address@hidden> wrote:
> The example below builds without error and gives the output I want.  
> However,
> if I include articulate.ly, then the output is garbaged even though I
> haven't used \unfoldRepeats \articulate, and I get the following warnings  
> in
> the log:

> /home/nick/lilypond/examples/test.ly:8:59: warning: already have a beam
>    \times 4/6 { a32[( g) fis( g) \appoggiatura { fis16
>                                                           [ g] } a32 g] }
> warning: cannot end slur
> warning: unterminated slur

> %=====================================
> \version "2.15.37"

> %\include "articulate.ly"

> \relative c'' {
>    \times 4/6 { a32[( g) fis( g) \appoggiatura { fis16[ g] } a32 g] }
> }
> %=====================================


> Nick


--snip--

On 27 April 2012 10:04, David Kastrup <address@hidden> wrote:
> James <address@hidden> 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.

--snip--