Archives are refreshed every 30 minutes - for details, please visit the main index.
You can also download the archives in mbox format.

bug-lilypond (date)

[Thread Index][Top][All Lists]

Advanced

[Prev Period]

Last Modified: Sat Dec 31 2011 20:47:23 -0500 Messages in reverse chronological order

[Next Period]

---

• December 31, 2011
  • Re: Segfault 2.15.23 Span_bar_stub_engraver, address@hidden, 20:47
  • Re: Issue 2163 in lilypond: Web: Added 'Ripple' to easier-editing section, lilypond, 18:59
  • Issue 2163 in lilypond: Patch: Web: Added 'Ripple' to easier-editing section, lilypond, 18:55
  • Re: Issue 1325 in lilypond: Volta bracket going over to next line, lilypond, 18:39
  • Re: Issue 1566 in lilypond: Beam properties won't be changed after the start of the beam, lilypond, 18:35
  • Issue 2162 in lilypond: Patch: Doc: NR added @knownissue for beam properties, lilypond, 18:31
  • Re: Issue 2136 in lilypond: Patch: Doc: Usage --include option layout consistency, lilypond, 18:09
  • Re: Issue 2093 in lilypond: Doc: NR alternativeNumberingStyle (fix issue 2059) needs to be documented, lilypond, 17:58
  • Segfault 2.15.23 Span_bar_stub_engraver, Jay Anderson, 16:57
  • Re: Issue 2153 in lilypond: piano pedal bracket should stop at requested moment, lilypond, 16:15
  • Re: Issue 1964 in lilypond: lilydev 2.0, lilypond, 16:11
  • Re: Issue 2153 in lilypond: piano pedal bracket should stop at requested moment, lilypond, 16:07
  • Re: Issue 2158 in lilypond: Patch: Sketch of not remaking html files, lilypond, 16:03
  • Re: Issue 2159 in lilypond: Patch: lexer.ll: Warn about non-UTF-8 characters, lilypond, 15:59
  • Re: Issue 1802 in lilypond: system-system-spacing in lilypond-book-file within a LaTeX file, lilypond, 15:55
  • Re: Issue 2136 in lilypond: Patch: Doc: Usage --include option layout consistency, lilypond, 15:51
  • Issue 2161 in lilypond: Nonfastforwarding push to staging, lilypond, 15:47
  • Re: Issue 2027 in lilypond: make website doesn't have dependencies, lilypond, 14:24
  • Issue 2160 in lilypond: document LILYPOND_WEB_MEDIA_GIT, lilypond, 14:20
  • Re: Issue 2156 in lilypond: lost commits, lilypond, 13:48
  • Re: Issue 1826 in lilypond: Guile 2.0 compat: `conditional-circle-markup' definition needs to be relocated, Ian Hulin, 13:14
  • Re: Issue 2156 in lilypond: lost commits, lilypond, 12:35
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond, lilypond, 12:09
  • Re: Issue 2156 in lilypond: lost commits, lilypond, 11:50
  • Re: Issue 2131 in lilypond: Patch: Tie LilyPond, lexer and parser together more type-safely., lilypond, 11:46
  • Re: Issue 2122 in lilypond: Regression in chord-name-exceptions.ly - badly spaced chord names, lilypond, 11:42
  • Re: Issue 2105 in lilypond: Patch: Remove warning and .aux file left over by lilypond-book., lilypond, 11:38
  • Re: Issue 2103 in lilypond: Patch: Output a newline by default at the end of progress messages., lilypond, 11:34
  • Re: Issue 2090 in lilypond: Add documentation for command line quoting on Windows, lilypond, 11:30
  • Re: Issue 2084 in lilypond: script-accidental avoidance fails for articulations, lilypond, 11:26
  • Re: Issue 2156 in lilypond: lost commits, David Kastrup, 11:24
  • Re: Issue 2059 in lilypond: Bar numbering of alternatives, lilypond, 11:22
  • Re: Issue 2156 in lilypond: lost commits, Phil Holmes, 11:19
  • Re: Issue 2027 in lilypond: make website doesn't have dependencies, lilypond, 11:18
  • Issue 2159 in lilypond: Patch: lexer.ll: Warn about non-UTF-8 characters, lilypond, 11:14
  • Re: Issue 2137 in lilypond: Patch: Doc: NR improve 'visibility' of 'q' operation, lilypond, 11:10
  • Re: letters like é, David Kastrup, 11:09
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 11:06
  • Re: Issue 2158 in lilypond: Patch: Sketch of not remaking html files, lilypond, 11:02
  • Issue 2158 in lilypond: Patch: Sketch of not remaking html files, lilypond, 10:58
  • Re: Issue 2020 in lilypond: Patch: avoid cryptic StopIteration failure from make when 'make check' is run before 'make test-baseline', lilypond, 10:54
  • Re: Issue 1947 in lilypond: Stem Tremoli for double-stemmed notes are too short on the right side., lilypond, 10:50
  • Re: Issue 1927 in lilypond: 2.15.2 doesn't build anymore on Mageia, lilypond, 10:46
  • Re: Issue 1861 in lilypond: DynamicText attached to spacer rest not correctly aligned, lilypond, 10:42
  • Re: Issue 1835 in lilypond: no learing manual pdf in dutch, lilypond, 10:38
  • Re: Issue 1826 in lilypond: Guile 2.0 compat: `conditional-circle-markup' definition needs to be relocated, lilypond, 10:34
  • Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly, lilypond, 10:30
  • Re: Issue 1377 in lilypond: Enhancement: make the last-page spacing more consistent and less tight, lilypond, 10:26
  • Re: Issue 1361 in lilypond: Collision: TupletNumber and Script, lilypond, 10:22
  • Re: Issue 2156 in lilypond: lost commits, James, 10:21
  • Re: Issue 1267 in lilypond: Documentation for 'ignore-collision is unclear, lilypond, 10:16
  • Re: Issue 1216 in lilypond: DynamicTextSpanners should end like hairpins, lilypond, 10:12
  • Re: Issue 2156 in lilypond: lost commits, David Kastrup, 10:11
  • Re: Issue 2156 in lilypond: lost commits, lilypond, 10:08
  • Re: Issue 695 in lilypond: slurs may take too much vertical extent, lilypond, 10:01
  • Re: Issue 2156 in lilypond: lost commits, lilypond, 09:57
  • Issue 2157 in lilypond: Add "quick URL box" to documentation, lilypond, 09:50
  • Re: Issue 1802 in lilypond: system-system-spacing in lilypond-book-file within a LaTeX file, lilypond, 09:03
  • Re: Tuplet positioning on beamed notes is ugly, James, 09:01
  • Tuplet positioning on beamed notes is ugly, Chris Morgan, 08:50
  • Re: Issue 2135 in lilypond: --include option description not consistent with others in Application Usage, lilypond, 07:56
  • Re: Issue 2136 in lilypond: Patch: Doc: Usage --include option layout consistency, lilypond, 07:52
  • Re: Issue 2135 in lilypond: --include option description not consistent with others in Application Usage, lilypond, 07:48
  • Re: Issue 257 in lilypond: collision accent and tuplet bracket, lilypond, 07:29
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond, lilypond, 07:25
  • Re: Issue 2140 in lilypond: warning issued when --default-defining an option that lilypond doesn't know, lilypond, 07:04
  • Re: Issue 2156 in lilypond: lost commits, David Kastrup, 07:03
  • Re: Issue 2151 in lilypond: add-grace-note usage interferes with MIDI output in same score block, lilypond, 07:00
  • Re: Issue 2156 in lilypond: lost commits, lilypond, 06:56
  • Re: Issue 2156 in lilypond: lost commits, lilypond, 06:52
• December 30, 2011
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond, Carl Sorensen, 22:23
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 22:11
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 22:07
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 22:03
  • Issue 2156 in lilypond: lost commits, lilypond, 20:53
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond, lilypond, 20:49
  • Re: Issue 2136 in lilypond: Patch: Doc: Usage --include option layout consistency, lilypond, 20:18
  • Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 19:20
  • Re: Issue 2124 in lilypond: Patch: Regtest script improvements:, lilypond, 18:57
  • Re: Issue 2126 in lilypond: Patch: CG: Typos in "Programming work" and "Regression tests" sections., lilypond, 18:53
  • Re: TextScript isn't entirely scaled, while using another "staff-size", Marek Klein, 18:46
  • Issue 2155 in lilypond: TextScript isn't entirely scaled, while using another "staff-size", lilypond, 18:45
  • Re: Issue 2096 in lilypond: Patch: Implements cross-staff stem avoidance for dynamics., lilypond, 16:54
  • Re: Issue 2096 in lilypond: Patch: Implements cross-staff stem avoidance for dynamics., lilypond, 16:44
  • RE: error: auto beaming in tuplets after dotted semiquaver, Carl Sorensen, 16:38
  • Re: Issue 651 in lilypond: Volta bracket placed too high after a line break, lilypond, 16:35
  • Re: Issue 1325 in lilypond: Volta bracket going over to next line, lilypond, 16:31
  • Re: Issue 1935 in lilypond: Doc: internal ledger lines need to be documented in NR, lilypond, 16:27
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 16:23
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 16:19
  • Re: Issue 2152 in lilypond: Patch: Removes ugly side bars from learning, lilypond, 16:15
  • Re: Issue 2136 in lilypond: Patch: Doc: Usage --include option layout consistency, lilypond, 16:11
  • Re: Issue 2096 in lilypond: Patch: Implements cross-staff stem avoidance for dynamics., lilypond, 16:07
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 15:55
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 15:45
  • Re: Issue 2112 in lilypond: documentation: precising -dpreview, lilypond, 15:41
  • Re: Issue 2060 in lilypond: Patch: Hairpin missing padding at line break, lilypond, 15:33
  • Re: Issue 2108 in lilypond: Patch: Implements avoidance of cross-staff-stem vs. articulation collisions., lilypond, 15:27
  • Re: Issue 2096 in lilypond: Patch: Implements cross-staff stem avoidance for dynamics., lilypond, 15:23
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 15:11
  • Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 15:07
  • Re: Issue 2069 in lilypond: Patch: More nuanced BarLine extra-spacing-height to allow tighter horizontal spacing, lilypond, 15:03
  • Re: Issue 2015 in lilypond: Patch: Usability improvements to {doc,cg}-section.sh and corresponding section of CG, lilypond, 14:59
  • Re: Issue 2153 in lilypond: piano pedal bracket should stop at requested moment, lilypond, 14:54
  • Re: Issue 1097 in lilypond: better skylines for volta brackets, lilypond, 14:50
  • error: auto beaming in tuplets after dotted semiquaver, Martin Straeten, 14:47
  • Re: Issue 651 in lilypond: Volta bracket placed too high after a line break, lilypond, 14:46
  • Re: Issue 2148 in lilypond: object outlines shouldn't be rectangular, lilypond, 14:42
  • Re: Changing global text size, Marek Klein, 14:28
  • Issue 2154 in lilypond: Changing global text size, lilypond, 14:27
  • Re: Issue 1826 in lilypond: Guile 2.0 compat: `conditional-circle-markup' definition needs to be relocated, Ian Hulin, 14:05
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, Graham Percival, 13:59
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 13:22
  • Re: Issue 1826 in lilypond: Guile 2.0 compat: `conditional-circle-markup' definition needs to be relocated, lilypond, 13:17
  • Re: Issue 2112 in lilypond: documentation: precising -dpreview, -Eluze, 11:25
  • Re: Issue 2028 in lilypond: Make doc always recreates HTML files, lilypond, 10:20
  • Re: Issue 1129 in lilypond: Font styles return to default when font size changed, lilypond, 09:54
  • Re: Issue 1129 in lilypond: Font styles return to default when font size changed, lilypond, 09:50
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 09:36
  • Re: letters like é, Werner LEMBERG, 08:59
  • Re: Issue 2153 in lilypond: piano pedal should stop at requested moment, lilypond, 08:17
  • Re: letters like é, David Kastrup, 08:06
  • Re: letters like é, Werner LEMBERG, 07:46
  • Re: letters like é, David Kastrup, 07:41
  • Re: letters like é, Werner LEMBERG, 07:31
  • Re: Issue 2114 in lilypond: documentation: more nitpicking on application usage, lilypond, 07:30
  • Re: letters like é, David Kastrup, 07:08
  • Re: letters like é, Werner LEMBERG, 07:01
  • Re: Issue 2093 in lilypond: Doc: NR alternativeNumberingStyle (fix issue 2059) needs to be documented, lilypond, 06:44
  • Re: Issue 2059 in lilypond: Bar numbering of alternatives, lilypond, 04:56
  • Re: Issue 2059 in lilypond: Bar numbering of alternatives, lilypond, 04:31
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 04:27
  • Re: Issue 2093 in lilypond: Doc: alternativeNumberingStyle (fix issue 2059) should be documented, lilypond, 04:22
  • Re: letters like é, David Kastrup, 03:26
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 03:03
  • Re: Issue 2093 in lilypond: Doc: alternativeNumberingStyle (fix issue 2059) should be documented, lilypond, 02:54
  • Re: Issue 1935 in lilypond: Doc: internal ledger lines need to be documented in NR, lilypond, 02:49
  • Re: Issue 1935 in lilypond: Doc: internal ledger lines need to be documented in NR, lilypond, 02:45
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 01:59
  • Re: Issue 1566 in lilypond: Beam properties won't be changed after the start of the beam, lilypond, 01:54
  • Re: Issue 1566 in lilypond: Beam properties won't be changed after the start of the beam, lilypond, 01:42
  • Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly, lilypond, 01:36
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 01:26
  • Re: Issue 2136 in lilypond: Patch: Doc: Usage --include option layout consistency, lilypond, 00:35
  • Re: Issue 2136 in lilypond: Patch: Doc: Usage --include option layout consistency, lilypond, 00:31
  • Re: Changing global text size, James, 00:22
• December 29, 2011
  • Issue 2153 in lilypond: piano pedal should stop at requested moment, lilypond, 23:15
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 22:05
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 21:21
  • Re: Issue 1906 in lilypond: Build fails on Fedora, lilypond, 21:16
  • Re: Issue 2136 in lilypond: Patch: Doc: Usage --include option layout consistency, lilypond, 21:10
  • Changing global text size, Clément, 20:00
  • Re: letters like é, Werner LEMBERG, 18:43
  • Re: Issue 2143 in lilypond: accidental arrangement should depend on tightness of music, lilypond, 17:12
  • Re: Bug with (banjo) tablature rendering (workaround possible), Carl Sorensen, 16:42
  • Re: Bug with (banjo) tablature rendering (workaround possible), David Kastrup, 16:23
  • Re: letters like é, Pavel Roskin, 16:11
  • Re: Bug with (banjo) tablature rendering (workaround possible), Phil Holmes, 16:04
  • Re: letters like é, David Kastrup, 15:57
  • Re: letters like é, Janek Warchoł, 15:47
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 15:34
  • Re: letters like é, Werner LEMBERG, 14:09
  • Bug with (banjo) tablature rendering (workaround possible), Dirk De Wachter, 13:50
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 13:41
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 13:33
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 13:01
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 12:55
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 12:30
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 12:11
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 11:39
  • Re: Issue 1964 in lilypond: lilydev 2.0, lilypond, 10:46
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 10:42
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 10:37
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., Francisco Vila, 10:32
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., David Kastrup, 09:50
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., David Kastrup, 09:43
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., Ian Hulin, 09:25
  • Re: Issue 2152 in lilypond: Patch: Removes ugly side bars from learning, lilypond, 08:19
  • Issue 2152 in lilypond: Patch: Removes ugly side bars from learning, lilypond, 08:15
  • Re: Issue 2147 in lilypond: Patch: Fixes width of NR A.11 - List of special character, lilypond, 06:50
  • Re: Issue 1005 in lilypond: syntax highlighting in the docs, lilypond, 06:38
  • Re: letters like é, David Kastrup, 06:27
  • Re: letters like é, Werner LEMBERG, 06:13
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 06:13
  • Re: letters like é, Janek Warchoł, 06:03
  • Re: letters like é, David Kastrup, 06:00
  • Re: Issue 1637 in lilypond: include newest version of Fontforge in Lilydev, lilypond, 05:54
  • Re: Issue 1964 in lilypond: lilydev 2.0, lilypond, 05:50
  • Re: letters like é, Francisco Vila, 05:48
  • letters like é, Amund, 05:45
  • Re: Issue 2143 in lilypond: accidental arrangement should depend on tightness of music, lilypond, 05:20
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 05:16
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 04:27
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 03:43
  • Re: Issue 2142 in lilypond: accidental right-padding should depend on the tightness of music, lilypond, 03:10
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 02:49
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 01:22
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 01:03
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 00:59
• December 28, 2011
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 23:19
  • Re: Issue 2147 in lilypond: Patch: Fixes width of NR A.11 - List of special character, lilypond, 23:15
  • Re: Issue 2137 in lilypond: Patch: Doc: NR improve 'visibility' of 'q' operation, lilypond, 23:11
  • Re: Issue 1629 in lilypond: Tuplet line collides with fingering, lilypond, 23:07
  • Re: add-grace-property and midi, Brett McCoy, 22:48
  • Issue 2151 in lilypond: add-grace-note usage interferes with MIDI output in same score block, lilypond, 22:47
  • Re: Issue 2150 in lilypond: 2.15.23 doesn't compile on Mageia, lilypond, 22:18
  • Re: Issue 1826 in lilypond: Guile 2.0 compat: `conditional-circle-markup' definition needs to be relocated, lilypond, 22:14
  • Issue 2150 in lilypond: 2.15.23 doesn't compile on Mageia, lilypond, 22:01
  • add-grace-property and midi, Keith OHara, 21:54
  • Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 18:13
  • Re: Issue 2142 in lilypond: accidental right-padding should depend on the tightness of music, lilypond, 17:46
  • Re: Issue 2143 in lilypond: accidental arrangement should depend on tightness of music, lilypond, 17:02
  • Re: Issue 2143 in lilypond: accidental arrangement should depend on tightness of music, lilypond, 16:33
  • Re: Issue 2142 in lilypond: accidental right-padding should depend on the tightness of music, lilypond, 16:21
  • Re: Issue 2142 in lilypond: accidental right-padding should depend on the tightness of music, lilypond, 15:19
  • Re: Issue 2142 in lilypond: accidental right-padding should depend on the tightness of music, lilypond, 15:06
  • Re: Issue 2066 in lilypond: Patch: Prevents accidentals from hanging over barlines., lilypond, 15:02
  • Re: Issue 2143 in lilypond: accidental arrangement should depend on tightness of music, lilypond, 14:57
  • Re: Little wish: Abolish lyqi-hint from Lilypond website., James, 14:53
  • Re: Issue 2142 in lilypond: accidental right-padding should depend on the tightness of music, lilypond, 14:25
  • Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 14:17
  • Re: Issue 2141 in lilypond: accidental spacing - some accidentals are too far from each other, lilypond, 14:13
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 14:09
  • Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 14:05
  • Re: Issue 2143 in lilypond: accidental arrangement should depend on tightness of music, lilypond, 12:36
  • Re: Issue 2066 in lilypond: Patch: Prevents accidentals from hanging over barlines., lilypond, 12:26
  • Re: Issue 2142 in lilypond: accidental right-padding should depend on the tightness of music, lilypond, 12:20
  • Re: Little wish: Abolish lyqi-hint from Lilypond website., Trevor Daniels, 12:17
  • Re: Issue 2143 in lilypond: accidental arrangement should depend on tightness of music, lilypond, 12:16
  • Re: Issue 2143 in lilypond: accidental arrangement should depend on tightness of music, lilypond, 12:07
  • Re: Issue 2142 in lilypond: accidental right-padding should depend on the tightness of music, lilypond, 12:02
  • Re: Issue 2141 in lilypond: accidental spacing - some accidentals are too far from each other, lilypond, 11:58
  • Re: Issue 2066 in lilypond: Patch: Prevents accidentals from hanging over barlines., lilypond, 11:36
  • Re: Issue 2094 in lilypond: spacing-measure-length.ly regtest has time sig overlaying rest, lilypond, 11:32
  • Re: Issue 2066 in lilypond: Patch: Prevents accidentals from hanging over barlines., lilypond, 11:13
  • Re: Issue 2145 in lilypond: shorter versions of accidentals for use in tight situations, lilypond, 10:48
  • Issue 2148 in lilypond: object outlines shouldn't be rectangular, lilypond, 10:37
  • Re: Issue 2147 in lilypond: Patch: Fixes width of NR A.11 - List of special character, lilypond, 09:38
  • Issue 2147 in lilypond: Patch: Fixes width of NR A.11 - List of special character, lilypond, 09:34
  • Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 08:53
  • Re: Issue 726 in lilypond: Request: accidentals in the same octave would look better not aligned (in some cases), lilypond, 08:41
  • Re: Issue 2144 in lilypond: accidentals should be able to slide over/under suspended notes without problems, lilypond, 08:36
  • Re: Issue 2141 in lilypond: accidental spacing - some accidentals are too far from each other, lilypond, 08:32
  • Issue 2145 in lilypond: shorter versions of accidentals for use in tight situations, lilypond, 08:28
  • Issue 2144 in lilypond: accidentals should be able to slide over/under suspended notes without problems, lilypond, 08:24
  • Issue 2143 in lilypond: accidental arrangement should depend on tightness of music, lilypond, 08:20
  • Issue 2142 in lilypond: accidental right-padding should depend on the tightness of music, lilypond, 08:16
  • Issue 2141 in lilypond: accidental spacing - some accidentals are too far from each other, lilypond, 08:12
  • Re: Issue 2066 in lilypond: Patch: Prevents accidentals from hanging over barlines., lilypond, 05:07
  • Re: Issue 2066 in lilypond: Patch: Prevents accidentals from hanging over barlines., lilypond, 04:56
  • Re: Issue 1629 in lilypond: Tuplet line collides with fingering, lilypond, 04:37
  • Re: Issue 1947 in lilypond: Stem Tremoli for double-stemmed notes are too short on the right side., lilypond, 04:31
  • Re: Issue 2084 in lilypond: script-accidental avoidance fails for articulations, lilypond, 04:28
  • Re: Issue 1861 in lilypond: DynamicText attached to spacer rest not correctly aligned, lilypond, 04:23
  • Re: Issue 1361 in lilypond: Collision: TupletNumber and Script, lilypond, 04:19
  • Re: Issue 257 in lilypond: collision accent and tuplet bracket, lilypond, 04:15
  • Re: Issue 695 in lilypond: slurs may take too much vertical extent, lilypond, 04:11
• December 27, 2011
  • Re: Issue 2136 in lilypond: Patch: Doc: Usage --include option layout consistency, lilypond, 20:58
  • Re: Issue 2127 in lilypond: Patch: Directs output of texi2html to log files (GOP 9), Graham Percival, 14:25
  • Re: Issue 2139 in lilypond: Doc AU: command line options - where to use equal signs in short and long term definitions, James, 07:40
  • Re: Issue 1835 in lilypond: no learing manual pdf in dutch, lilypond, 07:12
  • Re: Issue 2127 in lilypond: Patch: Directs output of texi2html to log files (GOP 9), lilypond, 07:08
  • Re: Issue 2132 in lilypond: Patch: Sends woodwind regtest op to stderr, lilypond, 06:59
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 06:55
  • Re: Issue 2139 in lilypond: Doc AU: command line options - where to use equal signs in short and long term definitions, -Eluze, 06:55
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 06:32
  • Re: Issue 2132 in lilypond: Patch: Sends woodwind regtest op to stderr, lilypond, 06:25
  • Re: Issue 2132 in lilypond: Patch: Sends woodwind regtest op to stderr, lilypond, 06:13
• December 26, 2011
  • Re: Issue 2132 in lilypond: Patch: Sends woodwind regtest op to stderr, lilypond, 18:37
  • Re: Issue 2139 in lilypond: Doc AU: command line options - where to use equal signs in short and long term definitions, lilypond, 18:33
  • Re: Issue 2137 in lilypond: Patch: Doc: NR improve 'visibility' of 'q' operation, lilypond, 18:26
  • Re: Issue 2138 in lilypond: Patch: Doc: NR @knownissues for #'ignore-collision, lilypond, 18:14
  • Re: Issue 1377 in lilypond: Enhancement: make the last-page spacing more consistent and less tight, lilypond, 13:31
  • Re: Issue 1377 in lilypond: Enhancement: make the last-page spacing more consistent and less tight, lilypond, 04:41
  • Re: Collision of hyphen and barline, address@hidden, 04:12
  • Re: Issue 1377 in lilypond: Enhancement: make the last-page spacing more consistent and less tight, lilypond, 04:11
• December 25, 2011
  • Re: Something wrong/strange about flags?, Thomas Morley, 18:43
  • Re: Something wrong/strange about flags?, Neil Puttock, 18:18
  • Re: Something wrong/strange about flags?, Thomas Morley, 18:01
  • TextScript isn't entirely scaled, while using another "staff-size", Thomas Morley, 17:39
  • Re: Something wrong/strange about flags?, Neil Puttock, 17:38
  • Something wrong/strange about flags?, Thomas Morley, 17:27
  • Re: Issue 766 in lilypond: Indent should automatically adapt to instrument names' length., lilypond, 17:08
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 14:05
  • Re: Issue 2138 in lilypond: Patch: Doc: NR @knownissues for #'ignore-collision, lilypond, 11:51
  • Re: Issue 2136 in lilypond: Patch: Doc: Usage --include option layout consistency, lilypond, 11:47
  • Re: Issue 2137 in lilypond: Patch: Doc: NR improve 'visibility' of 'q' operation, lilypond, 11:43
  • Issue 2140 in lilypond: warning issued when --default-defining an option that lilypond doesn't know, lilypond, 10:37
  • Issue 2139 in lilypond: Doc AU: command line options - where to use equal signs in short and long term definitions, lilypond, 10:16
  • Re: Issue 2111 in lilypond: documentation of include-settings in Usage, lilypond, 08:21
  • Re: Collision of hyphen and barline, James, 07:48
  • Re: Feature request: multiplication should work on notes, chords and all rests, James, 07:35
  • Re: Issue 2138 in lilypond: Patch: Doc: NR @knownissues for #'ignore-collision, lilypond, 07:33
  • Issue 2138 in lilypond: Patch: Doc: NR @knownissues for #'ignore-collision, lilypond, 07:29
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 07:00
  • Re: Issue 2137 in lilypond: Patch: Doc: NR improve 'visibility' of 'q' operation, lilypond, 06:56
  • Re: Issue 2111 in lilypond: documentation of include-settings in Usage, lilypond, 06:52
  • Re: Issue 2136 in lilypond: Patch: Doc: Usage --include option layout consistency, lilypond, 06:48
  • Issue 2137 in lilypond: Patch: Doc: NR improve 'visibility' of 'q' operation, lilypond, 05:20
• December 24, 2011
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 22:45
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 20:17
  • Re: Issue 1410 in lilypond: Rest in lower voice should be placed above notes in in upper if voices are crossed., lilypond, 17:53
  • Re: Issue 2130 in lilypond: Hairpin hits barline at line break, lilypond, 17:27
  • Re: Issue 1964 in lilypond: lilydev 2.0, lilypond, 13:41
  • Re: Issue 2136 in lilypond: Patch: Doc: Usage --include option layout consistency, lilypond, 10:47
  • Re: Issue 1964 in lilypond: lilydev 2.0, lilypond, 09:58
  • Re: turning the sequence of --include, -I=directory, -Eluze, 09:53
  • Re: Issue 2136 in lilypond: Patch: Doc: Usage --include option layout consistency, lilypond, 09:49
  • Re: Issue 2135 in lilypond: --include option description not consistent with others in Application Usage, lilypond, 09:45
  • Re: Issue 2135 in lilypond: --include option description not consistent with others in Application Usage, lilypond, 09:41
  • Issue 2136 in lilypond: Patch: Doc: Usage --include option layout consistency, lilypond, 09:37
  • Re: turning the sequence of --include, -I=directory, James, 09:33
  • Issue 2135 in lilypond: --include option description not consistent with others in Application Usage, lilypond, 09:32
  • Re: turning the sequence of --include, -I=directory, James, 08:55
  • turning the sequence of --include, -I=directory, -Eluze, 08:48
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 06:42
  • Re: Issue 1698 in lilypond: Slurs and ties are not correct over repeats, lilypond, 06:18
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 04:07
• December 23, 2011
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 18:22
  • Re: Issue 2102 in lilypond: vertical spacing of a nonstaff line below the system, lilypond, 17:51
  • Re: Issue 1906 in lilypond: Build fails on Fedora, lilypond, 00:40
  • Re: Issue 2130 in lilypond: Hairpin hits barline at line break, lilypond, 00:36
  • Re: Issue 2127 in lilypond: Patch: Directs output of texi2html to log files (GOP 9), lilypond, 00:32
  • Re: Issue 2084 in lilypond: script-accidental avoidance fails for articulations, lilypond, 00:28
  • Re: Issue 1947 in lilypond: Stem Tremoli for double-stemmed notes are too short on the right side., lilypond, 00:24
  • Re: Issue 1410 in lilypond: Rest in lower voice should be placed above notes in in upper if voices are crossed., lilypond, 00:20
• December 22, 2011
  • Re: Issue 2030 in lilypond: 2.14.2, dynamic cast crash introduced in commit 6f6369c0, lilypond, 12:59
  • Re: Issue 1964 in lilypond: lilydev 2.0, lilypond, 12:55
  • Re: Issue 2030 in lilypond: 2.14.2, dynamic cast crash introduced in commit 6f6369c0, lilypond, 12:37
  • Re: Issue 2030 in lilypond: 2.14.2, dynamic cast crash introduced in commit 6f6369c0, lilypond, 12:28
  • Re: Issue 1964 in lilypond: lilydev 2.0, lilypond, 12:21
  • Re: Issue 1964 in lilypond: lilydev 2.0, lilypond, 10:57
  • Re: Issue 2134 in lilypond: Redirect old website / download to new location, lilypond, 10:42
  • Re: Issue 2134 in lilypond: Redirect old website / download to new location, lilypond, 07:02
  • Issue 2134 in lilypond: Redirect old website / download to new location, lilypond, 05:14
  • Re: Issue 1964 in lilypond: lilydev 2.0, lilypond, 05:07
  • Re: Issue 2133 in lilypond: Patch: Emacs mode lines for parser.yy and lexer.ll, lilypond, 03:35
• December 21, 2011
  • Re: Feature request: change clef in the beginning of piece without affecting other staves, David Kastrup, 17:40
  • Re: Issue 695 in lilypond: slurs may take too much vertical extent, lilypond, 17:26
  • Feature request: change clef in the beginning of piece without affecting other staves, Pavel Roskin, 17:25
  • Re: Issue 2133 in lilypond: Patch: Emacs mode lines for parser.yy and lexer.ll, lilypond, 17:22
  • Re: Issue 2132 in lilypond: Patch: Sends woodwind regtest op to stderr, lilypond, 17:18
  • Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes, lilypond, 16:26
  • Re: Issue 2072 in lilypond: Add proper complex variables to Lilypond, Thomas Morley, 16:11
  • Re: Issue 2131 in lilypond: Patch: Tie LilyPond, lexer and parser together more type-safely., lilypond, 16:07
  • Issue 2133 in lilypond: Patch: Emacs mode lines for parser.yy and lexer.ll, lilypond, 15:56
  • Re: Issue 2131 in lilypond: Patch: Tie LilyPond, lexer and parser together more type-safely., lilypond, 15:10
  • Re: Issue 695 in lilypond: slurs may take too much vertical extent, lilypond, 14:45
  • Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes, lilypond, 13:52
  • Issue 2132 in lilypond: Patch: Sends woodwind regtest op to stderr, lilypond, 13:16
  • Re: Issue 695 in lilypond: slurs may take too much vertical extent, lilypond, 12:36
  • Re: Issue 2131 in lilypond: Patch: Tie LilyPond, lexer and parser together more type-safely., lilypond, 12:33
  • Issue 2131 in lilypond: Patch: Tie LilyPond, lexer and parser together more type-safely., lilypond, 11:43
  • Re: Issue 1861 in lilypond: DynamicText attached to spacer rest not correctly aligned, lilypond, 11:34
  • Re: Issue 695 in lilypond: slurs may take too much vertical extent, lilypond, 11:30
  • Re: Issue 695 in lilypond: slurs may take too much vertical extent, lilypond, 11:26
  • Re: Issue 257 in lilypond: collision accent and tuplet bracket, lilypond, 11:22
  • Re: Issue 2109 in lilypond: do not tinker with the position of a pitched rest, lilypond, 11:18
  • Re: Issue 2094 in lilypond: spacing-measure-length.ly regtest has time sig overlaying rest, lilypond, 11:13
  • Re: Issue 1861 in lilypond: DynamicText attached to spacer rest not correctly aligned, lilypond, 10:43
  • Re: Issue 2111 in lilypond: documentation of include-settings in Usage, -Eluze, 09:34
  • Re: Issue 695 in lilypond: slurs may take too much vertical extent, lilypond, 09:33
  • Re: Issue 2111 in lilypond: documentation of include-settings in Usage, lilypond, 09:29
  • Re: Issue 695 in lilypond: slurs may take too much vertical extent, lilypond, 07:34
  • Re: Issue 2109 in lilypond: do not tinker with the position of a pitched rest, lilypond, 05:52
  • Re: Issue 2109 in lilypond: do not tinker with the position of a pitched rest, lilypond, 05:18
  • Re: Issue 257 in lilypond: collision accent and tuplet bracket, lilypond, 04:50
  • Re: Issue 2123 in lilypond: Patch: Gets cross-staff collisions right for beams., lilypond, 03:11
  • Re: Issue 2122 in lilypond: Regression in chord-name-exceptions.ly - badly spaced chord names, lilypond, 03:07
  • Re: Issue 2116 in lilypond: Patch: Shows Flags in tabFullNotation, lilypond, 03:03
  • Re: Issue 2090 in lilypond: Add documentation for command line quoting on Windows, lilypond, 02:59
  • Re: Issue 2113 in lilypond: Beamlet points the wrong way when tuplet sixteenths are beamed with eighths, lilypond, 00:10
  • Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to "programming error" messages, lilypond, 00:06
• December 20, 2011
  • Re: Issue 1906 in lilypond: Build fails on Fedora, lilypond, 23:56
  • Re: Issue 2124 in lilypond: Patch: Regtest script improvements:, lilypond, 23:52
  • Re: Issue 2125 in lilypond: Patch: Build: Don't rebuild everything each time unless necessary., lilypond, 23:50
  • Re: Issue 2113 in lilypond: Beamlet points the wrong way when tuplet sixteenths are beamed with eighths, lilypond, 23:49
  • Re: Issue 2125 in lilypond: Patch: Build: Don't rebuild everything each time unless necessary., lilypond, 23:48
  • Re: Issue 2027 in lilypond: make website doesn't have dependencies, lilypond, 23:44
  • Re: Issue 2124 in lilypond: Patch: Regtest script improvements:, lilypond, 23:35
  • Re: Issue 2123 in lilypond: Patch: Gets cross-staff collisions right for beams., lilypond, 23:31
  • Re: Issue 2122 in lilypond: Regression in chord-name-exceptions.ly - badly spaced chord names, lilypond, 23:27
  • Re: Issue 2116 in lilypond: Patch: Shows Flags in tabFullNotation, lilypond, 23:23
  • Re: Issue 2102 in lilypond: vertical spacing of a nonstaff line below the system, lilypond, 23:15
  • Re: Issue 2090 in lilypond: Add documentation for command line quoting on Windows, lilypond, 23:11
  • Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to "programming error" messages, lilypond, 23:07
  • Re: Issue 2027 in lilypond: make website doesn't have dependencies, lilypond, 23:03
  • Re: Issue 2058 in lilypond: horizontal spacing allows space for neighboring staves in surprising ways, lilypond, 20:17
  • Re: Issue 2011 in lilypond: configure doesn't like clang++, lilypond, 20:12
  • Re: Issue 2064 in lilypond: Patch: Prevents Slur vs Dots collisions., lilypond, 19:52
  • Re: Issue 2064 in lilypond: Patch: Prevents Slur vs Dots collisions., lilypond, 19:48
  • Re: Issue 2046 in lilypond: Patch: Fixes certain undocumented properties., lilypond, 19:44
  • Re: Issue 1726 in lilypond: python versions might not be updating, lilypond, 19:38
  • Re: Issue 2030 in lilypond: 2.14.2, dynamic cast crash introduced in commit 6f6369c0, lilypond, 19:31
  • Re: Issue 2011 in lilypond: configure doesn't like clang++, lilypond, 19:16
  • Re: Issue 1941 in lilypond: Patch: Fixes to projecthosting_upload.py, lilypond, 18:51
  • Re: Issue 1941 in lilypond: Patch: Fixes to projecthosting_upload.py, lilypond, 18:36
  • Re: Issue 2094 in lilypond: spacing-measure-length.ly regtest has time sig overlaying rest, lilypond, 18:03
  • Re: Issue 2129 in lilypond: Patch: Changes to allow compiling with -Werror using gcc 4.6.2 on i386., lilypond, 17:59
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 16:52
  • Re: Issue 1267 in lilypond: Documentation for 'ignore-collision is unclear, lilypond, 16:37
  • Re: Issue 2112 in lilypond: documentation: precising -dpreview, lilypond, 16:33
  • Re: Issue 2114 in lilypond: documentation: more nitpicking on application usage, lilypond, 16:29
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 16:18
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 15:25
  • Re: Issue 2027 in lilypond: make website doesn't have dependencies, lilypond, 15:08
  • Re: Issue 2027 in lilypond: make website doesn't have dependencies, lilypond, 15:04
  • Re: Issue 2129 in lilypond: Patch: Changes to allow compiling with -Werror using gcc 4.6.2 on i386., lilypond, 14:09
  • Re: Issue 1267 in lilypond: Documentation for 'ignore-collision is unclear, lilypond, 12:51
  • Re: Issue 2130 in lilypond: Hairpin hits barline at line break, lilypond, 12:13
  • Re: Issue 2130 in lilypond: Hairpin hits barline at line break, lilypond, 12:02
  • Re: Issue 1726 in lilypond: python versions might not be updating, lilypond, 11:58
  • Re: Issue 1410 in lilypond: Rest in lower voice should be placed above notes in in upper if voices are crossed., lilypond, 11:54
  • Re: Issue 1267 in lilypond: Documentation for 'ignore-collision is unclear, lilypond, 11:50
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 11:46
  • Re: Issue 2126 in lilypond: Patch: CG: Typos in "Programming work" and "Regression tests" sections., lilypond, 11:42
  • Re: Issue 2105 in lilypond: Patch: Remove warning and .aux file left over by lilypond-book., lilypond, 11:38
  • Re: Issue 2103 in lilypond: Patch: Output a newline by default at the end of progress messages., lilypond, 11:34
  • Re: Issue 2107 in lilypond: new patch for lilypond-book on windows, lilypond, 11:30
  • Re: Issue 1802 in lilypond: system-system-spacing in lilypond-book-file within a LaTeX file, lilypond, 11:26
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 11:22
  • Re: Issue 2130 in lilypond: Hairpin hits barline at line break, lilypond, 11:18
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 11:14
  • Issue 2130 in lilypond: Hairpin hits barline at line break, lilypond, 11:10
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 10:59
  • Re: Issue 1908 in lilypond: Causes lily to fail during regtests if binary is unoptimized, lilypond, 10:54
  • Re: Issue 2127 in lilypond: Patch: Directs output of texi2html to log files (GOP 9), lilypond, 10:45
  • Re: Issue 2129 in lilypond: Patch: Changes to allow compiling with -Werror using gcc 4.6.2 on i386., lilypond, 10:41
  • Re: Issue 2084 in lilypond: script-accidental avoidance fails for articulations, lilypond, 10:37
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 10:33
  • Re: Issue 1947 in lilypond: Stem Tremoli for double-stemmed notes are too short on the right side., lilypond, 10:29
  • Re: Issue 1906 in lilypond: Build fails on Fedora, lilypond, 10:25
  • Re: Issue 2027 in lilypond: make website doesn't have dependencies, lilypond, 09:21
  • Re: Issue 1726 in lilypond: python versions might not be updating, lilypond, 09:17
  • Re: Issue 2127 in lilypond: Patch: Directs output of texi2html to log files (GOP 9), lilypond, 05:52
  • Re: Issue 2129 in lilypond: Patch: Changes to allow compiling with -Werror using gcc 4.6.2 on i386., lilypond, 05:23
  • Re: Issue 2127 in lilypond: Patch: Directs output of texi2html to log files (GOP 9), lilypond, 05:19
  • Re: Issue 2126 in lilypond: Patch: CG: Typos in "Programming work" and "Regression tests" sections., lilypond, 05:15
  • Re: Issue 2123 in lilypond: Patch: Gets cross-staff collisions right for beams., lilypond, 05:11
  • Re: Issue 2098 in lilypond: Patch: Now use astyle 2.02.1, lilypond, 05:07
  • Re: Issue 2072 in lilypond: Add proper complex variables to Lilypond, lilypond, 05:03
  • Re: Segfault in 2.13.63, David Kastrup, 04:08
  • Segfault in 2.13.63, John David Duncan, 03:30
  • Re: Issue 1267 in lilypond: Documentation for 'ignore-collision is unclear, lilypond, 03:07
  • Re: Issue 1802 in lilypond: system-system-spacing in lilypond-book-file within a LaTeX file, lilypond, 02:43
• December 19, 2011
  • Re: Issue 1410 in lilypond: Rest in lower voice should be placed above notes in in upper if voices are crossed., lilypond, 22:49
  • Issue 2129 in lilypond: Patch: Changes to allow compiling with -Werror using gcc 4.6.2 on i386., lilypond, 19:52
  • Re: Issue 1874 in lilypond: some stems are no longer transparent in the docs, lilypond, 19:03
  • Re: Issue 1874 in lilypond: some stems are no longer transparent in the docs, lilypond, 18:51
  • Re: Issue 1906 in lilypond: Build fails on Fedora, lilypond, 18:35
  • Re: Issue 1900 in lilypond: Multiple fret-diagram-x markup commands and lilypond safe-mode, lilypond, 18:15
  • Re: Issue 1645 in lilypond: Beam_collision_engraver sometimes fails on demisemiquavers or shorter notes, lilypond, 17:46
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 16:26
  • Re: Let header (or footer or title) elements be individually customizable, Ralph Palmer, 14:35
  • Issue 2128 in lilypond: Let header (or footer or title) elements be individually customizable, lilypond, 14:35
  • Re: Issue 1906 in lilypond: Build fails on Fedora, lilypond, 14:30
  • Re: 2.15.15 doesn't build on Mageia, Ralph Palmer, 14:22
  • Re: Issue 1906 in lilypond: Build fails on Fedora, lilypond, 14:21
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 13:04
  • Issue 2127 in lilypond: Patch: Directs output of texi2html to log files (GOP 9), lilypond, 11:31
  • Re: Issue 1947 in lilypond: Stem Tremoli for double-stemmed notes are too short on the right side., lilypond, 09:49
  • Re: Issue 2084 in lilypond: script-accidental avoidance fails for articulations, lilypond, 09:02
  • Re: Issue 2120 in lilypond: skipTypesetting a tie is postponed to the not skipped part starting with 2 notes of same pitch, lilypond, 08:56
  • Re: Issue 2084 in lilypond: script-accidental avoidance fails for articulations, lilypond, 07:37
  • Re: Issue 2119 in lilypond: script-accidental avoidance fails for articulations, lilypond, 07:33
  • Re: Issue 1908 in lilypond: Causes lily to fail during regtests if binary is unoptimized, lilypond, 05:08
  • Re: Issue 2108 in lilypond: Patch: Implements avoidance of cross-staff-stem vs. articulation collisions., lilypond, 05:04
  • Let header (or footer or title) elements be individually customizable, Denis Bitouzé, 05:00
  • Re: Issue 2096 in lilypond: Patch: Implements cross-staff stem avoidance for dynamics., lilypond, 02:06
• December 18, 2011
  • Re: Issue 1216 in lilypond: DynamicTextSpanners should end like hairpins, lilypond, 21:36
  • Re: Issue 2103 in lilypond: Patch: Output a newline by default at the end of progress messages., lilypond, 21:32
  • Re: Issue 2105 in lilypond: Patch: Remove warning and .aux file left over by lilypond-book., lilypond, 21:28
  • Re: Issue 2107 in lilypond: new patch for lilypond-book on windows, lilypond, 21:24
  • Re: Issue 2108 in lilypond: Patch: Implements avoidance of cross-staff-stem vs. articulation collisions., lilypond, 21:20
  • Re: Issue 2096 in lilypond: Patch: Implements cross-staff stem avoidance for dynamics., lilypond, 21:16
  • Re: Issue 1377 in lilypond: Enhancement: make the last-page spacing more consistent and less tight, lilypond, 21:12
  • Re: Issue 2126 in lilypond: Patch: CG: Typos in "Programming work" and "Regression tests" sections., lilypond, 20:06
  • Re: Issue 2027 in lilypond: make website doesn't have dependencies, lilypond, 20:02
  • Re: Issue 1908 in lilypond: Causes lily to fail during regtests if binary is unoptimized, lilypond, 19:35
  • Re: Issue 2090 in lilypond: Add documentation for command line quoting on Windows, lilypond, 19:31
  • Re: Issue 1726 in lilypond: python versions might not be updating, lilypond, 19:27
  • Re: Issue 2122 in lilypond: Regression in chord-name-exceptions.ly - badly spaced chord names, lilypond, 18:41
  • Re: Issue 2027 in lilypond: make website doesn't have dependencies, lilypond, 18:12
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 18:07
  • Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 14:53
  • Issue 2126 in lilypond: Patch: CG: Typos in "Programming work" and "Regression tests" sections., lilypond, 13:54
  • Re: Issue 2125 in lilypond: Patch: Build: Don't rebuild everything each time unless necessary., lilypond, 13:27
  • Re: Issue 2124 in lilypond: Patch: Regtest script improvements:, lilypond, 13:23
  • Re: Issue 2122 in lilypond: Regression in chord-name-exceptions.ly - badly spaced chord names, lilypond, 13:19
  • Re: Issue 2123 in lilypond: Patch: Gets cross-staff collisions right for beams., lilypond, 12:22
  • Re: Issue 2113 in lilypond: Beamlet points the wrong way when tuplet sixteenths are beamed with eighths, lilypond, 12:18
  • Re: Issue 2122 in lilypond: Regression in chord-name-exceptions.ly - badly spaced chord names, lilypond, 12:14
  • Re: Issue 2122 in lilypond: Regression in chord-name-exceptions.ly - badly spaced chord names, lilypond, 12:10
  • Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved., lilypond, 12:03
  • Re: Issue 2124 in lilypond: Patch: Regtest script improvements:, lilypond, 11:59
  • Re: Issue 2124 in lilypond: Patch: Regtest script improvements:, lilypond, 11:55
  • Re: Issue 2125 in lilypond: Patch: Build: Don't rebuild everything each time unless necessary., lilypond, 11:51
  • Issue 2125 in lilypond: Patch: Build: Don't rebuild everything each time unless necessary., lilypond, 11:47
  • Issue 2124 in lilypond: Patch: Regtest script improvements:, lilypond, 11:43
  • Re: Issue 2056 in lilypond: Typos in German translation, lilypond, 11:39
  • Issue 2123 in lilypond: Patch: Gets cross-staff collisions right for beams., lilypond, 11:35
  • Re: Typo in Documentation (2), Phil Holmes, 11:35
  • Re: Typo in Documentation, Phil Holmes, 11:34
  • Issue 2122 in lilypond: Regression in chord-name-exceptions.ly - badly spaced chord names, lilypond, 11:31
  • Typo in Documentation (2), hgz, 10:00
  • Typo in Documentation, hgz, 09:55
  • Re: Issue 2093 in lilypond: Doc: alternativeNumberingStyle (fix issue 2059) should be documented, lilypond, 08:54
  • Re: Issue 2121 in lilypond: Doc: alternativeNumberingStyle (fix issue 2059) should be documented, lilypond, 08:50
  • Re: Issue 2121 in lilypond: Doc: alternativeNumberingStyle (fix issue 2059) should be documented, lilypond, 08:46
  • Re: Issue 2103 in lilypond: Patch: Output a newline by default at the end of progress messages., lilypond, 08:27
  • Re: Issue 2109 in lilypond: do not tinker with the position of a pitched rest, lilypond, 08:23
  • Re: Issue 2096 in lilypond: Patch: Implements cross-staff stem avoidance for dynamics., lilypond, 08:19
  • Re: Issue 2096 in lilypond: Patch: Implements cross-staff stem avoidance for dynamics., lilypond, 08:14
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 08:10
  • Re: Issue 2105 in lilypond: Patch: Remove warning and .aux file left over by lilypond-book., lilypond, 08:06
  • Re: Issue 2108 in lilypond: Patch: Implements avoidance of cross-staff-stem vs. articulation collisions., lilypond, 08:02
  • Re: Issue 2116 in lilypond: Patch: Shows Flags in tabFullNotation, lilypond, 07:58
  • Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved., lilypond, 07:54
  • Re: Issue 2093 in lilypond: Doc: alternativeNumberingStyle (fix issue 2059) should be documented, lilypond, 07:50
  • Re: Issue 2118 in lilypond: Overriding stencil of StringNumber leads to "programming error"messages, lilypond, 07:46
  • Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to "programming error" messages, lilypond, 07:42
  • Re: Issue 2120 in lilypond: skipTypesetting a tie is postponed to the not skipped part starting with 2 notes of same pitch, lilypond, 07:30
  • Issue 2121 in lilypond: Doc: alternativeNumberingStyle (fix issue 2059) should be documented, lilypond, 07:26
  • Re: alternativeNumberingStyle (fix issue 2059) should be documented, Phil Holmes, 07:25
  • Issue 2120 in lilypond: skipTypesetting a tie is postponed to the not skipped part starting with 2 notes of same pitch, lilypond, 07:22
  • Re: installer lilypond, Phil Holmes, 07:20
  • Re: Overriding stencil of StringNumber leads to "programming error"messages, Phil Holmes, 07:15
  • Issue 2119 in lilypond: script-accidental avoidance fails for articulations, lilypond, 07:14
  • Re: script-accidental avoidance fails for articulations, Phil Holmes, 07:14
  • Issue 2118 in lilypond: Overriding stencil of StringNumber leads to "programming error"messages, lilypond, 07:10
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 06:16
  • Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to "programming error" messages, lilypond, 04:30
• December 17, 2011
  • Re: Issue 2113 in lilypond: Beamlet points the wrong way when tuplet sixteenths are beamed with eighths, lilypond, 23:23
  • Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to "programming error" messages, lilypond, 23:19
  • Re: Issue 1392 in lilypond: Internals Reference should document \paper variables, lilypond, 18:19
  • Re: Issue 2115 in lilypond: Documentation: Add note to show how to find valid entries for \language in Usage, lilypond, 16:24
  • Re: 2.15.15 doesn't build on Mageia, Thomas, 15:51
  • Re: Issue 2112 in lilypond: documentation: precising -dpreview, lilypond, 15:10
  • Re: Issue 2114 in lilypond: documentation: more nitpicking on application usage, lilypond, 15:06
  • Re: Issue 2116 in lilypond: Patch: Shows Flags in tabFullNotation, lilypond, 12:21
  • Re: Issue 2113 in lilypond: Beamlet points the wrong way when tuplet sixteenths are beamed with eighths, lilypond, 12:17
  • Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to "programming error" messages, lilypond, 12:13
  • Re: Issue 2114 in lilypond: documentation: more nitpicking on application usage, lilypond, 11:35
  • Re: Issue 2112 in lilypond: documentation: precising -dpreview, lilypond, 11:31
  • Re: Issue 2099 in lilypond: texi2pdf --quiet hides too much, David Kastrup, 11:20
  • Issue 2117 in lilypond: Update git-cl to use Type-Patch, lilypond, 11:06
  • Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to "programming error" messages, lilypond, 11:01
  • Re: No flags printed with "2.15.20" using TabStaff with \tabFullNotation, address@hidden, 10:58
  • Issue 2116 in lilypond: Patch: Shows Flags in tabFullNotation, lilypond, 10:57
  • Re: Issue 2113 in lilypond: Beamlet points the wrong way when tuplet sixteenths are beamed with eighths, lilypond, 10:52
  • Re: Issue 2099 in lilypond: texi2pdf --quiet hides too much, lilypond, 10:40
  • No flags printed with "2.15.20" using TabStaff with \tabFullNotation, Thomas Morley, 10:39
  • Re: Issue 2099 in lilypond: texi2pdf --quiet hides too much, lilypond, 10:17
  • Re: Issue 2099 in lilypond: texi2pdf --quiet hides too much, lilypond, 10:06
  • Re: Issue 2099 in lilypond: texi2pdf --quiet hides too much, lilypond, 09:11
  • Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc, lilypond, 08:50
  • Re: Issue 2114 in lilypond: documentation: more nitpicking on application usage, lilypond, 08:32
  • Re: Issue 2112 in lilypond: documentation: precising -dpreview, lilypond, 08:28
  • Re: Issue 2113 in lilypond: Beamlet points the wrong way when tuplet sixteenths are beamed with eighths, lilypond, 08:13
  • Re: Issue 2115 in lilypond: Documentation: Add note to show how to find valid entries for \language in Usage, lilypond, 08:09
  • Re: Issue 2090 in lilypond: Add documentation for command line quoting on Windows, lilypond, 08:05
  • Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to "programming error" messages, lilypond, 08:01
  • Re: Issue 2113 in lilypond: Beamlet points the wrong way when tuplet sixteenths are beamed with eighths, lilypond, 07:56
  • Re: Issue 2114 in lilypond: documentation: more nitpicking on application usage, lilypond, 07:39
  • Re: documentation: more nitpicking on application usage (AU), Phil Holmes, 07:28
  • Re: Issue 2115 in lilypond: Documentation: Add note to show how to find valid entries for \language in Usage, lilypond, 06:56
  • Re: Issue 1995 in lilypond: scheme-tutorial.itely: avoid unnecessary copying, lilypond, 06:47
  • Issue 2115 in lilypond: Documentation: Add note to show how to find valid entries for \language in Usage, lilypond, 06:43
  • Re: documentation: more nitpicking on application usage (AU), James, 06:42
  • Issue 2114 in lilypond: documentation: more nitpicking on application usage, lilypond, 06:39
  • Re: Issue 1995 in lilypond: scheme-tutorial.itely: avoid unnecessary copying, lilypond, 06:22
  • documentation: more nitpicking on application usage (AU), -Eluze, 06:22
  • Re: Issue 1995 in lilypond: scheme-tutorial.itely: avoid unnecessary copying, lilypond, 06:06
  • Re: Issue 2111 in lilypond: documentation of include-settings in Usage, lilypond, 05:59
  • Re: Issue 1999 in lilypond: Nonsensical example in programming-interface.itely, lilypond, 05:39
  • Re: Issue 2090 in lilypond: Add documentation for command line quoting on Windows, lilypond, 05:33
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, David Kastrup, 04:15
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 03:45
  • Re: Issue 2102 in lilypond: vertical spacing of a nonstaff line below the system, lilypond, 03:40
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 01:06
  • Re: Issue 2102 in lilypond: vertical spacing of a nonstaff line below the system, lilypond, 01:02
  • Re: Issue 2102 in lilypond: vertical spacing of a nonstaff line below the system, lilypond, 00:58
  • Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to "programming error" messages, lilypond, 00:22
  • Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to "programming error" messages, lilypond, 00:18
• December 16, 2011
  • Re: Issue 2113 in lilypond: Beamlet points the wrong way when tuplet sixteenths are beamed with eighths, lilypond, 23:15
  • Issue 2113 in lilypond: Beamlet points the wrong way when tuplet sixteenths are beamed with eighths, lilypond, 21:47
  • Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved., lilypond, 17:14
  • Re: Issue 2106 in lilypond: Patch: Build fixes for translated manuals: dependencies and a typo, lilypond, 16:54
  • Re: Issue 2106 in lilypond: Patch: Build fixes for translated manuals: dependencies and a typo, lilypond, 16:54
  • Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved., lilypond, 16:50
  • Re: Issue 2106 in lilypond: Patch: Build fixes for translated manuals: dependencies and a typo, lilypond, 16:38
  • hot potato bug handling, Graham Percival, 15:56
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 14:54
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, Werner LEMBERG, 14:43
  • Re: Beam subdivision bug in 2.15.22, Carl Sorensen, 14:20
  • Re: Beam subdivision bug in 2.15.22, Xavier Scheuer, 14:13
  • Beam subdivision bug in 2.15.22, Thomas Scharkowski, 13:48
  • Re: issues to verify, Phil Holmes, 12:18
  • Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved., lilypond, 11:31
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond, lilypond, 11:27
  • Issue 2112 in lilypond: documentation: precising -dpreview, lilypond, 11:22
  • Re: issues to verify, Graham Percival, 11:21
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 11:18
  • Re: issues to verify, Phil Holmes, 11:18
  • Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved., lilypond, 11:14
  • Re: documentation: precising -dpreview, Marek Klein, 11:13
  • Re: documentation of include-settings in Usage, Marek Klein, 11:11
  • Issue 2111 in lilypond: documentation of include-settings in Usage, lilypond, 11:10
  • Re: Issue 2106 in lilypond: Patch: Build fixes for translated manuals: dependencies and a typo, lilypond, 11:07
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond, lilypond, 11:02
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond, lilypond, 10:50
  • Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display, lilypond, 09:44
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 09:40
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond, lilypond, 09:36
  • Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 09:28
  • Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 09:24
  • Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 08:52
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond, lilypond, 07:36
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond, lilypond, 07:26
  • documentation of include-settings in Usage, -Eluze, 07:19
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond 2.14.x, lilypond, 07:15
  • Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display, lilypond, 07:08
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond 2.14.x, lilypond, 07:02
  • documentation: precising -dpreview, -Eluze, 06:49
  • Re: Issue 1645 in lilypond: Beam_collision_engraver sometimes fails on demisemiquavers or shorter notes, lilypond, 06:43
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond 2.14.x, lilypond, 06:39
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 06:35
  • Re: Issue 1567 in lilypond: Add documentation for footnotes, lilypond, 06:31
  • Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display, lilypond, 06:27
  • Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 06:22
  • Re: Issue 2087 in lilypond: Patch: Fixes various warnings from clang++, lilypond, 06:18
  • Re: Issue 2080 in lilypond: Request for better cross referencing of ornaments, lilypond, 06:14
  • Re: Issue 2101 in lilypond: Doc: NR Added glissando grob skip snippet to 1.3.3, lilypond, 06:10
  • Re: Issue 2065 in lilypond: Scripts in cross-staff constructions can collide with span bars, lilypond, 06:06
  • Re: Issue 2106 in lilypond: Patch: Build fixes for translated manuals: dependencies and a typo, lilypond, 06:02
  • Re: Issue 2110 in lilypond: Improved example showing use of whiteout and layer properties for ties avoiding collision with staff objects, lilypond, 05:54
  • Re: Issue 2102 in lilypond: vertical spacing of a nonstaff line below the system, lilypond, 05:25
  • Re: Issue 1645 in lilypond: Beam_collision_engraver sometimes fails on demisemiquavers or shorter notes, lilypond, 04:30
  • Re: Issue 2080 in lilypond: Request for better cross referencing of ornaments, lilypond, 03:54
  • Re: Issue 2101 in lilypond: Doc: NR Added glissando grob skip snippet to 1.3.3, lilypond, 03:49
  • Re: Issue 2065 in lilypond: Scripts in cross-staff constructions can collide with span bars, lilypond, 03:39
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 03:35
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 03:31
  • Re: Feature request: multiplication should work on notes, chords and all rests, David Kastrup, 01:38
  • Re: Issue 2102 in lilypond: vertical spacing of a nonstaff line below the system, lilypond, 01:08
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 00:39
  • Re: Issue 2107 in lilypond: new patch for lilypond-book on windows, lilypond, 00:35
  • Re: Issue 2106 in lilypond: Patch: Build fixes for translated manuals: dependencies and a typo, lilypond, 00:31
  • Re: Feature request: multiplication should work on notes, chords and all rests, Keith OHara, 00:22
  • Re: Issue 2102 in lilypond: vertical spacing of a nonstaff line below the system, lilypond, 00:21
  • Re: Issue 2102 in lilypond: vertical spacing of a nonstaff line below the system, lilypond, 00:10
• December 15, 2011
  • Re: Issue 2102 in lilypond: vertical spacing of a nonstaff line below the system, lilypond, 22:56
  • Re: Issue 1377 in lilypond: Enhancement: make the last-page spacing more consistent and less tight, lilypond, 22:49
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 22:45
  • Re: Issue 2065 in lilypond: Scripts in cross-staff constructions can collide with span bars, lilypond, 22:41
  • Re: Issue 2101 in lilypond: Doc: NR Added glissando grob skip snippet to 1.3.3, lilypond, 22:37
  • Re: Feature request: multiplication should work on notes, chords and all rests, Pavel Roskin, 22:23
  • Re: Issue 1798 in lilypond: Full measure rests take too little horizontal space compared to notes, lilypond, 20:40
  • Re: Issue 2110 in lilypond: Improved example showing use of whiteout and layer properties for ties avoiding collision with staff objects, lilypond, 19:41
  • Issue 2110 in lilypond: Improved example showing use of whiteout and layer properties for ties avoiding collision with staff objects, lilypond, 19:28
  • Re: Issue 2076 in lilypond: Doc: improve NR 1.6.3 Instrument names (better to use \with ), lilypond, 19:07
  • Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved., lilypond, 18:09
  • Re: Feature request: multiplication should work on notes, chords and all rests, Xavier Scheuer, 17:57
  • Re: Issue 2103 in lilypond: Patch: Output a newline by default at the end of progress messages., lilypond, 17:08
  • Feature request: multiplication should work on notes, chords and all rests, Pavel Roskin, 16:58
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 16:57
  • Re: Issue 2103 in lilypond: Patch: Output a newline by default at the end of progress messages., lilypond, 16:53
  • Re: Issue 2098 in lilypond: Patch: Now use astyle 2.02.1, lilypond, 16:48
  • Re: Issue 2109 in lilypond: do not tinker with the position of a pitched rest, lilypond, 16:44
  • Re: Issue 2108 in lilypond: Patch: Implements avoidance of cross-staff-stem vs. articulation collisions., lilypond, 16:34
  • Issue 2109 in lilypond: do not tinker with the position of a pitched rest, lilypond, 15:56
  • Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to "programming error" messages, lilypond, 14:34
  • Issue 2108 in lilypond: Patch: Implements avoidance of cross-staff-stem vs. articulation collisions., lilypond, 11:16
  • Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to "programming error" messages, lilypond, 10:22
  • Re: Issue 2013 in lilypond: clang error flower/file-name.cc, lilypond, 10:20
  • Re: Issue 2013 in lilypond: clang error flower/file-name.cc, lilypond, 10:15
  • Re: Issue 2012 in lilypond: clang warning flower/file-cookie.cc, lilypond, 10:10
  • Re: Issue 2012 in lilypond: clang warning flower/file-cookie.cc, lilypond, 10:07
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 09:05
  • Re: Issue 409 in lilypond: Using whiteout and layer properties for ties avoiding collision with staff objects, lilypond, 08:35
  • Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved., lilypond, 08:01
  • Re: Issue 409 in lilypond: Using whiteout and layer properties for ties avoiding collision with staff objects, lilypond, 07:40
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 04:51
  • Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved., lilypond, 04:46
  • Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved., lilypond, 04:43
  • Re: Issue 1216 in lilypond: DynamicTextSpanners should end like hairpins, lilypond, 04:39
  • Re: Issue 1798 in lilypond: Full measure rests take too little horizontal space compared to notes, lilypond, 04:05
• December 14, 2011
  • Re: Issue 1506 in lilypond: \tempo after StopStaff/StartStaff forces extension of staff symbol, lilypond, 23:33
  • Re: Issue 1216 in lilypond: DynamicTextSpanners should end like hairpins, lilypond, 22:39
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 19:58
  • Re: Issue 409 in lilypond: Using whiteout and layer properties for ties avoiding collision with staff objects, lilypond, 19:22
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 18:17
  • Re: Issue 2102 in lilypond: vertical spacing of a nonstaff line below the system, lilypond, 18:08
  • Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved., lilypond, 17:40
  • Re: Issue 1272 in lilypond: remove old /web/, lilypond, 17:36
  • Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to "programming error" messages, lilypond, 16:47
  • Re: Issue 1935 in lilypond: Doc: internal ledger lines need to be documented in NR, lilypond, 16:12
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 14:12
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 11:07
  • Re: Issue 2107 in lilypond: new patch for lilypond-book on windows, lilypond, 11:03
  • Re: Issue 2107 in lilypond: new patch for lilypond-book on windows, lilypond, 10:59
  • Re: Issue 2103 in lilypond: Patch: Output a newline by default at the end of progress messages., lilypond, 10:55
  • Re: Issue 1815 in lilypond: lilypond-book fails on Windows, lilypond, 10:51
  • Issue 2107 in lilypond: new patch for lilypond-book on windows, lilypond, 10:47
  • Re: Issue 1815 in lilypond: lilypond-book fails on Windows, lilypond, 10:43
  • Re: Issue 1815 in lilypond: lilypond-book fails on Windows, lilypond, 10:39
  • Re: Issue 2103 in lilypond: Patch: Output a newline by default at the end of progress messages., lilypond, 10:35
  • issues to verify, Graham Percival, 10:34
  • Re: Issue 1815 in lilypond: lilypond-book fails on Windows, lilypond, 10:31
  • Re: Issue 1815 in lilypond: lilypond-book fails on Windows, lilypond, 10:27
  • Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved., lilypond, 10:23
  • Re: Issue 2103 in lilypond: Patch: Output a newline by default at the end of progress messages., lilypond, 10:19
  • Re: Issue 2103 in lilypond: Patch: Output a newline by default at the end of progress messages., lilypond, 10:15
  • Re: Issue 2103 in lilypond: Patch: Output a newline by default at the end of progress messages., lilypond, 10:11
  • Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved., lilypond, 10:07
  • Re: Issue 2105 in lilypond: Patch: Remove warning and .aux file left over by lilypond-book., lilypond, 10:03
  • Re: Issue 2106 in lilypond: Patch: Build fixes for translated manuals: dependencies and a typo, lilypond, 09:59
  • Re: Issue 2105 in lilypond: Patch: Don't blindly issue the warning, lilypond, 09:55
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 09:51
  • Re: Issue 2105 in lilypond: Patch: Don't blindly issue the warning, lilypond, 09:25
  • Re: Issue 2106 in lilypond: Patch: Build fixes for translated manuals: dependencies and a typo, lilypond, 09:21
  • Issue 2106 in lilypond: Patch: Build fixes for translated manuals: dependencies and a typo, lilypond, 09:17
  • Issue 2105 in lilypond: Patch: Don't blindly issue the warning, lilypond, 09:13
  • Re: Issue 1815 in lilypond: lilypond-book fails on Windows, lilypond, 08:54
  • Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved., lilypond, 08:50
  • Issue 2103 in lilypond: Patch: Output a newline by default at the end of progress messages., lilypond, 08:46
  • Re: Issue 2087 in lilypond: Patch: Fixes various warnings from clang++, lilypond, 04:55
  • Re: Issue 1005 in lilypond: syntax highlighting in the docs, lilypond, 03:53
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 03:25
  • Re: Issue 409 in lilypond: Using whiteout and layer properties for ties avoiding collision with staff objects, lilypond, 02:29
  • Re: Issue 1935 in lilypond: Doc: internal ledger lines need to be documented in NR, lilypond, 02:25
• December 13, 2011
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 22:11
  • Re: Issue 409 in lilypond: Using whiteout and layer properties for ties avoiding collision with staff objects, lilypond, 22:07
  • Re: Issue 1798 in lilypond: Full measure rests take too little horizontal space compared to notes, lilypond, 22:03
  • Re: Issue 1935 in lilypond: Doc: internal ledger lines need to be documented in NR, lilypond, 21:59
  • Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc, lilypond, 21:55
  • Re: Issue 2087 in lilypond: Patch: Fixes various warnings from clang++, lilypond, 21:51
  • Re: Issue 2096 in lilypond: Patch: Implements cross-staff stem avoidance for dynamics., lilypond, 21:47
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 09:04
  • Re: Issue 2102 in lilypond: vertical spacing of a nonstaff line below the system, lilypond, 05:19
  • Re: Issue 2101 in lilypond: Doc: NR Added glissando grob skip snippet to 1.3.3, lilypond, 05:15
  • Re: Issue 1377 in lilypond: Enhancement: make the last-page spacing more consistent and less tight, lilypond, 05:11
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 03:31
  • Re: Issue 1154 in lilypond: Slur and Tie subproperties for 'details should be documented, lilypond, 03:12
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 01:05
  • Re: Issue 1377 in lilypond: Enhancement: make the last-page spacing more consistent and less tight, lilypond, 01:00
  • Re: Issue 2102 in lilypond: vertical spacing of a nonstaff line below the system, lilypond, 00:23
• December 12, 2011
  • Re: Last dynamics line doesn't stick to the above staff group, Pavel Roskin, 23:40
  • Re: Last dynamics line doesn't stick to the above staff group, Keith OHara, 20:19
  • Issue 2102 in lilypond: vertical spacing of a nonstaff line below the system, lilypond, 19:57
  • Re: Last dynamics line doesn't stick to the above staff group, Keith OHara, 19:43
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 18:19
  • Issue 2101 in lilypond: Doc: NR Added glissando grob skip snippet to 1.3.3, lilypond, 16:27
  • Re: Issue 1154 in lilypond: Slur and Tie subproperties for 'details should be documented, lilypond, 15:49
  • Re: Issue 2076 in lilypond: Doc: improve NR 1.6.3 Instrument names (better to use \with ), lilypond, 15:39
  • Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly, lilypond, 15:19
  • Re: Last dynamics line doesn't stick to the above staff group, Pavel Roskin, 14:39
  • Last dynamics line doesn't stick to the above staff group, Pavel Roskin, 14:35
  • Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly, lilypond, 09:38
  • Re: Issue 2065 in lilypond: Scripts in cross-staff constructions can collide with span bars, lilypond, 08:37
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 08:33
  • Re: Issue 2098 in lilypond: Patch: Now use astyle 2.02.1, lilypond, 08:29
  • Re: Issue 2072 in lilypond: Add proper complex variables to Lilypond, lilypond, 08:04
  • Re: no barlines in pdf output, Xavier Scheuer, 07:30
  • Re: no barlines in pdf output, James, 07:16
  • no barlines in pdf output, renato, 07:00
  • Re: Issue 2094 in lilypond: spacing-measure-length.ly regtest has time sig overlaying rest, lilypond, 05:59
  • Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 04:20
  • Issue 2099 in lilypond: texi2pdf --quiet hides too much, lilypond, 04:16
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 03:45
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 03:31
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 03:20
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 03:11
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 03:06
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 03:03
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 02:58
  • Re: Issue 2098 in lilypond: Patch: Now use astyle 2.02.1, lilypond, 02:54
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 02:50
  • Re: Issue 2064 in lilypond: Patch: Prevents Slur vs Dots collisions., lilypond, 02:45
  • Issue 2098 in lilypond: Patch: Now use astyle 2.02.1, lilypond, 02:30
  • Re: Issue 1686 in lilypond: Compile scheme files to scm/out when using Guile V2.n. Also load and run .go files if available, lilypond, 02:12
  • Re: Issue 1826 in lilypond: Guile 2.0 compat: `conditional-circle-markup' definition needs to be relocated, lilypond, 02:08
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 02:03
• December 11, 2011
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 23:47
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 23:43
  • Re: Issue 2080 in lilypond: Request for better cross referencing of ornaments, lilypond, 23:39
  • Re: Issue 2076 in lilypond: Doc: improve NR 1.6.3 Instrument names (better to use \with ), lilypond, 23:35
  • Re: Issue 2064 in lilypond: Patch: Prevents Slur vs Dots collisions., lilypond, 23:31
  • Re: Issue 2059 in lilypond: Bar numbering of alternatives, lilypond, 23:27
  • Re: Issue 2077 in lilypond: Patch: Provide Scheme sandbox., lilypond, 18:37
  • Re: Issue 2081 in lilypond: Patch: Remove spurious spaces from music expression display, adapt tests., lilypond, 18:31
  • Re: Issue 694 in lilypond: Enhancement: easier use of microtone accidentals, lilypond, 14:50
  • Re: Issue 2065 in lilypond: Scripts in cross-staff constructions can collide with span bars, lilypond, 13:59
  • Re: Issue 2065 in lilypond: Scripts in cross-staff constructions can collide with span bars, lilypond, 13:46
  • Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 12:37
  • Re: Issue 257 in lilypond: collision accent and tuplet bracket, lilypond, 12:33
  • Re: Issue 2065 in lilypond: Scripts in cross-staff constructions can collide with span bars, lilypond, 10:53
  • Re: Set global staff size as command line option, Xavier Scheuer, 10:24
  • Re: Issue 1774 in lilypond: Semi-breves unnecessarily shifted, lilypond, 10:10
  • Re: metronome markings, Phil Holmes, 07:20
  • Re: Issue 2065 in lilypond: Scripts in cross-staff constructions can collide with span bars, lilypond, 07:16
  • Re: Where to put user ly files on OSX?, Phil Holmes, 07:15
  • Issue 2097 in lilypond: Provide lily-include directory, lilypond, 07:12
  • Re: $LILYHOME as $TEXMFHOME with LaTeX, Phil Holmes, 07:10
  • Re: Issue 2048 in lilypond: shiftDurations with negative 2nd argument loops indefinitely, lilypond, 07:08
  • Re: loglevel=ERROR still emits Warning message, Ian Hulin, 07:06
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 07:03
  • Re: Issue 2061 in lilypond: Lyrics collide with bar lines, lilypond, 06:57
  • Re: loglevel=ERROR still emits Warning message, Phil Holmes, 06:53
  • Re: Issue 2065 in lilypond: Scripts in cross-staff constructions can collide with span bars, lilypond, 06:38
  • Re: Issue 2096 in lilypond: Patch: Implements cross-staff stem avoidance for dynamics., lilypond, 06:25
  • loglevel=ERROR still emits Warning message, -Eluze, 06:24
  • Re: Issue 2071 in lilypond: Collision of hyphen and barline, lilypond, 06:08
  • Re: Issue 2096 in lilypond: Patch: Implements cross-staff stem avoidance for dynamics., lilypond, 04:51
  • Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to "programming error" messages, lilypond, 01:26
• December 10, 2011
  • Issue 2096 in lilypond: Patch: Implements cross-staff stem avoidance for dynamics., lilypond, 22:17
  • Re: Issue 2061 in lilypond: Lyrics collide with bar lines, lilypond, 20:15
  • Re: Set global staff size as command line option, Colin Hall, 19:23
  • Issue 2095 in lilypond: Set global staff size as command line option, lilypond, 19:22
  • Re: Issue 2094 in lilypond: spacing-measure-length.ly regtest has time sig overlaying rest, lilypond, 14:55
  • Re: Issue 1935 in lilypond: Doc: internal ledger lines need to be documented in NR, lilypond, 11:30
  • Issue 2094 in lilypond: spacing-measure-length.ly regtest has time sig overlaying rest, lilypond, 11:06
  • Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments., lilypond, 10:09
  • Re: Issue 2072 in lilypond: Add proper complex variables to Lilypond, Werner LEMBERG, 08:40
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 07:34
  • Re: Issue 2072 in lilypond: Add proper complex variables to Lilypond, David Kastrup, 07:28
  • Re: Set global staff size as command line option, Colin Hall, 07:19
  • Re: Issue 2072 in lilypond: Add proper complex variables to Lilypond, Ian Hulin, 07:12
  • Re: Issue 2068 in lilypond: Patch: Doc: CG: add instructions for staging branch, lilypond, 06:57
  • Re: Issue 2059 in lilypond: Bar numbering of alternatives, lilypond, 06:53
  • Re: Doc: alternativeNumberingStyle (fix issue 2059) should be documented, Colin Hall, 06:50
  • Issue 2093 in lilypond: Doc: alternativeNumberingStyle (fix issue 2059) should be documented, lilypond, 06:49
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 06:11
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 06:05
  • Re: Issue 2084 in lilypond: script-accidental avoidance fails for articulations, lilypond, 05:52
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 05:44
  • Re: Issue 1798 in lilypond: Full measure rests take too little horizontal space compared to notes, lilypond, 05:40
  • Re: Issue 2084 in lilypond: script-accidental avoidance fails for articulations, lilypond, 05:36
  • $LILYHOME as $TEXMFHOME with LaTeX, Xavier Scheuer, 05:28
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 05:23
  • Re: Issue 1377 in lilypond: Enhancement: make the last-page spacing more consistent and less tight, lilypond, 05:04
  • Re: Issue 1935 in lilypond: Doc: internal ledger lines need to be documented in NR, lilypond, 04:46
  • Re: Issue 409 in lilypond: Using whiteout and layer properties for ties avoiding collision with staff objects, lilypond, 03:55
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 03:28
  • Re: Issue 2090 in lilypond: Add documentation for command line quoting on Windows, lilypond, 03:14
  • Re: Issue 1798 in lilypond: Full measure rests take too little horizontal space compared to notes, lilypond, 03:08
• December 09, 2011
  • Re: Issue 2068 in lilypond: Patch: Doc: CG: add instructions for staging branch, lilypond, 23:48
  • Re: Issue 2068 in lilypond: Patch: Doc: CG: add instructions for staging branch, lilypond, 21:56
  • Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc, lilypond, 21:52
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 21:48
  • Re: Issue 1798 in lilypond: Full measure rests take too little horizontal space compared to notes, lilypond, 21:44
  • Re: Issue 1798 in lilypond: Full measure rests take too little horizontal space compared to notes, lilypond, 19:14
  • Re: Issue 1228 in lilypond: \override RestCollision #'positioning-done = #merge-rests-on-positioning, lilypond, 18:42
  • Issue 1377 should be pushed now?, Xavier Scheuer, 18:25
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 18:15
  • Doc: alternativeNumberingStyle (fix issue 2059) should be documented, Xavier Scheuer, 17:46
  • Re: Set global staff size as command line option, Xavier Scheuer, 17:36
  • Re: Issue 2090 in lilypond: Add documentation for command line quoting on Windows, Eluze, 17:01
  • Re: Issue 2088 in lilypond: pointer confusion with clang++, lilypond, 14:35
  • Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc, lilypond, 10:50
  • Re: Issue 1964 in lilypond: lilydev 2.0, lilypond, 09:41
  • Re: Issue 2088 in lilypond: pointer confusion with clang++, lilypond, 09:24
  • Re: Issue 2068 in lilypond: Patch: Doc: CG: add instructions for staging branch, lilypond, 09:20
  • Re: Issue 2072 in lilypond: Add proper complex variables to Lilypond, lilypond, 07:56
  • Re: Issue 2069 in lilypond: Patch: More nuanced BarLine extra-spacing-height to allow tighter horizontal spacing, lilypond, 07:52
  • Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 07:35
  • Re: Fwd: bug or feature with the extent of NoteColumn with "2.15.20" ?, Colin Hall, 05:30
  • Issue 2091 in lilypond: bug or feature with the extent of NoteColumn with 2.15.20, lilypond, 05:28
  • Re: Issue 2089 in lilypond: dangerous redefinition of SCM s / Moment s, lilypond, 05:13
  • Re: Fwd: bug or feature with the extent of NoteColumn with "2.15.20" ?, Graham Percival, 05:11
  • Fwd: bug or feature with the extent of NoteColumn with "2.15.20" ?, Colin Hall, 05:07
  • Re: bug or feature with the extent of NoteColumn with "2.15.20" ?, Colin Hall, 04:53
  • Re: Set global staff size as command line option, Colin Hall, 04:28
  • Re: Issue 1964 in lilypond: lilydev 2.0, lilypond, 04:27
  • Issue 2090 in lilypond: Add documentation for command line quoting on Windows, lilypond, 04:23
  • Re: Issue 2089 in lilypond: dangerous redefinition of SCM s / Moment s, lilypond, 04:13
  • Re: Issue 2036 in lilypond: make test in flower subdirectory produces lots of warnings with g++ 4.6, lilypond, 03:52
  • Re: Issue 2089 in lilypond: dangerous redefinition of SCM s / Moment s, lilypond, 03:24
  • Re: Issue 1964 in lilypond: lilydev 2.0, lilypond, 03:20
  • Re: Issue 1964 in lilypond: lilydev 2.0, lilypond, 03:16
  • Re: Issue 2077 in lilypond: Patch: Provide Scheme sandbox., lilypond, 03:10
  • Re: Issue 2087 in lilypond: Patch: Fixes various warnings from clang++, lilypond, 03:04
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 03:00
  • Issue 2089 in lilypond: dangerous redefinition of SCM s / Moment s, lilypond, 02:42
  • Re: Issue 460 in lilypond: bar numbers for broken bars, address@hidden, 02:33
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 02:31
  • Re: Issue 1964 in lilypond: lilydev 2.0, lilypond, 01:30
  • Issue 2088 in lilypond: pointer confusion with clang++, lilypond, 01:02
  • Issue 2087 in lilypond: Patch: Fixes various warnings from clang++, lilypond, 00:58
  • Re: Issue 409 in lilypond: Using whiteout and layer properties for ties avoiding collision with staff objects, lilypond, 00:39
  • Re: Issue 2077 in lilypond: Patch: Provide Scheme sandbox., lilypond, 00:35
• December 08, 2011
  • Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc, lilypond, 22:04
  • Re: Unable to find file "lily.scm" in load path, Nick Payne, 14:38
  • Re: Issue 2084 in lilypond: script-accidental avoidance fails forarticulations, Phil Holmes, 13:09
  • Re: using quotes in command-line-commands under Windows, David Kastrup, 11:18
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 11:11
  • Re: using quotes in command-line-commands under Windows, Eluze, 11:05
  • Re: using quotes in command-line-commands under Windows, David Kastrup, 10:40
  • using quotes in command-line-commands under Windows, Eluze, 10:29
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 10:27
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 10:06
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 10:03
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 09:58
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 09:54
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 09:42
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 09:30
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 09:26
  • Issue 2086 in lilypond: generate gitstats automatically, lilypond, 09:05
  • Re: Issue 2027 in lilypond: make website doesn't have dependencies, lilypond, 08:57
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 08:45
  • Re: Set global staff size as command line option, James, 06:32
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 06:06
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 06:01
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 05:56
  • Re: Set global staff size as command line option, Eluze, 05:51
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 05:44
  • Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly, lilypond, 05:40
  • Re: Issue 1809 in lilypond: make test segfaults, lilypond, 05:36
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 05:32
  • Re: Issue 39 in lilypond: collision flag notehead with polyphony, lilypond, 05:28
  • Re: Issue 139 in lilypond: tie misinterpreted as a slur, lilypond, 05:24
  • Re: Issue 992 in lilypond: Tuplets collide with notes outside the staff, lilypond, 05:20
  • Re: Issue 1004 in lilypond: more thought needed for website integration, lilypond, 05:16
  • Re: Issue 1055 in lilypond: guile 2.0, lilypond, 05:12
  • Re: Issue 1134 in lilypond: Notes in different voices do not treat accidentals properly, lilypond, 05:08
  • Re: Issue 1183 in lilypond: @rcontrib{} from topdocs doesn't work, lilypond, 05:04
  • Re: Issue 1208 in lilypond: Some combination of 'staff-affinity for two Lyrics may cause unwanted vertical space, lilypond, 05:00
  • Re: Issue 1388 in lilypond: Support OpenType font features, lilypond, 04:56
  • Re: Issue 1505 in lilypond: bendAfter not spanning line break properly, lilypond, 04:52
  • Re: Issue 1566 in lilypond: Flagged notes lose flags with autobeaming and hidenotes, lilypond, 04:48
  • Re: Issue 1645 in lilypond: Beam_collision_engraver sometimes fails on demisemiquavers or shorter notes, lilypond, 04:44
  • Re: Issue 1662 in lilypond: midi & pdf disagree with conflicting tempo-changes, lilypond, 04:40
  • Re: Issue 1686 in lilypond: Compile scheme files to scm/out when using Guile V2.n. Also load and run .go files if available, lilypond, 04:36
  • Re: Issue 1713 in lilypond: Whole note/dotted note collision in polyphony, lilypond, 04:32
  • Re: Issue 1718 in lilypond: Slur collides with stems, lilypond, 04:28
  • Re: Issue 1731 in lilypond: LilyPond fails to install on Puppy Linux, lilypond, 04:24
  • Re: Issue 1806 in lilypond: Wrong search for translated docs, lilypond, 04:20
  • Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly, lilypond, 04:16
  • Re: Issue 1809 in lilypond: make test segfaults, lilypond, 04:12
  • Re: Unable to find file "lily.scm" in load path, David Kastrup, 03:50
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 03:49
  • Re: Issue 694 in lilypond: Enhancement: easier use of microtone accidentals, lilypond, 03:45
  • Re: Issue 2084 in lilypond: script-accidental avoidance fails for articulations, lilypond, 03:34
  • Re: Issue 409 in lilypond: Using whiteout and layer properties for ties avoiding collision with staff objects, lilypond, 03:30
  • Re: Issue 2076 in lilypond: Doc: improve NR 1.6.3 Instrument names (better to use \with ), lilypond, 03:21
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 03:13
  • Re: Unable to find file "lily.scm" in load path, Nick Payne, 03:01
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 02:52
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 02:25
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 02:21
  • Re: Unable to find file "lily.scm" in load path, David Kastrup, 02:10
• December 07, 2011
  • Re: Unable to find file "lily.scm" in load path, Nick Payne, 23:56
  • Issue 2085 in lilypond: Overriding stencil of StringNumber leads to "programming error" messages, lilypond, 21:23
  • Issue 2084 in lilypond: script-accidental avoidance fails for articulations, lilypond, 21:19
  • Re: Issue 2076 in lilypond: Doc: improve NR 1.6.3 Instrument names (better to use \with ), lilypond, 20:49
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 20:45
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 20:10
  • Unable to find file "lily.scm" in load path, Nick Payne, 20:07
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 19:26
  • bug or feature with the extent of NoteColumn with "2.15.20" ?, Thomas Morley, 18:54
  • Re: Issue 2059 in lilypond: Bar numbering of alternatives, Carl Sorensen, 17:44
  • Re: DOC NR 1.6.3 - quoting other voices (german doc), Werner, 16:58
  • Re: Set global staff size as command line option, Francisco Vila, 12:20
  • Re: Set global staff size as command line option, Francisco Vila, 12:18
  • Re: Set global staff size as command line option, Francisco Vila, 12:16
  • Re: Where to put user ly files on OSX?, Xavier Scheuer, 10:11
  • Set global staff size as command line option, Xavier Scheuer, 09:02
  • Re: Issue 2083 in lilypond: \break in alternative causes score to split, lilypond, 07:10
  • Re: Issue 2083 in lilypond: \\break in alternative causes score to split, address@hidden, 07:09
  • Re: Issue 2083 in lilypond: \\break in alternative causes score to split, Eluze, 07:07
  • Re: DOC NR 1.6.3 - quoting other voices (german doc) and formatiing cue notes (english), Werner, 06:28
  • Re: DOC NR 1.6.3 - quoting other voices (german doc) and formatiing cue notes (english), Werner, 06:18
  • Re: Issue 2069 in lilypond: Patch: More nuanced BarLine extra-spacing-height to allow tighter horizontal spacing, lilypond, 06:02
  • Overriding stencil of StringNumber leads to "programming error" messages, David Kastrup, 05:58
  • script-accidental avoidance fails for articulations, David Kastrup, 05:11
  • Re: Issue 2076 in lilypond: Doc: improve NR 1.6.3 Instrument names (better to use \with ), lilypond, 04:20
  • Re: Issue 2083 in lilypond: \break in alternative causes score to split, lilypond, 04:09
  • Re: Issue 2083 in lilypond: \break in alternative causes score to split, lilypond, 03:53
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 03:30
  • Re: Issue 2037 in lilypond: Patch: Bring argument processing of chord music functions in line with the rest, lilypond, 03:26
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 02:57
  • Re: Issue 2073 in lilypond: Patch: Allows for framing comments in LilyPond backends., lilypond, 02:48
  • Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments., lilypond, 01:42
  • Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments., lilypond, 01:31
  • Re: Issue 2080 in lilypond: Request for better cross referencing of ornaments, lilypond, 01:27
  • Re: Issue 409 in lilypond: Using whiteout and layer properties for ties avoiding collision with staff objects, lilypond, 01:23
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 01:19
• December 06, 2011
  • Re: Issue 2069 in lilypond: Patch: More nuanced BarLine extra-spacing-height to allow tighter horizontal spacing, lilypond, 23:34
  • Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments., lilypond, 23:30
  • Issue 2083 in lilypond: \break in alternative causes score to split, lilypond, 17:36
  • Re: Issue 2036 in lilypond: make test in flower subdirectory produces lots of warnings with g++ 4.6, lilypond, 17:32
  • Re: Issue 2059 in lilypond: Bar numbering of alternatives, lilypond, 17:26
  • Re: Issue 2076 in lilypond: Doc: improve NR 1.6.3 Instrument names (better to use \with ), lilypond, 17:18
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 17:14
  • Re: DOC 1.6.3 - german - quoting other voices, Brett McCoy, 17:13
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 17:06
  • Re: Issue 2076 in lilypond: Doc: improve NR 1.6.3 Instrument names (better to use \with ), lilypond, 16:13
  • Re: Issue 409 in lilypond: Using whiteout and layer properties for ties avoiding collision with staff objects, lilypond, 15:59
  • Re: Issue 1874 in lilypond: some stems are no longer transparent in the docs, lilypond, 15:37
  • Re: Issue 1269 in lilypond: Doc: using #'non-break-align-symbols = #'() to align MetronomeMark should be documented, lilypond, 15:33
  • Re: Issue 1874 in lilypond: some stems are no longer transparent in the docs, lilypond, 15:29
  • Re: Issue 2080 in lilypond: Request for better cross referencing of ornaments, lilypond, 15:25
  • Re: Issue 2076 in lilypond: Doc: improve NR 1.6.3 Instrument names (better to use \with ), lilypond, 15:09
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 13:46
  • DOC 1.6.3 ‒ german ‒ quoting other voices, Werner, 12:48
  • Re: Issue 1875 in lilypond: tests for flower appear to miss instantiations of classes, lilypond, 12:30
  • Re: Issue 2076 in lilypond: Doc: improve NR 1.6.3 Instrument names (better to use \with ), lilypond, 09:21
  • Re: Issue 2076 in lilypond: Doc: improve NR 1.6.3 Instrument names (better to use \with ), lilypond, 09:01
  • Re: Issue 2040 in lilypond: Documentation for unpure-pure-containers, lilypond, 07:29
  • Re: Issue 460 in lilypond: bar numbers for broken bars, lilypond, 06:57
  • Re: Issue 2081 in lilypond: Patch: Remove spurious spaces from music expression display, adapt tests., lilypond, 05:53
  • Re: Issue 2076 in lilypond: Doc: improve NR 1.6.3 Instrument names (better to use \with ), lilypond, 05:47
  • Re: Issue 2076 in lilypond: Doc: improve NR 1.6.3 Instrument names (better to use \with ), lilypond, 05:12
  • Re: Issue 2082 in lilypond: patchy should check for guile memory leaks, lilypond, 04:18
  • Re: Issue 2082 in lilypond: patchy should check for guile memory leaks, David Kastrup, 04:10
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 03:10
  • Re: Issue 2082 in lilypond: patchy should check for guile memory leaks, lilypond, 02:15
• December 05, 2011
  • Re: Issue 2082 in lilypond: patchy should check for guile memory leaks, lilypond, 21:12
  • Re: Issue 2081 in lilypond: Patch: Remove spurious spaces from music expression display, adapt tests., lilypond, 21:08
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 20:24
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 20:20
  • Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc, lilypond, 20:16
  • Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments., Graham Percival, 19:54
  • Issue 2082 in lilypond: patchy should check for guile memory leaks, lilypond, 19:54
  • Re: Issue 694 in lilypond: Enhancement: easier use of microtone accidentals, lilypond, 19:26
  • Issue 2081 in lilypond: Patch: Remove spurious spaces from music expression display, adapt tests., lilypond, 19:08
  • Re: Issue 1890 in lilypond: Compiler warnings in make on 64-bit systems, lilypond, 18:52
  • Re: adding a cross-reference to the music glossary, Ralph Palmer, 18:48
  • Issue 2080 in lilypond: Request for better cross referencing of ornaments, lilypond, 18:48
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 15:13
  • Re: Issue 2079 in lilypond: website links to 2.13, lilypond, 13:27
  • Re: Issue 2079 in lilypond: website links to 2.13, Jean-Charles Malahieude, 12:28
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 10:01
  • Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc, lilypond, 09:38
  • Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc, lilypond, 09:34
  • Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments., David Kastrup, 08:05
  • Issue 2079 in lilypond: website links to 2.13, lilypond, 06:44
  • Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc, lilypond, 06:40
  • Re: Issue 1506 in lilypond: \tempo after StopStaff/StartStaff forces extension of staff symbol, lilypond, 06:36
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 06:32
  • Re: Issue 1890 in lilypond: Compiler warnings in make on 64-bit systems, lilypond, 06:28
  • Re: Issue 2077 in lilypond: Patch: Provide Scheme sandbox., lilypond, 06:17
  • Issue 2078 in lilypond: always-changing regtest: graphviz.log, lilypond, 06:13
  • Re: Issue 2058 in lilypond: horizontal spacing allows space for neighboring staves in surprising ways, lilypond, 05:39
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 05:35
  • Issue 2077 in lilypond: Patch: Provide Scheme sandbox., lilypond, 05:16
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 04:28
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 02:54
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, David Kastrup, 02:54
  • Re: Issue 2066 in lilypond: Patch: Prevents accidentals from hanging over barlines., lilypond, 02:50
  • Re: Issue 2058 in lilypond: horizontal spacing allows space for neighboring staves in surprising ways, lilypond, 02:14
• December 04, 2011
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 23:56
  • Re: Issue 1875 in lilypond: tests for flower appear to miss instantiations of classes, lilypond, 23:52
  • Re: Issue 2059 in lilypond: Bar numbering of alternatives, lilypond, 23:48
  • Re: Issue 2060 in lilypond: Patch: Hairpin missing padding at line break, lilypond, 23:44
  • Re: Issue 2064 in lilypond: Patch: Prevents Slur vs Dots collisions., lilypond, 23:40
  • Re: Issue 2066 in lilypond: Patch: Prevents accidentals from hanging over barlines., lilypond, 23:36
  • Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments., lilypond, 20:35
  • Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments., lilypond, 20:11
  • Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments., lilypond, 20:08
  • Re: Issue 2036 in lilypond: make test in flower subdirectory produces lots of warnings with g++ 4.6, lilypond, 20:02
  • Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments., lilypond, 19:21
  • Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments., lilypond, 19:03
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, Valentin Villenave, 18:35
  • Re: Issue 2036 in lilypond: make test in flower subdirectory produces lots of warnings with g++ 4.6, lilypond, 14:07
  • Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments., lilypond, 13:46
  • Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc, lilypond, 13:18
  • metronome markings, Gerard van Reenen, 13:15
  • Issue 2076 in lilypond: Doc: improve NR 1.6.3 Instrument names (better to use \with ), lilypond, 11:35
  • Re: Doc: improve NR 1.6.3 Instrument names (better to use \with ), Colin Campbell, 11:32
  • Re: Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc, lilypond, 11:31
  • Issue 2075 in lilypond: Implement GOP 9 - behavior of make doc, lilypond, 11:08
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, David Kastrup, 11:06
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, David Kastrup, 10:05
  • Re: installer lilypond, Alice Tacaille, 09:26
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, David Kastrup, 09:07
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, Valentin Villenave, 08:51
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, David Kastrup, 07:20
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, Valentin Villenave, 06:53
  • Re: Issue 2072 in lilypond: Add proper complex variables to Lilypond, David Kastrup, 06:34
  • Re: Issue 2073 in lilypond: Patch: Allows for framing comments in LilyPond backends., lilypond, 06:29
  • Issue 2074 in lilypond: Add crossreferences to NR Appendix C "Lilypond Grammar", lilypond, 06:22
  • Re: Issue 2072 in lilypond: Add proper complex variables to Lilypond, Werner LEMBERG, 06:20
  • Re: Issue 2072 in lilypond: Add proper complex variables to Lilypond, David Kastrup, 05:35
  • Re: Issue 2072 in lilypond: Add proper complex variables to Lilypond, Werner LEMBERG, 05:23
  • Re: Issue 2073 in lilypond: Patch: Allows for framing comments in LilyPond backends., lilypond, 05:17
  • Issue 2073 in lilypond: Patch: Allows for framing comments in LilyPond backends., lilypond, 05:12
  • Doc: improve NR 1.6.3 Instrument names (better to use \with ), Xavier Scheuer, 04:37
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, David Kastrup, 04:01
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, David Kastrup, 03:45
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, David Kastrup, 03:38
  • Re: Issue 2072 in lilypond: Add proper complex variables to Lilypond, David Kastrup, 03:03
  • Re: Issue 2072 in lilypond: Add proper complex variables to Lilypond, Werner LEMBERG, 02:51
• December 03, 2011
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, Valentin Villenave, 19:06
  • Re: Issue 2068 in lilypond: Patch: Doc: CG: add instructions for staging branch, lilypond, 18:19
  • Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments., lilypond, 16:48
  • Re: Issue 2072 in lilypond: Add proper complex variables to Lilypond, lilypond, 16:43
  • Re: Issue 2072 in lilypond: Add proper complex variables to Lilypond, David Kastrup, 15:15
  • Re: Issue 2072 in lilypond: Add proper complex variables to Lilypond, Werner LEMBERG, 14:40
  • Re: Issue 2072 in lilypond: Add proper complex variables to Lilypond, Keith OHara, 14:29
  • Issue 2072 in lilypond: Add proper complex variables to Lilypond, lilypond, 12:21
  • Re: Issue 2069 in lilypond: Patch: More nuanced BarLine extra-spacing-height to allow tighter horizontal spacing, lilypond, 12:14
  • Re: (German) Documentation not precise, Phil Holmes, 08:35
  • Re: (German) Documentation flaw, David Kastrup, 07:29
  • (German) Documentation flaw, Mathias Weber, 06:03
  • Re: Issue 2069 in lilypond: Patch: More nuanced BarLine extra-spacing-height to allow tighter horizontal spacing, lilypond, 05:57
  • (German) Documentation not precise, Mathias Weber, 05:55
• December 02, 2011
  • Re: Issue 1700 in lilypond: Chord names collide when several note-columns lay in between, lilypond, 23:19
  • Re: Issue 2069 in lilypond: Patch: More nuanced BarLine extra-spacing-height to allow tighter horizontal spacing, lilypond, 20:26
  • Re: Issue 2069 in lilypond: Patch: More nuanced BarLine extra-spacing-height to allow tighter horizontal spacing, lilypond, 19:34
  • Re: Issue 2071 in lilypond: Collision of hyphen and barline, lilypond, 16:22
  • Re: installer lilypond, Pierre Perol-Schneider, 16:09
  • Re: Issue 1723 in lilypond: beam fails to extend over rest, intermittently, lilypond, 15:07
  • Re: Collision of hyphen and barline, Marek Klein, 14:32
  • Issue 2071 in lilypond: Collision of hyphen and barline, lilypond, 14:29
  • Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 12:58
  • Re: Issue 1567 in lilypond: Add documentation for footnotes, lilypond, 11:51
  • Re: Issue 2069 in lilypond: Patch: More nuanced BarLine extra-spacing-height to allow tighter horizontal spacing, lilypond, 10:45
  • Issue 2069 in lilypond: Patch: More nuanced BarLine extra-spacing-height to allow tighter horizontal spacing, lilypond, 08:44
  • Re: Issue 11 in lilypond: beamlet on wrong side of tuplet sixteenth, lilypond, 08:18
  • Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments., lilypond, 08:14
  • Re: Issue 1572 in lilypond: Change chord name separator and inversion separator, separately, lilypond, 08:10
  • Re: Issue 1838 in lilypond: Make accidental styles available as context mods, lilypond, 08:06
  • Re: Issue 2014 in lilypond: Patch: Improve HTML output of regression tests, lilypond, 08:01
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, David Kastrup, 07:59
  • Re: Issue 2051 in lilypond: Patch: Better pure heights for slurs, lilypond, 07:57
  • Re: Issue 2052 in lilypond: Patch: Asserts that footnotes are being numbered correctly., lilypond, 07:53
  • Re: Issue 2055 in lilypond: Patch: Make 2-argument form of \accidentalStyle, lilypond, 07:49
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, Valentin Villenave, 07:25
  • Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments., address@hidden, 06:42
  • installer lilypond, alice, 06:10
  • Issue 2068 in lilypond: Patch: Doc: CG: add instructions for staging branch, lilypond, 06:08
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, David Kastrup, 05:54
  • Re: Issue 2011 in lilypond: configure doesn't like clang++, lilypond, 05:02
  • Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments., lilypond, 04:41
  • Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments., lilypond, 04:33
  • Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments., lilypond, 04:25
  • Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments., lilypond, 04:18
  • Re: Issue 2066 in lilypond: Patch: Prevents accidentals from hanging over barlines., lilypond, 04:11
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 04:07
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, Valentin Villenave, 03:11
  • Re: Issue 2066 in lilypond: Patch: Prevents accidentals from hanging over barlines., lilypond, 03:10
  • Re: Issue 2066 in lilypond: Patch: Prevents accidentals from hanging over barlines., lilypond, 02:57
  • Re: Issue 1955 in lilypond: Patch: improving spacing over and below bar lines, lilypond, 02:53
  • Re: Issue 2066 in lilypond: Patch: Prevents accidentals from hanging over barlines., lilypond, 02:49
  • Re: Issue 2051 in lilypond: Patch: Better pure heights for slurs, lilypond, 02:35
  • Re: Issue 2052 in lilypond: Patch: Asserts that footnotes are being numbered correctly., lilypond, 02:31
  • Re: Issue 2063 in lilypond: Patch: Makes two functions in bezier-tools.scm public., lilypond, 02:27
  • Re: Issue 2061 in lilypond: Lyrics collide with bar lines, lilypond, 02:23
  • Re: Collision of hyphen and barline, address@hidden, 02:16
  • Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly, lilypond, 01:51
  • Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly, lilypond, 01:38
• December 01, 2011
  • Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly, lilypond, 22:40
  • Re: Issue 2011 in lilypond: configure doesn't like clang++, lilypond, 22:36
  • Re: Issue 1567 in lilypond: Add documentation for footnotes, lilypond, 22:32
  • Re: Issue 2051 in lilypond: Patch: Better pure heights for slurs, lilypond, 22:27
  • Re: Issue 2052 in lilypond: Patch: Asserts that footnotes are being numbered correctly., lilypond, 22:23
  • Re: Trouble uploading to Rietveld, Colin Hall, 19:12
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, David Kastrup, 19:06
  • Re: Issue 2053 in lilypond: Patch: prevent accidentals and articulations from moving over Clefs, TimeSignatures, and KeySignatures, lilypond, 18:45
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 17:38
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, Valentin Villenave, 16:22
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, Valentin Villenave, 15:57
  • Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments., lilypond, 14:28
  • Re: Issue 2066 in lilypond: Patch: Prevents accidentals from hanging over barlines., lilypond, 13:00
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 12:56
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 12:52
  • Re: Issue 2064 in lilypond: Patch: Prevents Slur vs Dots collisions., lilypond, 12:48
  • Re: Issue 2059 in lilypond: Bar numbering of alternatives, lilypond, 12:39
  • Re: Issue 2060 in lilypond: Patch: Hairpin missing padding at line break, lilypond, 12:31
  • Re: Collision of hyphen and barline, Phil Holmes, 12:21
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, David Kastrup, 06:58
  • Re: New read/eval Scheme syntax inconsistent in handling existing code, Valentin Villenave, 06:36
  • Re: Issue 1356 in lilypond: LilyPond-style comments embeddedinaScheme expression can't include special characters, Graham Percival, 04:31
  • Issue 2066 in lilypond: Patch: Prevents accidentals from hanging over barlines., lilypond, 03:27
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 02:30

---

[Prev Period]

[Next Period]

---

Mail converted by MHonArc