[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the s
From: |
lilypond |
Subject: |
Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning |
Date: |
Mon, 13 Feb 2012 12:24:50 +0000 |
Updates:
Summary: Concurrent slurs that start and end at the same moment should not
produce a warning
Comment #10 on issue 1967 by address@hidden: Concurrent slurs that
start and end at the same moment should not produce a warning
http://code.google.com/p/lilypond/issues/detail?id=1967
Ah, now that you point it out, I suppose that my implementation of that
warning is to blame. In 2.12, no warning was printed at all if a second
slur started while another slur was already active. I.e. the following
snippet was not producing ANY warning in 2.12.3:
\version "2.12.3"
\relative c'' { c4( d( g g) }
I fixed this, but did apparently not consider the case that the second slur
would start/end from within the same chord/moment (which is perfectly legal
and should not produce a warning...).
So, a simpler test case for this bug is:
\version "2.12.3"
\new Voice \relative c'' { << { c( d) } { e( f) } >> }
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning,
lilypond <=
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/13
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/13
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/13
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/13
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/13
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end atthe same moment should not produce a warning, Trevor Daniels, 2012/02/13
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/13
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15
- Message not available
- Re: Issue 1967 in lilypond: Concurrent slurs that start and end at the same moment should not produce a warning, lilypond, 2012/02/15