Updates:
Status: Verified
Comment #28 on issue 1555 by philehol...@googlemail.com: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
(No comment was entered for this change.)
___
bug-lily
Updates:
Labels: -fixed_2_13_61 fixed_2_13_62
Comment #27 on issue 1555 by k-ohara5...@oco.net: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
The 'fixed' label on this issue was off by one; the commits happened after
2.13.61 wa
Comment #26 on issue 1555 by colinpkc...@gmail.com: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
@Carl: I can't seem to verify this with 2.13.61 downloaded today from the
website. I still get the multiple warnings as in the original
Updates:
Labels: -Type-Collision -backport Type-Defect fixed_2_13_61
Comment #25 on issue 1555 by carl.d.s...@gmail.com: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
Backported with commit 1d63a3985005a45af468e5c9656de3d17fbb4ee
Updates:
Status: Fixed
Comment #24 on issue 1555 by colinpkc...@gmail.com: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
Unverified in 2.13.61
___
bug-lilypond mailing list
bug-lilypo
Updates:
Status: Verified
Comment #23 on issue 1555 by colinpkc...@gmail.com: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
Verified 2.15.0 only one warning is produced.
___
bug-lilyp
Updates:
Labels: backport
Comment #22 on issue 1555 by k-ohara5...@oco.net: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
Although this issue became non-critical, the repeated warnings were so
annoying and the patch is so safe
Updates:
Status: Fixed
Labels: -Patch-review fixed_2_15_0
Comment #21 on issue 1555 by k-ohara5...@oco.net: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
Patch pushed in commit 6ca4748f reduces the warnings to just one.
Updates:
Labels: -Patch-new Patch-review
Comment #20 on issue 1555 by colinpkc...@gmail.com: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
Clean compile and regtests with 2.13.61
___
Updates:
Labels: -Patch-needs_work Patch-new
Comment #19 on issue 1555 by k-ohara5...@oco.net: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
Simplified patch up at http://codereview.appspot.com/4278058/
Updates:
Labels: -Patch-new Patch-needs_work
Comment #18 on issue 1555 by colinpkc...@gmail.com: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
Applying the patch gave an error, which I posted on reitveld.
__
Updates:
Labels: Patch-new
Comment #17 on issue 1555 by percival.music.ca: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
(No comment was entered for this change.)
___
bug-lilypond mai
Comment #16 on issue 1555 by k-ohara5...@oco.net: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
The existing warning makes no sense at all to me.
The warning should indicate
that the problem is has to do with vertical spacing
LilyPo
Updates:
Labels: -Type-Defect -Priority-Critical Type-Collision Priority-Medium
Comment #15 on issue 1555 by percival.music.ca: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
ok, downgrading priority.
___
Comment #14 on issue 1555 by carl.d.s...@gmail.com: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
I think there is a very good reason why #'staff-affinity = ##f is not the
default. Lyrics are normally associated with a Staff. ChordNa
Comment #13 on issue 1555 by percival.music.ca: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
I'm confused, so could somebody clarify:
1. if
\new Lyrics \with { \override VerticalAxisGroup #'staff-affinity = ##f }
is required to get g
Comment #12 on issue 1555 by carl.d.s...@gmail.com: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
Perhaps we could minimize confusion by changing the terminology
from "staff" and "nonstaff" to fixed and loose (loose, of course, is
re
Comment #11 on issue 1555 by carl.d.s...@gmail.com: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
Quoting from Comment 7:
Through some mistake of copy and paste the Lyric lines have affinities
CENTER, UP, DOWN.
Lilypond and I are bot
Comment #10 on issue 1555 by k-ohara5...@oco.net: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
C8> Returning to the original issue. the problem is...
True. We should have linked the original thread, including Carl's mention
of the F
Comment #9 on issue 1555 by k-ohara5...@oco.net: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
C8> Returning to the original issue. the problem is...
True. We should have linked the original thread, including Carl's mention
of the Fr
Comment #8 on issue 1555 by tdaniels...@googlemail.com: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
Returning to the original issue, the problem is that the first of the two
scores
has no staff-like context. Setting the Lyrics conte
Comment #7 on issue 1555 by k-ohara5...@oco.net: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
Lilypond needs a better message here, to let users know the ordering of
non-staff lines is not consistent with their vertical spacing settin
Comment #6 on issue 1555 by philehol...@googlemail.com: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
This is leaping out at me as another issue that requires a documentation
solution. I don't really understand the contexts and how 2.1
Comment #5 on issue 1555 by tdaniels...@googlemail.com: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
I agree with Carl. The general message might not be perfect but I don't
think Keith's more specific one is better.
__
Comment #4 on issue 1555 by carl.d.s...@gmail.com: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
The warning message Keith proposes may be clearer in this instance, but I
think the general one is actually better.
Suppose I have three
Comment #3 on issue 1555 by philehol...@googlemail.com: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
GP said: "1) some warnings are printed. I don't consider this a Critical
issue." I think it can be, depending on the number of warn
Comment #2 on issue 1555 by percival.music.ca: Multiple warnings concerning
staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
There's two separate issues here.
1) some warnings are printed. I don't consider this a Critical issue.
2) there's a collision. I *do* conside
Comment #1 on issue 1555 by k-ohara5...@oco.net: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
If we want to keep the new vertical-spacing concept -- spacing staves
first, and then placing non-staffs in between -- then we need these
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical Regression
New issue 1555 by philehol...@googlemail.com: Multiple warnings concerning
staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
Reported by Marc Hohl
In 2.12.3, the code below compiles with no p
29 matches
Mail list logo
