Issue 916 in lilypond: Broken regtest: spacing-loose-grace-linebreak.ly

Status: Accepted Owner: pnorcks Labels: Type-Defect Priority-Regression New issue 916 by pnorcks: Broken regtest: spacing-loose-grace-linebreak.ly http://code.google.com/p/lilypond/issues/detail?id=916 With current git, spacing-loose-grace-linebreak.ly fails to compile. This is the output: GNU

Re: Issue 54 in lilypond: clef moves multimeasure rest

Updates: Labels: -Priority-Regression Priority-Low Comment #9 on issue 54 by pnorcks: clef moves multimeasure rest http://code.google.com/p/lilypond/issues/detail?id=54 Okay, I reported the regression in Issue 915. Hope that's okay. -- You received this message because you are listed i

Issue 915 in lilypond: Multi-measure rests dependent on prefatory matter in other staves

Status: Accepted Owner: pnorcks Labels: Type-Defect Priority-Regression New issue 915 by pnorcks: Multi-measure rests dependent on prefatory matter in other staves http://code.google.com/p/lilypond/issues/detail?id=915 %{ The regression test `multi-measure-rest-multi-staff-center.ly' broke be

Re: Uneven empty measures

2009/11/29 Trevor Daniels : > > Francisco Vila wrote Sunday, November 29, 2009 8:20 PM > > >> I can not find something similar in open issues. It seems that lines >> filled with spacing or multimeasure rests or give a first measure >> wider than the others, in each line: >> >> \version "2.13.8" >>

Re: Issue 451 in lilypond: Enhancement: a more flexible \parallelMusic syntax when used with \relative

Updates: Summary: Enhancement: a more flexible \parallelMusic syntax when used with \relative Owner: v.villenave Labels: Usability Comment #3 on issue 451 by v.villenave: Enhancement: a more flexible \parallelMusic syntax when used with \relative http://code.google.com/p/li

Issue 914 in lilypond: Enhancement: instrument-aware presets

Status: Accepted Owner: v.villenave Labels: Type-Enhancement Priority-Low New issue 914 by v.villenave: Enhancement: instrument-aware presets http://code.google.com/p/lilypond/issues/detail?id=914 New feature request from David: http://lists.gnu.org/archive/html/lilypond-devel/2009-11/msg00716.h

Re: Uneven empty measures

Francisco Vila wrote Sunday, November 29, 2009 8:20 PM I can not find something similar in open issues. It seems that lines filled with spacing or multimeasure rests or give a first measure wider than the others, in each line: \version "2.13.8" { \time 6/8 R2.*3 \break R2.*4 \break

Uneven empty measures

> I can not find something similar in open issues. It seems that lines filled with spacing or multimeasure rests or give a first measure wider than the others, in each line: \version "2.13.8" { \time 6/8 R2.*3 \break R2.*4 \break R2.*5 } It would be a regression as 2.12 did not show i

Re: Issue 451 in lilypond: \parallelMusic and \relative don't mix

Comment #2 on issue 451 by d...@gnu.org: \parallelMusic and \relative don't mix http://code.google.com/p/lilypond/issues/detail?id=451 The minimal examples are invalid syntax. I have no idea whether they might have been invalid syntax at the time of the bug report. The following file appe

Re: Issue 787 in lilypond: script stack order fails with 2 more notes

Updates: Status: Verified Comment #5 on issue 787 by v.villenave: script stack order fails with 2 more notes http://code.google.com/p/lilypond/issues/detail?id=787 Works perfectly now. Thanks! -- You received this message because you are listed in the owner or CC fields of this issue

Re: Issue 261 in lilypond: \partcombine prints rests (or not) depending on order of voices

Updates: Owner: v.villenave Labels: partcombine Comment #1 on issue 261 by v.villenave: \partcombine prints rests (or not) depending on order of voices http://code.google.com/p/lilypond/issues/detail?id=261 On a related note, see Issue 913. -- You received this message becaus

Re: change Pitch, strange behavior

On Sun, Nov 29, 2009 at 11:34 AM, Reinhold Kainhofer wrote: > Still it would be nice to collect such snippets for a future fix of > partcombine.Otherwise we'll have to think of all possible problesm againand > create regtets again. When the time comes, it should be as simple as http://code.google

Issue 913 in lilypond: \partcombine doesn't handle rests correctly when its arguments have different lengths

Status: Accepted Owner: v.villenave Labels: Type-Defect Priority-Low Engraving-nitpick partcombine New issue 913 by v.villenave: \partcombine doesn't handle rests correctly when its arguments have different lengths http://code.google.com/p/lilypond/issues/detail?id=913 % Obviously related to

Re: Issue 880 in lilypond: Regression: Arpeggios collide with notes when connectArpeggios is set

Updates: Summary: Regression: Arpeggios collide with notes when connectArpeggios is set Labels: -Priority-Medium Priority-Regression Comment #1 on issue 880 by v.villenave: Regression: Arpeggios collide with notes when connectArpeggios is set http://code.google.com/p/lilypond/issue

Re: span arpeggio and single notes

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

Re: Issue 638 in lilypond: auto-beam-settings do not take into account *all* durations covered by the beam

Updates: Status: Started Comment #8 on issue 638 by v.villenave: auto-beam-settings do not take into account *all* durations covered by the beam http://code.google.com/p/lilypond/issues/detail?id=638 OK, marking as Started. -- You received this message because you are listed in the o

Re: span arpeggio and single notes

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 collis