Re: Issue 2096 in lilypond: Patch: Implements cross-staff stem avoidance for dynamics.

2011-12-18 Thread lilypond
Comment #9 on issue 2096 by mts...@gmail.com: Patch: Implements cross-staff stem avoidance for dynamics. http://code.google.com/p/lilypond/issues/detail?id=2096 Pushed as 3bcfd69d91f52f70598f73719fbed7aa6eea8ad3. Cheers, MS ___ bug-lilypond maili

Re: Issue 1216 in lilypond: DynamicTextSpanners should end like hairpins

2011-12-18 Thread lilypond
Updates: Labels: -Patch-countdown Patch-push Comment #11 on issue 1216 by colinpkc...@gmail.com: DynamicTextSpanners should end like hairpins http://code.google.com/p/lilypond/issues/detail?id=1216 Counted down to 20111217, please push ___

Re: Issue 2103 in lilypond: Patch: Output a newline by default at the end of progress messages.

2011-12-18 Thread lilypond
Updates: Labels: -Patch-countdown Patch-push Comment #10 on issue 2103 by colinpkc...@gmail.com: Patch: Output a newline by default at the end of progress messages. http://code.google.com/p/lilypond/issues/detail?id=2103 Counted down to 20111217, please push

Re: Issue 2105 in lilypond: Patch: Remove warning and .aux file left over by lilypond-book.

2011-12-18 Thread lilypond
Updates: Labels: -Patch-countdown Patch-push Comment #6 on issue 2105 by colinpkc...@gmail.com: Patch: Remove warning and .aux file left over by lilypond-book. http://code.google.com/p/lilypond/issues/detail?id=2105 Counted down to 20111217, please push _

Re: Issue 2107 in lilypond: new patch for lilypond-book on windows

2011-12-18 Thread lilypond
Updates: Labels: -Patch-countdown Patch-push Comment #4 on issue 2107 by colinpkc...@gmail.com: new patch for lilypond-book on windows http://code.google.com/p/lilypond/issues/detail?id=2107 Counted down to 20111217, please push ___ bug-li

Re: Issue 2108 in lilypond: Patch: Implements avoidance of cross-staff-stem vs. articulation collisions.

2011-12-18 Thread lilypond
Updates: Labels: -Patch-countdown Patch-push Comment #4 on issue 2108 by colinpkc...@gmail.com: Patch: Implements avoidance of cross-staff-stem vs. articulation collisions. http://code.google.com/p/lilypond/issues/detail?id=2108 Counted down to 20111217, please push

Re: Issue 2096 in lilypond: Patch: Implements cross-staff stem avoidance for dynamics.

2011-12-18 Thread lilypond
Comment #7 on issue 2096 by colinpkc...@gmail.com: Patch: Implements cross-staff stem avoidance for dynamics. http://code.google.com/p/lilypond/issues/detail?id=2096 Mike, would you be willing to push this, as it has been counted down and set to "push" a couple of days ago? _

Re: Issue 1377 in lilypond: Enhancement: make the last-page spacing more consistent and less tight

2011-12-18 Thread lilypond
Comment #13 on issue 1377 by colinpkc...@gmail.com: Enhancement: make the last-page spacing more consistent and less tight http://code.google.com/p/lilypond/issues/detail?id=1377 Keith, would you be willing to push this, as it has had a countdown and been set to "push" a couple of days ago?

Re: Issue 2126 in lilypond: Patch: CG: Typos in "Programming work" and "Regression tests" sections.

2011-12-18 Thread lilypond
Updates: Labels: Patch-review Comment #1 on issue 2126 by lilypond...@gmail.com: Patch: CG: Typos in "Programming work" and "Regression tests" sections. http://code.google.com/p/lilypond/issues/detail?id=2126#c1 Patchy the autobot says: LGTM.

Re: Issue 2027 in lilypond: make website doesn't have dependencies

2011-12-18 Thread lilypond
Updates: Labels: Patch-review Comment #6 on issue 2027 by lilypond...@gmail.com: make website doesn't have dependencies http://code.google.com/p/lilypond/issues/detail?id=2027#c6 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list

Re: Issue 1908 in lilypond: Causes lily to fail during regtests if binary is unoptimized

2011-12-18 Thread lilypond
Comment #2 on issue 1908 by julien.r...@gmail.com: Causes lily to fail during regtests if binary is unoptimized http://code.google.com/p/lilypond/issues/detail?id=1908 Is this invalid then? ___ bug-lilypond mailing list bug-lilypond@gnu.org https:

Re: Issue 2090 in lilypond: Add documentation for command line quoting on Windows

2011-12-18 Thread lilypond
Comment #4 on issue 2090 by julien.r...@gmail.com: Add documentation for command line quoting on Windows http://code.google.com/p/lilypond/issues/detail?id=2090 Re: please verify under Linux! I tried on a few shells here and yes you can write -dpoint-and-click=#f as well (without spaces!).

Re: Issue 1726 in lilypond: python versions might not be updating

2011-12-18 Thread lilypond
Updates: Labels: Patch-new Comment #3 on issue 1726 by julien.r...@gmail.com: python versions might not be updating http://code.google.com/p/lilypond/issues/detail?id=1726#c3 Build: Version dependency for python modules (issue 1726). http://codereview.appspot.com/5490067 __

Re: Issue 2122 in lilypond: Regression in chord-name-exceptions.ly - badly spaced chord names

2011-12-18 Thread lilypond
Updates: Owner: mts...@gmail.com Comment #4 on issue 2122 by carl.d.s...@gmail.com: Regression in chord-name-exceptions.ly - badly spaced chord names http://code.google.com/p/lilypond/issues/detail?id=2122 (No comment was entered for this change.) ___

Re: Issue 2027 in lilypond: make website doesn't have dependencies

2011-12-18 Thread lilypond
Updates: Labels: Patch-new Comment #5 on issue 2027 by julien.r...@gmail.com: make website doesn't have dependencies http://code.google.com/p/lilypond/issues/detail?id=2027#c5 Build: Dependencies for make website (issue 2027). http://codereview.appspot.com/5493074 _

Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module

2011-12-18 Thread lilypond
Updates: Status: Started Labels: Patch-needs_work Comment #10 on issue 2026 by ianhuli...@gmail.com: Make markup utility definitions available via new (scm markup-utility-defs) scheme module http://code.google.com/p/lilypond/issues/detail?id=2026 Problems identified with docs

Re: Issue 586 in lilypond: Cross-staff slur causes a weird output

2011-12-18 Thread lilypond
Comment #9 on issue 586 by paconet@gmail.com: Cross-staff slur causes a weird output http://code.google.com/p/lilypond/issues/detail?id=586 No odd messajes with latest master, stems are OK and output is as example image, bad slur and bad tuplet bracket. __

Issue 2126 in lilypond: Patch: CG: Typos in "Programming work" and "Regression tests" sections.

2011-12-18 Thread lilypond
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2126 by julien.r...@gmail.com: Patch: CG: Typos in "Programming work" and "Regression tests" sections. http://code.google.com/p/lilypond/issues/detail?id=2126 CG: Typos in "Programming work" and "Regression tests" sections

Re: Issue 2125 in lilypond: Patch: Build: Don't rebuild everything each time unless necessary.

2011-12-18 Thread lilypond
Updates: Labels: Patch-review Comment #2 on issue 2125 by lilypond...@gmail.com: Patch: Build: Don't rebuild everything each time unless necessary. http://code.google.com/p/lilypond/issues/detail?id=2125#c2 Patchy the autobot says: LGTM. _

Re: Issue 2124 in lilypond: Patch: Regtest script improvements:

2011-12-18 Thread lilypond
Updates: Labels: Patch-review Comment #3 on issue 2124 by lilypond...@gmail.com: Patch: Regtest script improvements: http://code.google.com/p/lilypond/issues/detail?id=2124#c3 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bu

Re: Issue 2122 in lilypond: Regression in chord-name-exceptions.ly - badly spaced chord names

2011-12-18 Thread lilypond
Updates: Labels: Patch-review Comment #3 on issue 2122 by lilypond...@gmail.com: Regression in chord-name-exceptions.ly - badly spaced chord names http://code.google.com/p/lilypond/issues/detail?id=2122#c3 Patchy the autobot says: LGTM. __

Re: Issue 2123 in lilypond: Patch: Gets cross-staff collisions right for beams.

2011-12-18 Thread lilypond
Updates: Labels: Patch-review Comment #1 on issue 2123 by lilypond...@gmail.com: Patch: Gets cross-staff collisions right for beams. http://code.google.com/p/lilypond/issues/detail?id=2123#c1 Patchy the autobot says: LGTM. ___ bug-lilypond

Re: Issue 2113 in lilypond: Beamlet points the wrong way when tuplet sixteenths are beamed with eighths

2011-12-18 Thread lilypond
Updates: Labels: Patch-review Comment #7 on issue 2113 by lilypond...@gmail.com: Beamlet points the wrong way when tuplet sixteenths are beamed with eighths http://code.google.com/p/lilypond/issues/detail?id=2113#c7 Patchy the autobot says: LGTM.

Re: Issue 2122 in lilypond: Regression in chord-name-exceptions.ly - badly spaced chord names

2011-12-18 Thread lilypond
Updates: Labels: Patch-new Comment #2 on issue 2122 by mts...@gmail.com: Regression in chord-name-exceptions.ly - badly spaced chord names http://code.google.com/p/lilypond/issues/detail?id=2122#c2 Adds extra-spacing-width to ChordName. http://codereview.appspot.com/5490063 ___

Re: Issue 2122 in lilypond: Regression in chord-name-exceptions.ly - badly spaced chord names

2011-12-18 Thread lilypond
Comment #1 on issue 2122 by mts...@gmail.com: Regression in chord-name-exceptions.ly - badly spaced chord names http://code.google.com/p/lilypond/issues/detail?id=2122 It's worth it to add chord-names-bass.ly and chords-funky-ignatzek.ly into the mix. They didn't change between versions, b

Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved.

2011-12-18 Thread lilypond
Updates: Blockedon: 2124 Comment #13 on issue 2104 by julien.r...@gmail.com: Patch: Fix .dep file from lilypond-book when include paths are involved. http://code.google.com/p/lilypond/issues/detail?id=2104 (No comment was entered for this change.) ___

Re: Issue 2124 in lilypond: Patch: Regtest script improvements:

2011-12-18 Thread lilypond
Issue 2124: Patch: Regtest script improvements: http://code.google.com/p/lilypond/issues/detail?id=2124 This issue is now blocking issue 2104. See http://code.google.com/p/lilypond/issues/detail?id=2104 -- You received this message because you are listed in the owner or CC fields of this issue,

Re: Issue 2124 in lilypond: Patch: Regtest script improvements:

2011-12-18 Thread lilypond
Updates: Status: Started Owner: julien.r...@gmail.com Comment #1 on issue 2124 by julien.r...@gmail.com: Patch: Regtest script improvements: http://code.google.com/p/lilypond/issues/detail?id=2124 (No comment was entered for this change.)

Re: Issue 2125 in lilypond: Patch: Build: Don't rebuild everything each time unless necessary.

2011-12-18 Thread lilypond
Updates: Status: Started Owner: julien.r...@gmail.com Comment #1 on issue 2125 by julien.r...@gmail.com: Patch: Build: Don't rebuild everything each time unless necessary. http://code.google.com/p/lilypond/issues/detail?id=2125 (No comment was entered for this change.) _

Issue 2125 in lilypond: Patch: Build: Don't rebuild everything each time unless necessary.

2011-12-18 Thread lilypond
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2125 by julien.r...@gmail.com: Patch: Build: Don't rebuild everything each time unless necessary. http://code.google.com/p/lilypond/issues/detail?id=2125 Build: Don't rebuild everything each time unless necessary. - Fix a t

Issue 2124 in lilypond: Patch: Regtest script improvements:

2011-12-18 Thread lilypond
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2124 by julien.r...@gmail.com: Patch: Regtest script improvements: http://code.google.com/p/lilypond/issues/detail?id=2124 Regtest script improvements: - Allow to customize the length of shortened strings. - When filtering thr

Re: Issue 2056 in lilypond: Typos in German translation

2011-12-18 Thread lilypond
Comment #1 on issue 2056 by philehol...@gmail.com: Typos in German translation http://code.google.com/p/lilypond/issues/detail?id=2056 Further typos: Typo in Documentation http://lilypond.org/doc/v2.14/Documentation/learning/engravers-explained Staff_symbol_engraver *Ersetllt* die (standar

Issue 2123 in lilypond: Patch: Gets cross-staff collisions right for beams.

2011-12-18 Thread lilypond
Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2123 by mts...@gmail.com: Patch: Gets cross-staff collisions right for beams. http://code.google.com/p/lilypond/issues/detail?id=2123 Gets cross-staff collisions right for beams. http://codereview.appspot.com/5489076

Re: Typo in Documentation (2)

2011-12-18 Thread Phil Holmes
"hgz" wrote in message news:loom.20111218t155621-...@post.gmane.org... Typo in Documentation (2) http://lilypond.org/doc/v2.14/Documentation/learning/modifying-context-properties in "Kontexteigenschaften mit \with setzen" [...] die für die gesamte Partitur erhalten *bleichen* soll. MfG hgz

Re: Typo in Documentation

2011-12-18 Thread Phil Holmes
"hgz" wrote in message news:loom.20111218t153505-...@post.gmane.org... Typo in Documentation http://lilypond.org/doc/v2.14/Documentation/learning/engravers-explained Staff_symbol_engraver *Ersetllt* die (standardmäßig) fünf Notenlinien des Systems. MfG hgz Thanks. Added to http://code.goo

Issue 2122 in lilypond: Regression in chord-name-exceptions.ly - badly spaced chord names

2011-12-18 Thread lilypond
Status: Accepted Owner: Labels: Regression Type-Ugly New issue 2122 by philehol...@gmail.com: Regression in chord-name-exceptions.ly - badly spaced chord names http://code.google.com/p/lilypond/issues/detail?id=2122 In version 2.15.22, chord names now overlap bar lines, leading to text t

Typo in Documentation (2)

2011-12-18 Thread hgz
Typo in Documentation (2) http://lilypond.org/doc/v2.14/Documentation/learning/modifying-context-properties in "Kontexteigenschaften mit \with setzen" [...] die für die gesamte Partitur erhalten *bleichen* soll. MfG hgz ___ bug-lilypond mailing lis

Typo in Documentation

2011-12-18 Thread hgz
Typo in Documentation http://lilypond.org/doc/v2.14/Documentation/learning/engravers-explained Staff_symbol_engraver *Ersetllt* die (standardmäßig) fünf Notenlinien des Systems. MfG hgz ___ bug-lilypond mailing list bug-lilypond@gnu.org https://li

Re: Issue 2093 in lilypond: Doc: alternativeNumberingStyle (fix issue 2059) should be documented

2011-12-18 Thread lilypond
Comment #2 on issue 2093 by pkx1...@gmail.com: Doc: alternativeNumberingStyle (fix issue 2059) should be documented http://code.google.com/p/lilypond/issues/detail?id=2093 Issue 2121 has been merged into this issue. ___ bug-lilypond mailing list b

Re: Issue 2121 in lilypond: Doc: alternativeNumberingStyle (fix issue 2059) should be documented

2011-12-18 Thread lilypond
Updates: Status: Duplicate Mergedinto: 2093 Comment #2 on issue 2121 by pkx1...@gmail.com: Doc: alternativeNumberingStyle (fix issue 2059) should be documented http://code.google.com/p/lilypond/issues/detail?id=2121 (No comment was entered for this change.) _

Re: Issue 2121 in lilypond: Doc: alternativeNumberingStyle (fix issue 2059) should be documented

2011-12-18 Thread lilypond
Comment #1 on issue 2121 by x.sche...@gmail.com: Doc: alternativeNumberingStyle (fix issue 2059) should be documented http://code.google.com/p/lilypond/issues/detail?id=2121 Hi Phil, Colin already added it as issue 2093. This one is then a duplicate. Thanks! __

Re: Issue 2103 in lilypond: Patch: Output a newline by default at the end of progress messages.

2011-12-18 Thread lilypond
Updates: Status: Started Owner: julien.r...@gmail.com Comment #9 on issue 2103 by pkx1...@gmail.com: Patch: Output a newline by default at the end of progress messages. http://code.google.com/p/lilypond/issues/detail?id=2103 (No comment was entered for this change.)

Re: Issue 2109 in lilypond: do not tinker with the position of a pitched rest

2011-12-18 Thread lilypond
Updates: Status: Started Comment #2 on issue 2109 by pkx1...@gmail.com: do not tinker with the position of a pitched rest http://code.google.com/p/lilypond/issues/detail?id=2109 (No comment was entered for this change.) ___ bug-lilypond ma

Re: Issue 2096 in lilypond: Patch: Implements cross-staff stem avoidance for dynamics.

2011-12-18 Thread lilypond
Updates: Owner: mts...@gmail.com Cc: -mts...@gmail.com Comment #6 on issue 2096 by pkx1...@gmail.com: Patch: Implements cross-staff stem avoidance for dynamics. http://code.google.com/p/lilypond/issues/detail?id=2096 (No comment was entered for this change.)

Re: Issue 2096 in lilypond: Patch: Implements cross-staff stem avoidance for dynamics.

2011-12-18 Thread lilypond
Updates: Status: Started Cc: mts...@gmail.com Comment #5 on issue 2096 by pkx1...@gmail.com: Patch: Implements cross-staff stem avoidance for dynamics. http://code.google.com/p/lilypond/issues/detail?id=2096 (No comment was entered for this change.) _

Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient

2011-12-18 Thread lilypond
Updates: Status: Started Owner: gra...@percival-music.ca Comment #10 on issue 2100 by pkx1...@gmail.com: Patch: CG: explanation of branches for the impatient http://code.google.com/p/lilypond/issues/detail?id=2100 (No comment was entered for this change.) ___

Re: Issue 2105 in lilypond: Patch: Remove warning and .aux file left over by lilypond-book.

2011-12-18 Thread lilypond
Updates: Status: Started Owner: julien.r...@gmail.com Comment #5 on issue 2105 by pkx1...@gmail.com: Patch: Remove warning and .aux file left over by lilypond-book. http://code.google.com/p/lilypond/issues/detail?id=2105 (No comment was entered for this change.)

Re: Issue 2108 in lilypond: Patch: Implements avoidance of cross-staff-stem vs. articulation collisions.

2011-12-18 Thread lilypond
Updates: Status: Started Owner: mts...@gmail.com Comment #3 on issue 2108 by pkx1...@gmail.com: Patch: Implements avoidance of cross-staff-stem vs. articulation collisions. http://code.google.com/p/lilypond/issues/detail?id=2108 (No comment was entered for this change.)

Re: Issue 2116 in lilypond: Patch: Shows Flags in tabFullNotation

2011-12-18 Thread lilypond
Updates: Status: Started Owner: mts...@gmail.com Comment #2 on issue 2116 by pkx1...@gmail.com: Patch: Shows Flags in tabFullNotation http://code.google.com/p/lilypond/issues/detail?id=2116 (No comment was entered for this change.) ___

Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved.

2011-12-18 Thread lilypond
Updates: Status: Started Owner: julien.r...@gmail.com Comment #12 on issue 2104 by pkx1...@gmail.com: Patch: Fix .dep file from lilypond-book when include paths are involved. http://code.google.com/p/lilypond/issues/detail?id=2104 (No comment was entered for this change.) __

Re: Issue 2093 in lilypond: Doc: alternativeNumberingStyle (fix issue 2059) should be documented

2011-12-18 Thread lilypond
Comment #1 on issue 2093 by pkx1...@gmail.com: Doc: alternativeNumberingStyle (fix issue 2059) should be documented http://code.google.com/p/lilypond/issues/detail?id=2093 Can someone enlighten me what \set Score.alternativeNumberingStyle = #'number does? I've tried the two options on som

Re: Issue 2118 in lilypond: Overriding stencil of StringNumber leads to "programming error"messages

2011-12-18 Thread lilypond
Updates: Status: Duplicate Cc: adam.spi...@gmail.com Mergedinto: 2085 Comment #1 on issue 2118 by carl.d.s...@gmail.com: Overriding stencil of StringNumber leads to "programming error"messages http://code.google.com/p/lilypond/issues/detail?id=2118 Duplicate of 2085, w

Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to "programming error" messages

2011-12-18 Thread lilypond
Updates: Cc: adam.spi...@gmail.com Comment #12 on issue 2085 by carl.d.s...@gmail.com: Overriding stencil of StringNumber leads to "programming error" messages http://code.google.com/p/lilypond/issues/detail?id=2085 Issue 2118 has been merged into this issue. ___

Re: Issue 2120 in lilypond: skipTypesetting a tie is postponed to the not skipped part starting with 2 notes of same pitch

2011-12-18 Thread lilypond
Comment #1 on issue 2120 by elu...@gmail.com: skipTypesetting a tie is postponed to the not skipped part starting with 2 notes of same pitch http://code.google.com/p/lilypond/issues/detail?id=2120 s. also this discussion: http://old.nabble.com/skipTypesetting-oddities-td32988646.html ___

Issue 2121 in lilypond: Doc: alternativeNumberingStyle (fix issue 2059) should be documented

2011-12-18 Thread lilypond
Status: Accepted Owner: Labels: Type-Documentation New issue 2121 by philehol...@gmail.com: Doc: alternativeNumberingStyle (fix issue 2059) should be documented http://code.google.com/p/lilypond/issues/detail?id=2121 From Xavier: The use of this \set Score.alternativeNumberingStyle =

Re: alternativeNumberingStyle (fix issue 2059) should be documented

2011-12-18 Thread Phil Holmes
"Xavier Scheuer" wrote in message news:cadgqhrc+9g5+qaeo+8nxysbm4drdi-pwaahox9io2y74np5...@mail.gmail.com... On 7 December 2011 23:44, Carl Sorensen wrote: This should become a new issue, type Documentation. Thanks, The use of this \set Score.alternativeNumberingStyle = #'number or \s

Issue 2120 in lilypond: skipTypesetting a tie is postponed to the not skipped part starting with 2 notes of same pitch

2011-12-18 Thread lilypond
Status: New Owner: Labels: Type-Defect New issue 2120 by elu...@gmail.com: skipTypesetting a tie is postponed to the not skipped part starting with 2 notes of same pitch http://code.google.com/p/lilypond/issues/detail?id=2120 when a tie occurs in the skipped typesetting part the first no

Re: installer lilypond

2011-12-18 Thread Phil Holmes
"alice" wrote in message news:loom.20111202t120438-...@post.gmane.org... installer lilypond Not a bug report. -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Overriding stencil of StringNumber leads to "programming error"messages

2011-12-18 Thread Phil Holmes
"David Kastrup" wrote in message news:87borkir7a@fencepost.gnu.org... Hi, the awful spacing of input/regression/tablature-harmonic-functions.ly let me to investigate, and it is apparently due to StringNumber being set to transparent, meaning that it still occupies space. I tried now to do

Issue 2119 in lilypond: script-accidental avoidance fails for articulations

2011-12-18 Thread lilypond
Status: Accepted Owner: Labels: Type-Ugly New issue 2119 by philehol...@gmail.com: script-accidental avoidance fails for articulations http://code.google.com/p/lilypond/issues/detail?id=2119 Reported by David Kastrup: See the output of this augmented version of script-accidental-collisi

Re: script-accidental avoidance fails for articulations

2011-12-18 Thread Phil Holmes
"David Kastrup" wrote in message news:87fwgwitdb@fencepost.gnu.org... See the output of this augmented version of script-accidental-collision.ly: in the second half the collision avoidance does not work.

Issue 2118 in lilypond: Overriding stencil of StringNumber leads to "programming error"messages

2011-12-18 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect New issue 2118 by philehol...@gmail.com: Overriding stencil of StringNumber leads to "programming error"messages http://code.google.com/p/lilypond/issues/detail?id=2118 David Kastrup reports: the awful spacing of input/regression/tablature-har

Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default.

2011-12-18 Thread lilypond
Comment #16 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord around rhythmic events by default. http://code.google.com/p/lilypond/issues/detail?id=2070 Again, concerning comment #14 and compatibility. I have tried looking in the engravers concerning how to make things behave as

Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to "programming error" messages

2011-12-18 Thread lilypond
Comment #11 on issue 2085 by d...@gnu.org: Overriding stencil of StringNumber leads to "programming error" messages http://code.google.com/p/lilypond/issues/detail?id=2085 There are a number of cases in the manuals where stencils are just cleared out with ##f. That's reasonably straightfor