[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Issue 1996 in lilypond: Bar check inside a slur causes fatal error
From: |
lilypond |
Subject: |
Issue 1996 in lilypond: Bar check inside a slur causes fatal error |
Date: |
Sun, 30 Oct 2011 02:54:20 +0000 |
Status: Accepted
Owner: ----
Labels: Type-Defect
New issue 1996 by address@hidden: Bar check inside a slur causes
fatal error
http://code.google.com/p/lilypond/issues/detail?id=1996
Putting a bar check inside a slur causes a fatal error. the followiong code:
\version "2.15.16"
\relative c' {
c4 c c c | (a) c c c
}
gives this:
/tmp/frescobaldi-gs9BEy/tmp4Jxaqd/document.ly:4:15: error: syntax error,
unexpected '('
c4 c c c |
(a) c c c
/tmp/frescobaldi-gs9BEy/tmp4Jxaqd/document.ly:3:0: error: errors found,
ignoring music expression
\relative c' {
fatal error: failed files: "/tmp/frescobaldi-gs9BEy/tmp4Jxaqd/document.ly"
Exited with return code 1.
Taking out the bar check allows the code to compile, and ties, between same
pitches, are allowed across a bar check. This doesn't seem to have worked
in 2.12.3 either, so I don't know if it's a regression. If there isn't a
simple code fix, this could also be the subject of a Known Issue.
- Issue 1996 in lilypond: Bar check inside a slur causes fatal error,
lilypond <=