lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lilypond-auto] Issue 2584 in lilypond: please make partcombine merg


From: lilypond
Subject: Re: [Lilypond-auto] Issue 2584 in lilypond: please make partcombine merge slurs
Date: Mon, 04 Jun 2012 08:47:23 +0000


Comment #13 on issue 2584 by address@hidden: please make partcombine merge slurs
http://code.google.com/p/lilypond/issues/detail?id=2584

Does this patch result in cases where "clearly wrong manual input gets let through and interpreted in interesting ways" ?

Version 2.15.39 interprets \relative c'' { c(( d) e) } as a nested slur (who asked for that?) but interprets \relative c'' { c( d( e)) } as an error.

After this patch we treat (( as if it were (, and )) as if ), which seems a non-interesting interpretation, and rather similar to the way Lilypond treats {\clef bass \clef bass}.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]