Dr. Chubb,
Your comment that an appoggiatura should only be one note seems to disagree
with the LilyPond documentation:
http://lilypond.org/doc/v2.15/Documentation/music-glossary/appoggiatura
>From my point of view on the Bug Squad, this doesn't appear to be a bug
unless perhaps someone feels tha
> "Nick" == Nick Payne writes:
Nick> The example below builds without error and gives the output I
Nick> want. However, if I include articulate.ly, then the output is
Nick> garbaged even though I haven't used \unfoldRepeats \articulate,
Nick> and I get the following warnings in the log:
Tha
On Fri, Apr 27, 2012 at 11:04:20AM +0200, David Kastrup wrote:
> James 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 workin
James 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
Hello,
On 27 April 2012 02:42, Nick Payne 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:
>
> /ho
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 h
