[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 586 in lilypond: Cross-staff slur causes a weird output
From: |
lilypond |
Subject: |
Re: Issue 586 in lilypond: Cross-staff slur causes a weird output |
Date: |
Fri, 16 Dec 2011 14:28:40 +0000 |
Comment #8 on issue 586 by address@hidden: Cross-staff slur causes a
weird output
http://code.google.com/p/lilypond/issues/detail?id=586
That's fine - the two branches will usually yield equivalent results (they
rarely differ by more than a few commits at a time).
I just compiled with staging and also got a clean result.
Can a few other people please compile this to see what comes out?
Cheers,
MS
- Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 2011/12/11
- Message not available
- Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 2011/12/16
- Message not available
- Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 2011/12/16
- Message not available
- Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 2011/12/16
- Message not available
- Re: Issue 586 in lilypond: Cross-staff slur causes a weird output,
lilypond <=
- Message not available
- Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 2011/12/18
- Message not available
- Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 2011/12/30
- Message not available
- Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 2011/12/30