[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Lilypond-auto] Issue 2501 in lilypond: Port articulate to the new way o
From: |
lilypond |
Subject: |
[Lilypond-auto] Issue 2501 in lilypond: Port articulate to the new way of working with EventChord |
Date: |
Fri, 27 Apr 2012 09:45:32 +0000 |
Status: Accepted
Owner: ----
Labels: Type-Defect
New issue 2501 by address@hidden: Port articulate to the new way of
working with EventChord
http://code.google.com/p/lilypond/issues/detail?id=2501
Reported on lilypond-user by Nick Payne:
http://lists.gnu.org/archive/html/lilypond-user/2012-04/msg00464.html
Confirmed by James:
http://lists.gnu.org/archive/html/lilypond-user/2012-04/msg00472.html
Analysis from David Kastrup:
http://lists.gnu.org/archive/html/lilypond-user/2012-04/msg00473.html
Original posting to lilypond-user including tiny example follows:
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
- [Lilypond-auto] Issue 2501 in lilypond: Port articulate to the new way of working with EventChord,
lilypond <=