On Mon, Nov 30, 2009 at 5:43 PM, Robin Bannister wrote:
> 821's priority should therefore be not Medium but Regression.
Thanks, updated.
Cheers,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lil
Robin Bannister wrote:
This of course also applies to the issue(s) I referenced in my followup
http://lists.gnu.org/archive/html/bug-lilypond/2009-10/msg00294.html
I am unsuccessful again. I will just spell out the main point:
The collision snippet which is registered as issue 821
http://co
On Sun, Nov 29, 2009 at 11:16 AM, Robin Bannister wrote:
> The priority should therefore be not Medium but Regression.
Thanks, updated.
Cheers,
Valentin
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lily
Seeing the issues in the priority/type table format made me realise
how important it is to get these categories right.
This thread (span arpeggio and single notes)
supplied the collision snippet which is registered as issue 880
http://code.google.com/p/lilypond/issues/detail?id=880
No
Valentin Villenave wrote:
While waiting for acknowledgement,
I have come across several online examples of this.
Yes, I suspect these issues have the same underlying cause (though I
opened multiple issues since I'm not sure what that cause might be).
Well, that was my point
On Wed, Oct 21, 2009 at 2:53 PM, Robin Bannister wrote:
> While waiting for acknowledgement,
> I have come across several online examples of this.
Yes, I suspect these issues have the same underlying cause (though I
opened multiple issues since I'm not sure what that cause might be).
Regards,
Va
On Tue, Sep 29, 2009 at 11:19 PM, Robin Bannister wrote:
Greetings,
> When the connectArpeggios mode includes an arpeggio on a single note,
> the resultant span arpeggio may collide with a previous note.
Added (with much delay) as
http://code.google.com/p/lilypond/issues/detail?id=880
Cheers,
While waiting for acknowledgement,
I have come across several online examples of this.
Their severity depends on how dense the local layout is.
Neighboring things may push the faulty arpeggio that bit too far.
And less severe cases may go unnoticed, e.g. the Ravel;
the tight layout may look appro
>
When the connectArpeggios mode includes an arpeggio on a single note,
the resultant span arpeggio may collide with a previous note.
%%
\version "2.12.1"
d = { d'16 d'16 d'16 d'16 d'4 \arpeggio } % single note
sdf = { s4 4 \arpe
