Updates:
Labels: -Patch-new Patch-needs_work
Comment #10 on issue 1791 by pkx1...@gmail.com: footnote numbering is 'out
of order' when using multiple staves in a system
http://code.google.com/p/lilypond/issues/detail?id=1791
Mike,
No seg fault (although it does go up to 2.5+ GB of Me
On 11-11-06 03:25 PM, Colin Campbell wrote:
On 11-11-06 02:05 AM, Graham Percival wrote:
On Sat, Nov 05, 2011 at 10:29:05PM -0600, Colin Campbell wrote:
This evening, I d/l a copy of the gub source, ran bin/gupdate
--replace gub/specs/curl.py which pulled curl up to version 7.22 so
wow, I had
Comment #9 on issue 1791 by mts...@gmail.com: footnote numbering is 'out of
order' when using multiple staves in a system
http://code.google.com/p/lilypond/issues/detail?id=1791
Hey all,
Just a note that this newest patch set slows down the regtests a lot. So
it is a sketch & is not meant
Updates:
Labels: Patch-new
Comment #8 on issue 1791 by mts...@gmail.com: footnote numbering is 'out of
order' when using multiple staves in a system
http://code.google.com/p/lilypond/issues/detail?id=1791#c8
Fixes footnote automatic numbering.
http://codereview.appspot.com/4877041
Updates:
Labels: -fixed_15_17 fixed_2_15_17
Comment #5 on issue 2017 by tdaniels...@gmail.com: Patch: Correct forward
declarations (struct vs. class)
http://code.google.com/p/lilypond/issues/detail?id=2017
(No comment was entered for this change.)
___
Comment #32 on issue 11 by carl.d.s...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
They are all correct.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://list
Updates:
Labels: -Patch-countdown Patch-review
Comment #31 on issue 11 by pkx1...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Carl,
I reran the patch again on a new build but still only got that one reg test
show up.
Updates:
Labels: -Patch-new Patch-review
Comment #20 on issue 2000 by pkx1...@gmail.com: Patch: Fixes NoteColumn vs
SpanBar collisions.
http://code.google.com/p/lilypond/issues/detail?id=2000
passes make and reg test diffs are all here:
http://lilypond-stuff.1065243.n5.nabble.com/Tra
Updates:
Status: Fixed
Labels: -Patch-push fixed_15_17
Comment #4 on issue 2017 by gra...@percival-music.ca: Patch: Correct
forward declarations (struct vs. class)
http://code.google.com/p/lilypond/issues/detail?id=2017
pushed e2f8a198c6f4eafe83b8a3a7892873feef7d762e
___
Issue 2024: Patch: Let #{ ... #} pass its $ handling to environment cloning
http://code.google.com/p/lilypond/issues/detail?id=2024
This issue is now blocking issue 2033.
See http://code.google.com/p/lilypond/issues/detail?id=2033
--
You received this message because you are listed in the owner
Updates:
Owner: d...@gnu.org
Blockedon: 2024
Comment #1 on issue 2033 by d...@gnu.org: Patch: This removes ly:export for
real and separates read/eval for Scheme expressions.
http://code.google.com/p/lilypond/issues/detail?id=2033
(No comment was entered for this change.)
___
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2033 by d...@gnu.org: Patch: This removes ly:export for real and
separates read/eval for Scheme expressions.
http://code.google.com/p/lilypond/issues/detail?id=2033
This removes ly:export for real and separates read/eval for
Comment #1 on issue 1861 by michaeld...@earthlink.net: DynamicText attached
to spacer rest not correctly aligned
http://code.google.com/p/lilypond/issues/detail?id=1861
I wonder if the issue revolves around centering dynamics on grobs with
width (as in the former part of the example) and ce
Updates:
Labels: Patch-new
Comment #19 on issue 2000 by mts...@gmail.com: Patch: Fixes NoteColumn vs
SpanBar collisions.
http://code.google.com/p/lilypond/issues/detail?id=2000#c19
Fixes NoteColumn vs SpanBar collisions.
http://codereview.appspot.com/5323062
___
Comment #16 on issue 1873 by pkx1...@gmail.com: Added glyphs for Kievan
Notation
http://code.google.com/p/lilypond/issues/detail?id=1873
On 2011/10/18 17:46:23, Bertrand Bordage wrote:
LGTM. Two tiny changes and it'll be ready to push.
That was three weeks ago. Is this done? I still see t
Updates:
Owner: d...@gnu.org
Blockedon: 2024
Comment #1 on issue 2032 by d...@gnu.org: Patch: Fold set-time-signature
into \time
http://code.google.com/p/lilypond/issues/detail?id=2032
(No comment was entered for this change.)
___
Issue 2024: Patch: Let #{ ... #} pass its $ handling to environment cloning
http://code.google.com/p/lilypond/issues/detail?id=2024
This issue is now blocking issue 2032.
See http://code.google.com/p/lilypond/issues/detail?id=2032
--
You received this message because you are listed in the owner
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2032 by d...@gnu.org: Patch: Fold set-time-signature into \time
http://code.google.com/p/lilypond/issues/detail?id=2032
Fold set-time-signature into \time
This removes the strange-syntax set-time-signature and folds its
functi
18 matches
Mail list logo
