Re: Issue 139 in lilypond: tie misinterpreted as a slur

2011-12-08 Thread lilypond
Updates: Labels: -Priority-High Comment #13 on issue 139 by pkx1...@gmail.com: tie misinterpreted as a slur http://code.google.com/p/lilypond/issues/detail?id=139 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lil

Re: Issue 139 in lilypond: tie misinterpreted as a slur

2010-11-19 Thread lilypond
Updates: Labels: -Priority-Low Priority-High Comment #12 on issue 139 by PhilEHolmes: tie misinterpreted as a slur http://code.google.com/p/lilypond/issues/detail?id=139 Another example where there should be one tied note within a chord, but LilyPond typesets it as if it's a slur, whic

Re: Issue 139 in lilypond: tie misinterpreted as a slur

2010-03-24 Thread lilypond
Updates: Status: Accepted Comment #11 on issue 139 by percival.music.ca: tie misinterpreted as a slur http://code.google.com/p/lilypond/issues/detail?id=139 LOLwut? "Verified" means "a programmer said it was fixed, and an independant person agrees that the issue was fixed". It doesn'

Re: Issue 139 in lilypond: tie misinterpreted as a slur

2010-03-24 Thread lilypond
Updates: Status: Verified Comment #10 on issue 139 by jameseli...@googlemail.com: tie misinterpreted as a slur http://code.google.com/p/lilypond/issues/detail?id=139 (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC field

Issue 139 in lilypond: tie misinterpreted as a slur

2008-05-30 Thread codesite-noreply
Issue 139: tie misinterpreted as a slur http://code.google.com/p/lilypond/issues/detail?id=139 Comment #9 by v.villenave: (Still unfixed as of 2.11.47) Issue attribute updates: Status: Accepted Labels: -fixed_2_11_12 -- You received this message because you are listed in the ow