Re: Issue 943 in lilypond: input/regression/slur-broken-trend.ly broken

Updates: Status: Fixed Labels: -Patch fixed_2_13_20 Comment #25 on issue 943 by pnorcks: input/regression/slur-broken-trend.ly broken http://code.google.com/p/lilypond/issues/detail?id=943 (No comment was entered for this change.) ___

Re: Issue 507 in lilypond: fails to compile file on windows SMB share

Comment #1 on issue 507 by jermitts: fails to compile file on windows SMB share http://code.google.com/p/lilypond/issues/detail?id=507 I can confirm that this bug exists in 2.12.3.1 modified 12/15/2009 2:57 PM on Windows 7. This is especially a problem if your user folders (desktop, docum

Re: Re: Connected arpeggios may collide with previos chord.

I think the problem which cause this, is that lilypond obvious calculates the spacing as if the arpeggios were splitted. BTW, there seems to be another issue regarding arpeggios: When you have an Ossia PianoStaff, formatted smaller, the connected arpeggios are not scaled, but the normal arpeggios

Re: Connected arpeggios may collide with previos chord.

On Mon Apr 26, 17:44 Robert Clausecker wrote: > No, it's not the same issue. In issue 931, there are two chords at the > same moment, but I have two following chords, which are colliding. The > attached image shows the collision. Yes, it seems to be different. Now i can tell just that in Your exa