Updates:
Labels: -Patch-new Patch-review
Comment #14 on issue 1780 by pkx1...@gmail.com: Scheme format functions
with no destination parameter cause deprecation warnings in Guile V2
http://code.google.com/p/lilypond/issues/detail?id=1780
Passes make. There is one reg test that shows
Updates:
Labels: -Patch-new Patch-needs_work
Comment #7 on issue 1572 by pkx1...@gmail.com: Change chord name separator
and inversion separator, separately
http://code.google.com/p/lilypond/issues/detail?id=1572
Passes make but fails reg test:
--snip--
Processing cf/lily-2272dc04
Updates:
Labels: -Patch-new Patch-needs_work
Comment #13 on issue 1503 by pkx1...@gmail.com: Feature request: simplify
jazz chord display
http://code.google.com/p/lilypond/issues/detail?id=1503
Passes make but fails reg test comparison.
--snip--
ocessing cf/lily-2272dc04
Processing
Comment #36 on issue 1776 by pkx1...@gmail.com: Doc: NR - Polymetric
Notation \compoundMeter isn't documented
http://code.google.com/p/lilypond/issues/detail?id=1776
Neil, thanks for that.
new patch uploaded with (hopefully) corrected snippet edit as well.
Comment #6 on issue 1110 by arnowas...@gmail.com: Wrong octave of
repetition chord with \relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110
2.13.4? Are you sure? I could not make release/2.13.4-1 make compile the
above snippets...
Comment #8 on issue 1529 by philehol...@googlemail.com: filename changing
should not trigger a regtests comparison
http://code.google.com/p/lilypond/issues/detail?id=1529
Looking at the output for the 2.15.10 regtests (there's quite a bit to
scroll down...) I still see the
Status: Accepted
Owner:
Labels: Type-Ugly
New issue 1879 by philehol...@googlemail.com: Packed-spacing works
improperly with Mensural_ligature_engraver and Vaticana_ligature_engraver
http://code.google.com/p/lilypond/issues/detail?id=1879
Marek Klein reports (NB I have not checked this
Reinhold Kainhofer reinh...@kainhofer.com wrote in message
news:201109082343.26053.reinh...@kainhofer.com...
If there is bar number printed after a measure, a full measure rest will
be
much longer than if there is no bar number printed. Simple example
attached.
A bar number should not have an
Status: Accepted
Owner:
Labels: Type-Ugly
New issue 1880 by philehol...@googlemail.com: Presence of a bar number
changes whole-measure rest width significantly
http://code.google.com/p/lilypond/issues/detail?id=1880
Reported by Reinhold:
If there is bar number printed after a measure,
Updates:
Status: Verified
Comment #8 on issue 724 by philehol...@googlemail.com: Staves that begin
with an accidental should have more space before their first note.
http://code.google.com/p/lilypond/issues/detail?id=724
(No comment was entered for this change.)
Updates:
Status: Verified
Comment #6 on issue 905 by philehol...@googlemail.com: LilyPond should
accept UTF-8 BOM signatures even if preceded with other chars
http://code.google.com/p/lilypond/issues/detail?id=905
(No comment was entered for this change.)
Comment #8 on issue 1805 by philehol...@googlemail.com: Ambitus engraver
produces false warnings
http://code.google.com/p/lilypond/issues/detail?id=1805
Not verified. I still get the error message on 2.15.10.
___
bug-lilypond mailing list
Updates:
Labels: -Priority-Low -Patch-push -fixed_2_15_10 fixed_2_15_11
Comment #9 on issue 1805 by tdaniels...@googlemail.com: Ambitus engraver
produces false warnings
http://code.google.com/p/lilypond/issues/detail?id=1805
The fix didn't make it in 2.15.10. It's in 2.15.11
Updates:
Status: Started
Owner: d...@gnu.org
Labels: -Patch-needs_work Patch-review
Comment #4 on issue 1584 by d...@gnu.org: removing parser DIGIT rule
http://code.google.com/p/lilypond/issues/detail?id=1584
Rietveld URL:http://codereview.appspot.com/4311041 now carries
Comment #1 on issue 1880 by tdaniels...@googlemail.com: Presence of a bar
number changes whole-measure rest width significantly
http://code.google.com/p/lilypond/issues/detail?id=1880
Here's a simple work-around (by analogy with textLengthOn/Off):
barNumberLengthOn = {
\override
Am Saturday, 10. September 2011, 21:22:30 schrieb lilyp...@googlecode.com:
Comment #32 on issue 1776 by percival.music.ca: Doc: NR - Polymetric
Notation \compoundMeter isn't documented
http://code.google.com/p/lilypond/issues/detail?id=1776
2.14.2, and then clear out everything in
Comment #15 on issue 1780 by reinhold...@gmail.com: Scheme format functions
with no destination parameter cause deprecation warnings in Guile V2
http://code.google.com/p/lilypond/issues/detail?id=1780
That's a regression. The regtest should print out 0.19 (i.e. two decimals
after the
Updates:
Status: Fixed
Labels: -Patch-review
Comment #5 on issue 1584 by d...@gnu.org: removing parser DIGIT rule
http://code.google.com/p/lilypond/issues/detail?id=1584
Actually, I have reread the patch as diff again. It is straightforward and
simple. It passes regtests
Updates:
Labels: fixed_2_15_11
Comment #6 on issue 1584 by philehol...@googlemail.com: removing parser
DIGIT rule
http://code.google.com/p/lilypond/issues/detail?id=1584
(No comment was entered for this change.)
___
bug-lilypond mailing
Updates:
Status: Verified
Comment #4 on issue 1849 by philehol...@googlemail.com: Fix memleak:
temporary skyline objects for systems were never deleted
http://code.google.com/p/lilypond/issues/detail?id=1849
Verified as pushed on Sept 1.
Updates:
Status: Verified
Comment #4 on issue 1848 by philehol...@googlemail.com: Lilypond-book: Give
images 1mm less linewidth
http://code.google.com/p/lilypond/issues/detail?id=1848
Confirmed as geting rid of all those nasty black bars on images in
Learning :-)
Updates:
Status: Fixed
Labels: -Patch-push
Comment #14 on issue 1741 by d...@gnu.org: Tablature Bug when pitch is
higher then beh in a quarter-tone string
http://code.google.com/p/lilypond/issues/detail?id=1741
Pushed as 5f1308c20d09eb5385f746e7ee05932ae079b5a6
Note that
Updates:
Labels: -Patch-review Patch-needs_work
Comment #16 on issue 1780 by pkx1...@gmail.com: Scheme format functions
with no destination parameter cause deprecation warnings in Guile V2
http://code.google.com/p/lilypond/issues/detail?id=1780
(No comment was entered for this
Hallo,
welche zeichenkodierung benutzt ihr für Lilipond? Ich kanns nicht lesen. Mit
UTF-8 geht es nicht.
Danke
Thomas
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
More details, more concrete please!
Am 11.09.2011 22:56, schrieb Thomas:
Hallo,
welche zeichenkodierung benutzt ihr für Lilipond? Ich kanns nicht lesen. Mit
UTF-8 geht es nicht.
Danke
Thomas
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Status: Accepted
Owner:
Labels: Type-Critical
New issue 1881 by n.putt...@gmail.com: Multiple cyclic dependency errors
for Beam/Stem
http://code.google.com/p/lilypond/issues/detail?id=1881
Following commit 6465274e66a851cccd4cd32a521abc853f3e79dd, `Restores stem
length and
Comment #1 on issue 1881 by n.putt...@gmail.com: Multiple cyclic dependency
errors for Beam/Stem
http://code.google.com/p/lilypond/issues/detail?id=1881
Here's a diff from make check for autobeam-show-defaults.ly. It changes
for each test, so always shows up (and it's one of many).
Comment #3 on issue 1843 by x.sche...@gmail.com: Creates a Flag grob
http://code.google.com/p/lilypond/issues/detail?id=1843
Could you check there is a convert-ly rule for this?
And add it if needed? :-)
___
bug-lilypond mailing list
28 matches
Mail list logo
