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: Tue Jan 31 2012 21:30:53 -0500 Messages in reverse chronological order

[Next Period]

---

• January 31, 2012
  • Re: Issue 2259 in lilypond: Hairpin still hits barline at line break, lilypond, 21:30
  • Re: Issue 2255 in lilypond: Doc: NR Add @warning for Margin adjustment', lilypond, 21:26
  • Re: Issue 2189 in lilypond: Doc: NR add to \partial for clearer understanding, lilypond, 21:22
  • Re: Issue 2179 in lilypond: Improve warnings about spanners/lyrics etc. cannot be set from 'outside' to 'inside' << {...} \\ {...} >> constructs, lilypond, 21:18
  • Re: Issue 2162 in lilypond: Patch: Doc: NR added @knownissue for beam properties, lilypond, 21:14
  • Re: Issue 2040 in lilypond: Documentation for unpure-pure-containers, lilypond, 21:10
  • Re: Feature request: cross-staff chords, Francisco Vila, 19:13
  • Re: Feature request: cross-staff chords, address@hidden, 15:27
  • Re: Feature request: cross-staff chords, Francisco Vila, 15:15
  • Re: 2.15.27 won't open on Mac 10.4 PPC, James Worlton, 13:28
  • Re: 2.15.27 won't open on Mac 10.4 PPC, Hans Aberg, 13:21
  • Re: 2.15.27 won't open on Mac 10.4 PPC, Carl Sorensen, 12:41
  • Re: Feature request: cross-staff chords, Pavel Roskin, 12:33
  • Re: 2.15.27 won't open on Mac 10.4 PPC, David Kastrup, 12:29
  • Re: Issue 2263 in lilypond: Reimplement chord repetition, lilypond, 12:17
  • Re: 2.15.27 won't open on Mac 10.4 PPC, Graham Percival, 12:14
  • Re: Issue 2251 in lilypond: website still doesn't auto-update, lilypond, 12:13
  • Re: Issue 2260 in lilypond: line-broken spanners start too far to the right, with \tempo and \time, lilypond, 12:09
  • Re: Feature request: cross-staff chords, Francisco Vila, 12:02
  • Re: Issue 2251 in lilypond: website still doesn't auto-update, lilypond, 12:02
  • Re: 2.15.27 won't open on Mac 10.4 PPC, Hans Aberg, 10:16
  • Re: If piece begins with \cueDuringWithClef, ambitus is shown in cue's clef, James, 10:14
  • Re: 2.15.27 won't open on Mac 10.4 PPC, David Kastrup, 09:56
  • Re: 2.15.27 won't open on Mac 10.4 PPC, James Worlton, 09:47
  • Re: If piece begins with \cueDuringWithClef, ambitus is shown in cue's clef, Ole V . Villumsen, 09:31
  • Re: If piece begins with \cueDuringWithClef, ambitus is shown in cue's clef, Ole V . Villumsen, 09:25
  • Re: Issue 2263 in lilypond: Reimplement chord repetition, lilypond, 09:24
  • If piece begins with \cueDuringWithClef, ambitus is shown in cue's clef, Ole V . Villumsen, 07:28
  • Re: 2.15.27 won't open on Mac 10.4 PPC, Hans Aberg, 03:55
  • Feature request: cross-staff chords, Pavel Roskin, 03:13
  • Unable to find file "ice-9/boot-9.scm" in load path, Helge Kruse, 02:04
• January 30, 2012
  • 2.15.27 won't open on Mac 10.4 PPC, James Worlton, 21:54
  • Re: Issue 2256 in lilypond: empty strings: tabStaff insists on stringnumbers and looses notes, lilypond, 20:18
  • Re: Issue 2266 in lilypond: @rlsrnamed{Name,Translation} translates also the name in the URI, lilypond, 17:37
  • Re: Issue 2265 in lilypond: problem with beam-shortened-length.ly, lilypond, 17:26
  • Re: Issue 1627 in lilypond: global-staff-size effects on grace notes (LilyPond 2.13.58), lilypond, 17:22
  • Re: Issue 1022 in lilypond: \chordmode neglects point-and-click, lilypond, 16:41
  • Re: @rlsrnamed{Name,Translation} translates also the name in the URI, James, 16:30
  • Issue 2266 in lilypond: @rlsrnamed{Name, Translation} translates also the name in the URI, lilypond, 16:28
  • Re: @rlsrnamed{Name,Translation} translates also the name in the URI, Ralph Palmer, 16:28
  • Issue 2265 in lilypond: problem with beam-shortened-length.ly, lilypond, 16:24
  • Re: a beaming regression?, Ralph Palmer, 16:22
  • Re: Issue 1022 in lilypond: \chordmode neglects point-and-click, lilypond, 16:20
  • Re: Issue 1022 in lilypond: \chordmode neglects point-and-click, lilypond, 16:16
  • Re: Issue 2263 in lilypond: Reimplement chord repetition, lilypond, 15:55
  • Re: exceeding processing time when processing multiple scores within onebook, Martin Straeten, 15:14
  • Re: exceeding processing time when processing multiple scores within onebook, Phil Holmes, 13:32
  • Re: I am a real person, -Eluze, 13:20
  • Re: exceeding processing time when processing multiple scores within onebook, Martin Straeten, 13:04
  • I am a real person, Julia Young, 12:25
  • Re: exceeding processing time when processing multiple scores within onebook, Phil Holmes, 10:29
  • Re: tuplets, David Kastrup, 08:37
  • Re: tuplets, Phil Holmes, 08:32
  • Re: Issue 2263 in lilypond: Reimplement chord repetition, lilypond, 08:25
  • exceeding processing time when processing multiple scores within one book, Martin Straeten, 08:12
  • Re: Issue 2178 in lilypond: NR: clarify the subsection "Automatic accidentals" of section 1.1.3, lilypond, 06:01
  • Re: Bug squad roll call, James, 05:51
  • Re: Issue 2178 in lilypond: NR: clarify the subsection "Automatic accidentals" of section 1.1.3, lilypond, 05:49
  • Re: Issue 2178 in lilypond: NR: clarify the subsection "Automatic accidentals" of section 1.1.3, lilypond, 05:42
  • Re: Issue 2263 in lilypond: Reimplement chord repetition, lilypond, 05:27
  • Re: Issue 2263 in lilypond: Reimplement chord repetition, lilypond, 04:13
  • Re: tuplets, David Kastrup, 02:17
  • Issue 2264 in lilypond: Line breaking can be slow with very wide paper, lilypond, 01:30
• January 29, 2012
  • tuplets, G . S . Williams, 22:35
  • Re: Issue 2256 in lilypond: empty strings: tabStaff insists on stringnumbers and looses notes, lilypond, 19:31
  • Re: Issue 2229 in lilypond: Patch: Broadcast articulations not in EventChord, lilypond, 15:30
  • Re: Issue 2247 in lilypond: Patch: parser.yy: strip music-wrapper-music inside of EventChord, lilypond, 15:03
  • Re: Issue 2247 in lilypond: Patch: parser.yy: strip music-wrapper-music inside of EventChord, lilypond, 14:59
  • Re: Issue 2263 in lilypond: Reimplement chord repetition, lilypond, 14:01
  • Re: Issue 2261 in lilypond: Sustain off placement bug, lilypond, 13:34
  • Re: Issue 2263 in lilypond: Reimplement chord repetition, David Kastrup, 13:10
  • Re: Issue 2263 in lilypond: Reimplement chord repetition, Graham Percival, 12:47
  • Re: Issue 2263 in lilypond: Reimplement chord repetition, David Kastrup, 12:40
  • Re: Issue 2263 in lilypond: Reimplement chord repetition, David Kastrup, 12:30
  • Re: Issue 2263 in lilypond: Reimplement chord repetition, lilypond, 12:26
  • Re: Issue 2263 in lilypond: Reimplement chord repetition, lilypond, 12:22
  • Re: Issue 2263 in lilypond: Reimplement chord repetition, lilypond, 12:12
  • Re: Issue 2263 in lilypond: Reimplement chord repetition, lilypond, 12:08
  • Re: Issue 2263 in lilypond: Reimplement chord repetition, lilypond, 12:04
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 12:00
  • Re: Issue 2263 in lilypond: Reimplement chord repetition, lilypond, 11:56
  • Issue 2263 in lilypond: Reimplement chord repetition, lilypond, 11:52
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 11:35
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, Werner LEMBERG, 10:54
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 10:47
  • Re: Issue 2209 in lilypond: lilypond-book creates uncompilable latex files (windows), lilypond, 10:43
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 10:39
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 10:35
  • Re: Issue 2210 in lilypond: Patch: Build: Top-level GNUmakefile, lilypond, 10:31
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 10:27
  • Re: Issue 2255 in lilypond: Doc: NR Add @warning for Margin adjustment', lilypond, 10:23
  • Re: Issue 2189 in lilypond: Doc: NR add to \partial for clearer understanding, lilypond, 10:19
  • Re: Issue 2179 in lilypond: Improve warnings about spanners/lyrics etc. cannot be set from 'outside' to 'inside' << {...} \\ {...} >> constructs, lilypond, 10:15
  • Re: Issue 2162 in lilypond: Patch: Doc: NR added @knownissue for beam properties, lilypond, 10:11
  • Re: Issue 2040 in lilypond: Documentation for unpure-pure-containers, lilypond, 10:07
  • Re: @rlsrnamed{Name,Translation} translates also the name in the URI, Federico Bruni, 09:30
  • Re: Bug squad roll call, Colin Hall, 09:22
  • Re: Issue 2251 in lilypond: website still doesn't auto-update, lilypond, 09:20
  • Re: Issue 2256 in lilypond: empty strings: tabStaff insists on stringnumbers and looses notes, David Kastrup, 08:54
  • Re: Issue 2260 in lilypond: line-broken spanners start too far to the right, with \tempo and \time, lilypond, 08:52
  • Re: Issue 2256 in lilypond: empty strings: tabStaff insists on stringnumbers and looses notes, lilypond, 08:48
  • Re: Issue 2251 in lilypond: website still doesn't auto-update, lilypond, 08:44
  • Re: Issue 803 in lilypond: correction needed for the German translation of convert-ly, lilypond, 08:28
  • Re: Issue 2223 in lilypond: Regtest for lilypond-book are not running, lilypond, 08:24
  • Re: Issue 2251 in lilypond: website still doesn't auto-update, lilypond, 08:20
  • Re: Issue 2251 in lilypond: website still doesn't auto-update, lilypond, 07:45
  • Re: Issue 2251 in lilypond: website still doesn't auto-update, lilypond, 07:42
  • Re: Issue 2260 in lilypond: line-broken spanners start too far to the right, with \tempo and \time, lilypond, 07:37
  • Re: Issue 2256 in lilypond: empty strings: tabStaff insists on stringnumbers and looses notes, lilypond, 07:33
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 07:29
  • Re: Issue 2222 in lilypond: lilypond-book fails with html input, lilypond, 07:25
  • Re: Issue 2231 in lilypond: Tuplet bracket makes space for dynamic but dynamic is placed underneath bracket, lilypond, 07:21
  • Re: Bug squad roll call, Graham Percival, 07:20
  • Re: Issue 2160 in lilypond: document LILYPOND_WEB_MEDIA_GIT, lilypond, 07:17
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 07:13
  • Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly, lilypond, 07:09
  • Re: Issue 1997 in lilypond: segfault in tablature-negative-fret.ly, lilypond, 07:05
  • Re: Issue 1933 in lilypond: Lilypond-book subprocess doesn't work on mingw, lilypond, 07:01
  • Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse, lilypond, 06:57
  • Re: Issue 1802 in lilypond: system-system-spacing in lilypond-book-file within a LaTeX file, lilypond, 06:53
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond, lilypond, 06:49
  • Re: Issue 2162 in lilypond: Patch: Doc: NR added @knownissue for beam properties, lilypond, 06:45
  • Re: Issue 1566 in lilypond: Beam properties won't be changed after the start of the beam, lilypond, 06:41
  • Re: Issue 1352 in lilypond: Polyphonic dots placement is inconsistent, confusing and prone to collisions, lilypond, 06:37
  • Re: Issue 1230 in lilypond: Dot may collide with flag with some stem's 'length values, lilypond, 06:33
  • Re: Issue 1183 in lilypond: @rcontrib{} from topdocs doesn't work, lilypond, 06:29
  • Re: Issue 1566 in lilypond: Beam properties won't be changed after the start of the beam, lilypond, 06:25
  • Re: Issue 1091 in lilypond: Dot in \voiceOne collides with stem in \voiceThree in short intervals, lilypond, 06:21
  • Re: Issue 2189 in lilypond: Doc: NR add to \partial for clearer understanding, lilypond, 06:17
  • Re: Bug squad roll call, Marek Klein, 06:13
  • Re: Issue 2040 in lilypond: Documentation for unpure-pure-containers, lilypond, 06:13
  • Re: Issue 2255 in lilypond: Doc: NR Add @warning for Margin adjustment', lilypond, 06:09
  • Re: Issue 2179 in lilypond: Improve warnings about spanners/lyrics etc. cannot be set from 'outside' to 'inside' << {...} \\ {...} >> constructs, lilypond, 06:05
  • Re: Issue 856 in lilypond: links in Snippets appear to not work for snippets in multiple categories, lilypond, 06:01
  • Re: Bug squad roll call, James, 06:00
  • Re: Issue 737 in lilypond: Enhancement: support for footnotes and/or endnotes., lilypond, 05:56
  • Bug squad roll call, Phil Holmes, 05:51
  • Re: Issue 2178 in lilypond: NR: clarify the subsection "Automatic accidentals" of section 1.1.3, lilypond, 05:45
  • Re: Issue 2179 in lilypond: Improve warnings about spanners/lyrics etc. cannot be set from 'outside' to 'inside' << {...} \\ {...} >> constructs, lilypond, 05:40
  • Re: Issue 2262 in lilypond: Patch: Creates a MIDI note length formatter, lilypond, 05:28
  • Re: Issue 2255 in lilypond: Doc: NR Add @warning for Margin adjustment', lilypond, 05:18
  • Issue 2262 in lilypond: Patch: Creates a MIDI note length formatter, lilypond, 04:34
  • Re: Issue 1717 in lilypond: Possible incompatibility with Ghostscript 9 (was: Full notes and half notes are drawn filled), lilypond, 03:34
• January 28, 2012
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 22:52
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 21:00
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 20:05
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 19:50
  • Re: Issue 1352 in lilypond: Polyphonic dots placement is inconsistent, confusing and prone to collisions, lilypond, 17:59
  • Re: Issue 1230 in lilypond: Dot may collide with flag with some stem's 'length values, Keith OHara, 17:57
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 16:18
  • Re: Issue 2260 in lilypond: broken ottava spanner interferes with \tempo and \time, Werner LEMBERG, 16:12
  • Re: Issue 2260 in lilypond: broken ottava spanner interferes with \tempo and \time, Keith OHara, 16:05
  • Re: Issue 2260 in lilypond: line-broken spanners start too far to the right, with \tempo and \time, lilypond, 16:02
  • Re: Sustain off placement bug, Keith OHara, 15:52
  • Issue 2261 in lilypond: Sustain off placement bug, lilypond, 15:42
  • Re: Sustain off placement bug, James, 15:42
  • Re: Issue 2259 in lilypond: Hairpin still hits barline at line break, lilypond, 15:15
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 14:57
  • Sustain off placement bug, Phil Holmes, 13:48
  • Re: Issue 2260 in lilypond: broken ottava spanner interferes with \tempo and \time, lilypond, 12:47
  • Re: Issue 2134 in lilypond: Redirect old website / download to new location, lilypond, 09:59
  • Re: Issue 2260 in lilypond: broken ottava spanner interferes with \tempo and \time, lilypond, 08:59
  • Re: Issue 2260 in lilypond: broken ottava spanner interferes with \tempo and \time, lilypond, 08:00
  • Re: Issue 2260 in lilypond: broken ottava spanner interferes with \tempo and \time, lilypond, 07:42
  • Issue 2260 in lilypond: broken ottava spanner interferes with \tempo and \time, lilypond, 07:38
  • Re: Issue 1964 in lilypond: lilydev 2.0, lilypond, 07:34
  • Re: Issue 1230 in lilypond: Dot may collide with flag with some stem's 'length values, -Eluze, 04:27
• January 27, 2012
  • Re: Issue 2259 in lilypond: Hairpin still hits barline at line break, lilypond, 14:37
  • Re: Issue 2259 in lilypond: Hairpin still hits barline at line break, lilypond, 14:10
  • Re: Bug for slur and (not) restored accidental, James, 14:00
  • Re: Bug for slur and (not) restored accidental, Xavier Scheuer, 13:57
  • Re: Issue 2259 in lilypond: Hairpin still hits barline at line break, lilypond, 13:49
  • Re: Issue 2259 in lilypond: Hairpin still hits barline at line break, lilypond, 13:22
  • Re: Issue 2259 in lilypond: Hairpin still hits barline at line break, lilypond, 12:52
  • Bug for slur and (not) restored accidental, Rutger Hofman, 12:50
  • Re: Issue 2259 in lilypond: Hairpin still hits barline at line break, lilypond, 12:39
  • Re: Issue 2259 in lilypond: Hairpin still hits barline at line break, lilypond, 12:28
  • Re: Issue 2259 in lilypond: Hairpin still hits barline at line break, lilypond, 12:24
  • Re: Issue 2259 in lilypond: Hairpin still hits barline at line break, lilypond, 12:20
  • Re: Issue 2259 in lilypond: Hairpin still hits barline at line break, lilypond, 12:16
  • Re: Issue 621 in lilypond: Dynamics should avoid cross-staff BarLines (e.g. GrandStaff, PianoStaff etc), lilypond, 12:12
  • Re: Issue 2130 in lilypond: Hairpin hits barline at line break, lilypond, 12:03
  • Re: Issue 2259 in lilypond: Hairpin still hits barline at line break, lilypond, 11:56
  • Re: Issue 2130 in lilypond: Hairpin hits barline at line break, lilypond, 11:52
  • Issue 2259 in lilypond: Hairpin still hits barline at line break, lilypond, 11:48
  • Re: Issue 2247 in lilypond: Patch: parser.yy: strip music-wrapper-music inside of EventChord, lilypond, 11:44
  • Re: Issue 2130 in lilypond: Hairpin hits barline at line break, lilypond, 11:38
  • Re: Issue 1 in lilypond: this is a test, lilypond, 09:18
  • Re: Issue 2256 in lilypond: empty strings: tabStaff insists on stringnumbers and looses notes, lilypond, 08:58
  • Re: make doc problem, Phil Holmes, 08:57
  • Re: make doc problem, Phil Holmes, 08:38
  • Re: Issue 2256 in lilypond: empty strings: tabStaff insists on stringnumbers and looses notes, lilypond, 08:35
  • Re: Issue 2243 in lilypond: Incorrect subdivision of beams, lilypond, 08:04
  • Re: Issue 2256 in lilypond: empty strings: tabStaff insists on stringnumbers and looses notes, lilypond, 08:00
  • Re: Issue 2256 in lilypond: empty strings: tabStaff insists on stringnumbers and looses notes, lilypond, 07:56
  • Re: Issue 2242 in lilypond: Incorrect tabstaff fingering, lilypond, 07:52
  • Re: Issue 2255 in lilypond: Doc: NR Add @warning for Margin adjustment', lilypond, 04:27
  • Re: Issue 2189 in lilypond: Doc: NR add to \partial for clearer understanding, lilypond, 04:22
  • Re: Issue 2189 in lilypond: Doc: NR add to \partial for clearer understanding, lilypond, 04:17
  • Re: Issue 2249 in lilypond: ledger lines of pitched rests are verticaly misplaced, lilypond, 03:41
  • Re: Issue 2258 in lilypond: Bad regression test 'beam-shortened-lengths.ly', lilypond, 02:00
  • Re: Issue 2257 in lilypond: reg-test beam-shortened-lengths.ly fails, lilypond, 01:45
  • Issue 2258 in lilypond: Bad regression test 'beam-shortened-lengths.ly', lilypond, 01:41
  • Re: Issue 2256 in lilypond: empty strings: tabStaff insists on stringnumbers and looses notes, lilypond, 00:47
  • Re: Issue 2249 in lilypond: ledger lines of pitched rests are verticaly misplaced, lilypond, 00:07
• January 26, 2012
  • Issue 2257 in lilypond: reg-test beam-shortened-lengths.ly fails, lilypond, 23:29
  • Re: Issue 2248 in lilypond: Patch: change bugreports expected response time, lilypond, 22:59
  • Re: Issue 2223 in lilypond: Regtest for lilypond-book are not running, lilypond, 22:55
  • Re: Issue 2189 in lilypond: Doc: NR add to \partial for clearer understanding, lilypond, 22:51
  • Re: Issue 803 in lilypond: correction needed for the German translation of convert-ly, lilypond, 22:47
  • Re: empty strings: tabStaff insists on stringnumbers and looses notes, Ralph Palmer, 19:04
  • Issue 2256 in lilypond: empty strings: tabStaff insists on stringnumbers and looses notes, lilypond, 19:04
  • Re: Top Margin Adjustment, Ralph Palmer, 19:00
  • Issue 2255 in lilypond: Margin adjustment documentation, lilypond, 19:00
  • Re: make doc problem, Julien Rioux, 18:19
  • Re: make doc problem, Graham Percival, 18:15
  • Re: make doc problem, Julien Rioux, 18:01
  • Re: make doc problem, Julien Rioux, 17:57
  • a beaming regression?, Janek Warchoł, 17:41
  • Re: Issue 2249 in lilypond: ledger lines of pitched rests are verticaly misplaced, lilypond, 17:32
  • Re: Issue 1985 in lilypond: musicxml2ly: group-symbol none leads to bus error, lilypond, 16:47
  • Re: Issue 2225 in lilypond: Patch: Docs: Explain the difference between ritardando and rallentando, lilypond, 16:25
  • Re: Issue 2227 in lilypond: Patch: changes.tely: mention Flag changes, remove duplicate "does", lilypond, 16:21
  • Re: Issue 2238 in lilypond: Patch: Spelling fixes in comments and documentation, lilypond, 16:11
  • Re: Issue 2248 in lilypond: Patch: change bugreports expected response time, lilypond, 12:55
  • Re: Issue 2249 in lilypond: ledger lines of pitched rests are verticaly misplaced, lilypond, 12:51
  • Re: how shall I handle "issues to verify", Phil Holmes, 12:43
  • Re: make doc problem, Phil Holmes, 12:40
  • Re: Issue 2180 in lilypond: beams are detached from stems, lilypond, 11:32
  • Re: make doc problem, Reinhold Kainhofer, 11:13
  • Re: Issue 2180 in lilypond: beams are detached from stems, lilypond, 10:47
  • Re: Issue 2200 in lilypond: Dots shouldn't always be placed in one column, lilypond, 10:24
  • Re: Issue 2220 in lilypond: Undefined references to node in translated manuals, lilypond, 09:42
  • Re: Issue 2224 in lilypond: LM: clickable examples in the docs have stopped working., lilypond, 09:23
  • Re: Issue 2254 in lilypond: Function like '\partcombineApart' for two notes of the same pitch and duration at the same time, lilypond, 07:44
  • Re: Issue 2044 in lilypond: convert-ly fails on input with invalid version string, lilypond, 05:28
  • Re: Issue 39 in lilypond: collision flag notehead with polyphony, lilypond, 05:14
  • Re: Issue 2044 in lilypond: convert-ly fails on input with invalid version string, lilypond, 05:05
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chordwith\relative and #{ #} syntax, Trevor Daniels, 03:50
  • Re: Issue 2044 in lilypond: convert-ly fails on input with invalid version string, lilypond, 02:50
  • Re: Issue 2247 in lilypond: Patch: parser.yy: strip music-wrapper-music inside of EventChord, Colin Campbell, 01:00
  • Re: Issue 2240 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 00:28
  • Re: Issue 2247 in lilypond: Patch: parser.yy: strip music-wrapper-music inside of EventChord, lilypond, 00:24
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with\relative and #{ #} syntax, David Kastrup, 00:12
• January 25, 2012
  • Re: Issue 2180 in lilypond: beams are detached from stems, lilypond, 18:34
  • Re: Issue 2109 in lilypond: do not tinker with the position of a pitched rest, -Eluze, 17:47
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with\relative and #{ #} syntax, Trevor Daniels, 17:35
  • Issue 2254 in lilypond: Function like '\partcombineAutomatic' for two notes of the same duration at the same time, lilypond, 16:57
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 13:07
  • Re: Issue 2240 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 12:52
  • Re: Issue 2231 in lilypond: Tuplet bracket makes space for dynamic but dynamic is placed underneath bracket, lilypond, 12:48
  • Re: Issue 2253 in lilypond: Markup in separate voices in \partcombine results in "stacked" markup., lilypond, 12:39
  • Issue 2253 in lilypond: Markup in separate voices in \partcombine results in "stacked" markup., lilypond, 12:25
  • Re: Markup in Partcombine, James, 12:24
  • Re: Issue 2252 in lilypond: the first bar's shortest-duration-space carries over into the first beat of the second, lilypond, 12:18
  • Issue 2252 in lilypond: the first bar's shortest-duration-space carries over into the first beat of the second, lilypond, 12:14
  • Re: Strange spacing, James, 12:14
  • Re: Issue 2231 in lilypond: Tuplet bracket makes space for dynamic but dynamic is placed underneath bracket, lilypond, 12:10
  • Re: Issue 2109 in lilypond: do not tinker with the position of a pitched rest, lilypond, 12:04
  • Re: Issue 552 in lilypond: Metronome mark affects spacing, lilypond, 11:37
  • Re: Issue 552 in lilypond: Metronome mark affects spacing, lilypond, 11:33
  • Re: Issue 2249 in lilypond: ledger lines of pitched rests are verticaly misplaced, lilypond, 11:29
  • Re: Issue 2240 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., David Kastrup, 09:54
  • Re: Issue 1379 in lilypond: augmentum in Gregorian notation compromises layout and is applied to wrong (groups of) notes, lilypond, 09:51
  • Markup in Partcombine, Nels, 09:38
  • Re: Strange spacing, Thomas Scharkowski, 06:43
  • Re: Issue 2249 in lilypond: ledger lines of pitched rests are verticaly misplaced, -Eluze, 05:52
  • Issue 2251 in lilypond: website still doesn't auto-update, lilypond, 05:07
  • Re: Issue 2249 in lilypond: ledger lines of pitched rests are verticaly misplaced, lilypond, 04:31
  • Re: Issue 2249 in lilypond: ledger lines of pitched rests are verticaly misplaced, lilypond, 03:44
  • Re: how shall I handle "issues to verify", Janek Warchoł, 03:40
  • Re: Issue 2249 in lilypond: ledger lines of pitched rests are verticaly misplaced, lilypond, 03:33
  • Re: Issue 2249 in lilypond: ledger lines of pitched rests are verticaly misplaced, lilypond, 03:24
  • Re: Issue 2249 in lilypond: ledger lines of pitched rests are verticaly misplaced, lilypond, 03:13
  • Re: Issue 2249 in lilypond: ledger lines of pitched rests are verticaly misplaced, lilypond, 02:56
  • Re: Issue 2249 in lilypond: ledger lines of pitched rests are verticaly misplaced, lilypond, 02:34
  • Issue 2250 in lilypond: notes from \quoteDuring ignored in MIDI, lilypond, 00:55
• January 24, 2012
  • Re: Issue 1922 in lilypond: Adds StemTremolo to the note column's element list., lilypond, 23:21
  • Re: Issue 1850 in lilypond: FiguredBass: Rewrite of the engraver to fix vertical position, lilypond, 23:17
  • Re: Issue 155 in lilypond: \parenthesize does not take accidentals into account, lilypond, 23:13
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 23:09
  • Re: Issue 1128 in lilypond: Text pedal mark not closed at music end, lilypond, 23:05
  • Re: Issue 1784 in lilypond: Adds epsilon to Bezier range calculations, lilypond, 23:01
  • Re: Issue 1786 in lilypond: New engraver for braces, lilypond, 22:57
  • Re: Issue 1833 in lilypond: Deprecate \fermataMarkup for full-bar rests., lilypond, 22:53
  • Re: Issue 1742 in lilypond: print transposed guitar chords on piano sheets, lilypond, 22:49
  • Re: Issue 2248 in lilypond: Patch: change bugreports expected response time, lilypond, 22:45
  • Re: Issue 2240 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 22:19
  • Re: Issue 2238 in lilypond: Patch: Spelling fixes in comments and documentation, lilypond, 22:16
  • Re: Issue 2109 in lilypond: do not tinker with the position of a pitched rest, lilypond, 19:13
  • Issue 2249 in lilypond: ledger lines of pitched rests are verticaly misplaced, lilypond, 19:05
  • Re: how shall I handle "issues to verify", Graham Percival, 18:22
  • how shall I handle "issues to verify", -Eluze, 18:10
  • Re: Issue 1726 in lilypond: python versions might not be updating, lilypond, 17:58
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 17:44
  • Re: Issue 2228 in lilypond: Some users prefer to minimize partial beams rather than beam by the beat, lilypond, 14:15
  • Re: Issue 2244 in lilypond: Beamlet orientation is wrong in compound meters, lilypond, 14:11
  • Re: Issue 2228 in lilypond: Some users prefer to minimize partial beams rather than beam by the beat, lilypond, 13:48
  • Issue 2248 in lilypond: Patch: change bugreports expected response time, lilypond, 08:44
  • Re: Need to resign from Bug Squad, Colin Campbell, 08:34
  • Re: Need to resign from Bug Squad, Marek Klein, 07:31
  • Need to resign from Bug Squad, Brett McCoy, 07:18
  • Re: Issue 2223 in lilypond: Regtest for lilypond-book are not running, lilypond, 07:12
  • Re: Issue 803 in lilypond: correction needed for the German translation of convert-ly, lilypond, 07:07
  • Re: Issue 2189 in lilypond: Doc: NR add to \partial for clearer understanding, lilypond, 07:04
  • Re: Issue 2040 in lilypond: Documentation for unpure-pure-containers, lilypond, 06:29
  • Re: empty strings: tabStaff insists on stringnumbers and looses notes, S . Runkel, 04:50
  • Re: Issue 2127 in lilypond: Patch: Directs output of texi2html to log files (GOP 9), lilypond, 04:16
  • Re: Issue 2189 in lilypond: Doc: NR add to \partial for clearer understanding, lilypond, 03:34
  • Re: Issue 2040 in lilypond: Documentation for unpure-pure-containers, lilypond, 02:47
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 02:34
  • Re: Issue 2040 in lilypond: Documentation for unpure-pure-containers, lilypond, 02:30
• January 23, 2012
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 23:40
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 23:29
  • Re: Issue 2127 in lilypond: Patch: Directs output of texi2html to log files (GOP 9), lilypond, 18:51
  • Re: Issue 2127 in lilypond: Patch: Directs output of texi2html to log files (GOP 9), lilypond, 18:44
  • Re: Top Margin Adjustment, Xavier Scheuer, 18:38
  • Re: Top Margin Adjustment, Xavier Scheuer, 18:30
  • Re: Issue 2245 in lilypond: wrong/inconsistent placement of lyrics and dynamics under suspended notes, lilypond, 18:28
  • Re: Issue 2245 in lilypond: wrong/inconsistent placement of lyrics under suspended notes, lilypond, 18:24
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 18:10
  • Re: Strange spacing, Thomas Morley, 17:52
  • Re: Issue 2243 in lilypond: Incorrect subdivision of beams, lilypond, 17:10
  • Re: Issue 1815 in lilypond: lilypond-book fails on Windows, lilypond, 16:30
  • Re: Issue 2127 in lilypond: Patch: Directs output of texi2html to log files (GOP 9), lilypond, 16:26
  • Re: Issue 2028 in lilypond: Make doc always recreates HTML files, lilypond, 16:14
  • Re: Issue 2158 in lilypond: Patch: Sketch of not remaking html files, lilypond, 16:10
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 16:06
  • Re: Issue 2223 in lilypond: Regtest for lilypond-book are not running, lilypond, 15:53
  • Re: Issue 2223 in lilypond: Regtest for lilypond-book are not running, lilypond, 15:07
  • Re: Issue 2223 in lilypond: Regtest for lilypond-book are not running, lilypond, 15:03
  • Re: Issue 2239 in lilypond: google code only returns 20 or 25 comments with API, lilypond, 14:59
  • Re: Issue 2222 in lilypond: lilypond-book fails with html input, lilypond, 14:55
  • Re: Issue 2223 in lilypond: Regtest for lilypond-book are not running, lilypond, 14:51
  • Re: Issue 2224 in lilypond: LM: clickable examples in the docs have stopped working., lilypond, 14:47
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 13:49
  • Re: Issue 2239 in lilypond: google code only returns 20 or 25 comments with API, lilypond, 12:10
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 10:12
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 10:02
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 09:22
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 08:38
  • Re: Strange spacing, David Kastrup, 08:18
  • Re: Strange spacing, Werner LEMBERG, 08:16
  • Re: Strange spacing, Thomas Scharkowski, 08:11
  • Re: Strange spacing, David Kastrup, 07:41
  • Re: Strange spacing, Thomas Scharkowski, 07:32
  • Re: Strange spacing, Thomas Scharkowski, 07:21
  • Re: Strange spacing, James, 07:18
  • Re: Strange spacing, Neil Puttock, 07:10
  • Re: Strange spacing, James, 07:06
  • Re: Strange spacing, Thomas Scharkowski, 06:31
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 05:55
  • Re: Strange spacing, Francisco Vila, 05:45
  • Re: Strange spacing, Francisco Vila, 05:40
  • Re: Strange spacing, James, 05:40
  • Strange spacing, Thomas Scharkowski, 04:55
  • Re: Issue 2193 in lilypond: collision between beams and flags, lilypond, 04:52
  • Re: Issue 2204 in lilypond: Patch: Gets rid of PostScript in bar-chords-notation-for-guitar--with-text-spanner.ly, lilypond, 04:48
  • Re: Issue 2205 in lilypond: Breathing sign is positioned incorrectly after changing Staff or TabStaff size, lilypond, 04:44
  • Re: Issue 2206 in lilypond: Patch: Let \footnote do the job of \footnote, \footnoteGrob, \autoFootnote and \autoFootnoteGrob, lilypond, 04:40
  • Re: Issue 2213 in lilypond: Update documentation for \footnotes in Notation Reference, lilypond, 04:36
  • Re: Issue 2215 in lilypond: lost commits jan 7, lilypond, 04:32
  • Re: Issue 2218 in lilypond: Web: Added Concert to Introduction.itexi, lilypond, 04:28
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 04:24
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 02:24
• January 22, 2012
  • Re: Issue 2237 in lilypond: Patch: Fix spelling in input/regression/*.ly, lilypond, 16:26
  • Re: Issue 2226 in lilypond: Patch: Docs: Explain the difference between ritardando and rallentando, lilypond, 16:22
  • Re: Issue 2223 in lilypond: Regtest for lilypond-book are not running, lilypond, 15:54
  • Re: Issue 1964 in lilypond: lilydev 2.0, lilypond, 15:35
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 15:16
  • Re: make doc problem, Phil Holmes, 15:13
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 15:11
  • Re: make doc problem, David Kastrup, 15:05
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 15:05
  • Re: make doc problem, Julien Rioux, 14:59
  • Re: make doc problem, Jean-Charles Malahieude, 14:48
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 14:40
  • Re: make doc problem, David Kastrup, 14:39
  • Re: make doc problem, Julien Rioux, 14:22
  • Re: make doc problem, Julien Rioux, 14:15
  • Re: make doc problem, Jean-Charles Malahieude, 14:14
  • Re: make doc problem, Jean-Charles Malahieude, 14:11
  • Re: make doc problem, Julien Rioux, 14:06
  • Re: make doc problem, Phil Holmes, 13:42
  • Re: make doc problem, Julien Rioux, 13:35
  • Re: make doc problem, Julien Rioux, 13:32
  • Re: make doc problem, Phil Holmes, 13:31
  • Re: Issue 2240 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 13:24
  • Re: Issue 2247 in lilypond: Patch: parser.yy: strip music-wrapper-music inside of EventChord, lilypond, 13:20
  • make doc problem, Jean-Charles Malahieude, 13:20
  • Issue 2247 in lilypond: Patch: parser.yy: strip music-wrapper-music inside of EventChord, lilypond, 13:16
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 13:00
  • Re: ERROR: Unable to find file "ice-9/boot-9.scm" in load path, Ian Hulin, 12:52
  • Issue 2246 in lilypond: beaming in 3/4 - a setting to not beam 3 eights against the beat., lilypond, 12:49
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 11:54
  • Issue 2245 in lilypond: wrong/inconsistent placement of lyrics under suspended notes, lilypond, 11:50
  • Re: Issue 1183 in lilypond: @rcontrib{} from topdocs doesn't work, lilypond, 11:38
  • Re: Issue 2210 in lilypond: Patch: Build: Top-level GNUmakefile, lilypond, 11:34
  • Re: Issue 2210 in lilypond: Patch: Build: Top-level GNUmakefile, lilypond, 11:30
  • Re: Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 11:26
  • Re: Issue 2210 in lilypond: Patch: Build: Top-level GNUmakefile, lilypond, 11:11
  • Re: Issue 2210 in lilypond: Patch: Build: Top-level GNUmakefile, lilypond, 10:44
  • Re: Issue 2240 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 07:16
  • Issue 2244 in lilypond: Beamlet orientation is wrong in compound meters, lilypond, 06:58
  • Re: Defect [new]: \partcombine: accidental reminders of first partlost., Phil Holmes, 06:55
  • Re: Tuplet Bracket Spacing Bug, Phil Holmes, 06:50
  • Re: Regression: 16th tuplets not subdivided with subdivideBeams, Phil Holmes, 06:47
  • Issue 2243 in lilypond: Incorrect subdivision of beams, lilypond, 06:47
  • Issue 2242 in lilypond: Incorrect tabstaff fingering, lilypond, 06:35
  • Re: Tabstaff: Epmty String no longer prefered when accord spans 2 octaves, Phil Holmes, 06:35
  • Re: empty strings: tabStaff insists on stringnumbers and looses notes, Phil Holmes, 06:30
  • Re: LilyPond ignores copyright assertions for scores in a book., Phil Holmes, 06:21
  • Issue 2241 in lilypond: Book only puts copyright information on the first page, lilypond, 06:21
  • Re: Issue 2240 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 05:22
  • Re: Issue 2240 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 04:17
  • LilyPond ignores copyright assertions for scores in a book., Christopher R . Maden, 00:00
• January 21, 2012
  • Re: Issue 2044 in lilypond: convert-ly fails on input with invalid version string, lilypond, 18:58
  • Re: Issue 2044 in lilypond: convert-ly fails on input with invalid version string, lilypond, 18:28
  • Re: Issue 803 in lilypond: correction needed for the German translation of convert-ly, lilypond, 18:04
  • Re: Issue 2056 in lilypond: Typos in German translation, lilypond, 18:00
  • Re: ERROR: Unable to find file "ice-9/boot-9.scm" in load path, Damian leGassick, 17:39
  • Re: Issue 2240 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 16:03
  • Re: Issue 2240 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 13:47
  • Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 13:09
  • Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 13:05
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 13:01
  • Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 12:18
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 12:14
  • Re: Issue 2240 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 11:48
  • Re: Issue 2240 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 11:44
  • Re: Issue 2240 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 11:40
  • Re: Issue 2239 in lilypond: google code only returns 20 or 25 comments with API, lilypond, 11:36
  • Re: Issue 2240 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 11:32
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 11:28
  • Issue 2240 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 11:24
  • Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 11:20
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 11:16
  • Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 10:48
  • Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 10:44
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 10:20
  • Re: Issue 2239 in lilypond: google code only returns 20 or 25 comments with API, lilypond, 09:42
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 09:38
  • Issue 2239 in lilypond: google code only returns 20 or 25 comments with API, lilypond, 09:34
  • empty strings: tabStaff insists on stringnumbers and looses notes, s . runkel, 09:24
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 09:15
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 09:05
  • Tabstaff: Epmty String no longer prefered when accord spans 2 octaves, s . runkel, 08:45
  • Re: Issue 2229 in lilypond: Patch: Broadcast articulations not in EventChord, lilypond, 08:40
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 08:36
  • Re: Issue 2237 in lilypond: Patch: Fix spelling in input/regression/*.ly, lilypond, 08:32
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 08:28
  • Re: ERROR: Unable to find file "ice-9/boot-9.scm" in load path, James, 08:09
  • Re: ERROR: Unable to find file "ice-9/boot-9.scm" in load path, address@hidden, 07:55
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 07:21
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 07:11
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 06:51
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., David Kastrup, 06:45
  • Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 06:41
  • Re: Issue 2235 in lilypond: \partcombine: accidental reminders of first part lost, lilypond, 06:37
  • Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 06:33
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 06:29
  • Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 06:25
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 06:21
  • Re: Issue 2228 in lilypond: Some users prefer to minimize partial beams rather than beam by the beat, Graham Percival, 06:19
  • Re: Issue 2237 in lilypond: Patch: Fix spelling in input/regression/*.ly, lilypond, 06:17
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 06:13
  • Regression: 16th tuplets not subdivided with subdivideBeams, Xavier Scheuer, 06:12
  • Re: Issue 2238 in lilypond: Patch: Spelling fixes in comments and documentation, lilypond, 06:09
  • Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 06:05
  • Re: Issue 2237 in lilypond: Patch: Fix spelling in input/regression/*.ly, lilypond, 06:01
  • Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 05:40
  • Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 05:32
  • Re: Issue 2238 in lilypond: Patch: Spelling fixes in comments and documentation, lilypond, 05:07
  • Re: Issue 2237 in lilypond: Patch: Fix spelling in input/regression/*.ly, lilypond, 05:03
  • Issue 2238 in lilypond: Patch: Spelling fixes in comments and documentation, lilypond, 04:59
  • Issue 2237 in lilypond: Patch: Fix spelling in input/regression/*.ly, lilypond, 04:55
  • Re: Issue 2233 in lilypond: Patch: Make inherited stream event properties immutable., lilypond, 03:54
  • Re: Issue 1230 in lilypond: Dot may collide with flag with some stem's 'length values, lilypond, 01:15
• January 20, 2012
  • Re: Issue 2201 in lilypond: dots are sometimes placed too far from the notes, lilypond, 23:33
  • Re: Issue 2200 in lilypond: Dots shouldn't always be placed in one column, lilypond, 23:29
  • Re: Issue 1352 in lilypond: Polyphonic dots placement is inconsistent, confusing and prone to collisions, lilypond, 23:25
  • Re: Issue 1091 in lilypond: Dot in \voiceOne collides with stem in \voiceThree in short intervals, lilypond, 23:21
  • Re: Issue 2165 in lilypond: Patch: Modifies broken hairpin height, lilypond, 18:29
  • Re: Issue 2225 in lilypond: Patch: Docs: Explain the difference between ritardando and rallentando, lilypond, 18:25
  • Re: Issue 2227 in lilypond: Patch: changes.tely: mention Flag changes, remove duplicate "does", lilypond, 18:21
  • Re: Issue 2235 in lilypond: \partcombine: accidental reminders of first part lost, lilypond, 17:34
  • Re: Issue 2236 in lilypond: accidentals in "complex chords", lilypond, 17:30
  • Re: Issue 2235 in lilypond: \partcombine: accidental reminders of first part lost, lilypond, 17:26
  • Re: Issue 2175 in lilypond: Patch: explain how to add git-cl to PATH, lilypond, 16:31
  • Re: Defect: quarter tones sound bad before rest, Marek Klein, 16:23
  • Re: Defect [new]: \partcombine: accidental reminders of first part lost., Marek Klein, 16:22
  • Re: Defect [new]: \partcombine: accidental reminders of first part lost., Marek Klein, 16:19
  • Issue 2236 in lilypond: accidentals in "complex chords", lilypond, 16:18
  • Issue 2235 in lilypond: \partcombine: accidental reminders of first part lost, lilypond, 16:11
  • Issue 2234 in lilypond: MIDI: quarter tones sound bad before rest, lilypond, 15:23
  • Re: Defect: quarter tones sound bad before rest, Pavel Roskin, 11:53
  • Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 08:44
  • Re: Issue 2233 in lilypond: Patch: Make inherited stream event properties immutable., lilypond, 07:42
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 07:34
  • Issue 2233 in lilypond: Patch: Make inherited stream event properties immutable., lilypond, 06:23
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 05:27
  • Re: Defect: quarter tones sound bad before rest, David Kastrup, 03:55
  • Re: Issue 2213 in lilypond: Update documentation for \footnotes in Notation Reference, lilypond, 03:06
  • Re: Issue 2200 in lilypond: Dots shouldn't always be placed in one column, lilypond, 01:16
  • Re: Issue 2213 in lilypond: Update documentation for \footnotes in Notation Reference, lilypond, 01:12
  • Re: Issue 2227 in lilypond: Patch: changes.tely: mention Flag changes, remove duplicate "does", lilypond, 01:07
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 00:36
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 00:22
• January 19, 2012
  • Re: Defect: quarter tones sound bad before rest, Keith OHara, 21:13
  • Re: Defect: quarter tones sound bad before rest, Pavel Roskin, 20:25
  • Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers, Janek Warchoł, 19:22
  • Re: Defect: quarter tones sound bad before rest, Ralph Palmer, 18:50
  • Re: Defect [new]: \partcombine: accidental reminders of first part lost., Xavier Scheuer, 18:26
  • Defect: quarter tones sound bad before rest, Pavel Roskin, 17:38
  • Re: Defect [new]: \partcombine: accidental reminders of first part lost., James, 16:52
  • Defect [new]: \partcombine: accidental reminders of first part lost., Peter Häring, 16:25
  • Re: Issue 2224 in lilypond: LM: clickable examples in the docs have stopped working., lilypond, 13:51
  • Re: Issue 2224 in lilypond: LM: clickable examples in the docs have stopped working., lilypond, 13:44
  • Re: Issue 2228 in lilypond: Some users prefer to minimize partial beams rather than beam by the beat, lilypond, 13:40
  • Re: Issue 2222 in lilypond: lilypond-book fails with html input, lilypond, 13:35
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 13:32
  • Re: Issue 2228 in lilypond: Some users prefer to minimize partial beams rather than beam by the beat, Carl Sorensen, 13:12
  • Re: Issue 2228 in lilypond: Some users prefer to minimize partial beams rather than beam by the beat, Graham Percival, 12:05
  • Re: Issue 2228 in lilypond: Some users prefer to minimize partial beams rather than beam by the beat, lilypond, 11:48
  • Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers, Carl Sorensen, 10:45
  • Re: Issue 2222 in lilypond: lilypond-book fails with html input, lilypond, 10:11
  • Issue 2232 in lilypond: (de)crescendo terminated with (de)crescendo doesn't afftect midi volume, lilypond, 10:07
  • Re: (de)crescendo terminated with (de)crescendo doesn't afftect midi volume, James, 10:07
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 09:59
  • (de)crescendo terminated with (de)crescendo doesn't afftect midi volume, PrzemysławPawełczyk, 09:05
  • Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers, Martin Straeten, 08:07
  • Re: Issue 2228 in lilypond: Some users prefer to minimize partial beams rather than beam by the beat, lilypond, 06:32
  • Re: Issue 2229 in lilypond: Patch: Broadcast articulations not in EventChord, lilypond, 06:28
  • Re: Issue 2224 in lilypond: LM: clickable examples in the docs have stopped working., lilypond, 05:58
  • Re: Issue 2222 in lilypond: lilypond-book fails with html input, lilypond, 05:54
  • Re: Issue 2228 in lilypond: Some users prefer to minimize partial beams rather than beam by the beat, lilypond, 05:50
  • Re: Issue 2231 in lilypond: Tuplet bracket makes space for dynamic but dynamic is placed underneath bracket, lilypond, 05:46
  • Re: Issue 2229 in lilypond: Patch: Broadcast articulations not in EventChord, lilypond, 05:41
• January 18, 2012
  • Re: Issue 2231 in lilypond: Tuplet bracket makes space for dynamic but dynamic is placed underneath bracket, lilypond, 23:02
  • Re: Issue 2228 in lilypond: Some users prefer to minimize partial beams rather than beam by the beat, lilypond, 22:53
  • Re: Issue 2231 in lilypond: Tuplet bracket makes space for dynamic but dynamic is placed underneath bracket, lilypond, 22:46
  • Re: Issue 2224 in lilypond: LM: clickable examples in the docs have stopped working., lilypond, 19:30
  • Re: Issue 2223 in lilypond: Regtest for lilypond-book are not running, lilypond, 19:26
  • Re: Issue 2222 in lilypond: lilypond-book fails with html input, lilypond, 19:22
  • Re: Issue 2224 in lilypond: LM: clickable examples in the docs have stopped working., lilypond, 19:18
  • Re: Issue 2222 in lilypond: lilypond-book fails with html input, lilypond, 19:14
  • Re: Issue 2228 in lilypond: Some users prefer to minimize partial beams rather than beam by the beat, lilypond, 14:05
  • Re: Issue 2228 in lilypond: Some users prefer to minimize partial beams rather than beam by the beat, lilypond, 13:27
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 12:25
  • Re: Issue 2231 in lilypond: Tuplet bracket makes space for dynamic but dynamic is placed underneath bracket, lilypond, 10:59
  • Re: Tuplet Bracket Spacing Bug, James, 10:51
  • Issue 2231 in lilypond: Tuplet bracket makes space for dynamic but dynamic is placed underneath bracket, lilypond, 10:51
  • Re: verbose does not work when invoked as -d option, Neil Puttock, 10:23
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 09:15
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 09:11
  • Issue 2230 in lilypond: add svg regtests, lilypond, 09:07
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 09:03
  • Re: Issue 2229 in lilypond: Patch: Broadcast articulations not in EventChord, lilypond, 08:59
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 08:55
  • Re: Issue 2223 in lilypond: Regtest for lilypond-book are not running, lilypond, 08:51
  • Re: Issue 2223 in lilypond: Regtest for lilypond-book are not running, lilypond, 08:47
  • Re: Issue 2219 in lilypond: Set makeinfo and texi2html error limit to zero, lilypond, 08:43
  • Re: Issue 1010 in lilypond: extract_texi_filenames misses special node names, lilypond, 08:39
  • Re: Issue 2219 in lilypond: Set makeinfo and texi2html error limit to zero, lilypond, 08:35
  • Re: Issue 2229 in lilypond: Patch: Broadcast articulations not in EventChord, lilypond, 08:31
  • Re: Issue 2219 in lilypond: Set makeinfo and texi2html error limit to zero, lilypond, 08:27
  • Re: Issue 2219 in lilypond: Set makeinfo and texi2html error limit to zero, lilypond, 08:04
  • Re: Issue 2229 in lilypond: Patch: Broadcast articulations not in EventChord, address@hidden, 07:43
  • Re: Issue 2229 in lilypond: Patch: Broadcast articulations not in EventChord, lilypond, 07:42
  • Re: Issue 2229 in lilypond: Patch: Broadcast articulations not in EventChord, lilypond, 07:28
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 07:04
  • Re: Issue 2229 in lilypond: Patch: Broadcast articulations not in EventChord, lilypond, 07:00
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 06:44
  • Re: Issue 2229 in lilypond: Patch: Broadcast articulations not in EventChord, lilypond, 06:40
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 06:36
  • Re: Issue 2229 in lilypond: Patch: Broadcast articulations not in EventChord, lilypond, 06:32
  • Re: Issue 2229 in lilypond: Patch: Broadcast articulations not in EventChord, lilypond, 06:28
  • Re: Issue 1985 in lilypond: musicxml2ly: group-symbol none leads to bus error, lilypond, 06:24
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 04:09
  • Re: Issue 2205 in lilypond: Breathing sign is positioned incorrectly after changing Staff or TabStaff size, lilypond, 02:42
  • Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse, lilypond, 02:33
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 02:28
  • Re: Issue 2180 in lilypond: beams are detached from stems, lilypond, 02:24
• January 17, 2012
  • Tuplet Bracket Spacing Bug, Jay Anderson, 22:52
  • Re: Issue 2225 in lilypond: Patch: Docs: Explain the difference between ritardando and rallentando, lilypond, 22:20
  • Re: Issue 2180 in lilypond: beams are detached from stems, lilypond, 22:16
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 22:12
  • Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse, lilypond, 22:08
  • Re: Issue 2224 in lilypond: LM: clickable examples in the docs have stopped working., lilypond, 20:04
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 18:51
  • Re: Issue 2219 in lilypond: Set makeinfo and texi2html error limit to zero, lilypond, 18:18
  • Re: Issue 2219 in lilypond: Set makeinfo and texi2html error limit to zero, lilypond, 18:14
  • Re: Issue 2220 in lilypond: Undefined references to node in translated manuals, lilypond, 18:10
  • Re: Issue 856 in lilypond: links in Snippets appear to not work for snippets in multiple categories, lilypond, 18:06
  • Re: Issue 1010 in lilypond: extract_texi_filenames misses special node names, lilypond, 18:02
  • Re: Issue 1985 in lilypond: musicxml2ly: group-symbol none leads to bus error, lilypond, 13:36
  • Re: Issue 2229 in lilypond: Patch: Broadcast articulations not in EventChord, lilypond, 12:25
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 12:21
  • Issue 2229 in lilypond: Patch: Broadcast articulations not in EventChord, lilypond, 12:17
  • Re: Issue 2164 in lilypond: Learning Manual: Better explanation with updated example for \once tweak, lilypond, 11:54
  • Re: Issue 2167 in lilypond: Patch: Doc: selective point and click, lilypond, 11:07
  • Re: Issue 1935 in lilypond: Doc: internal ledger lines need to be documented in NR, lilypond, 10:52
  • Re: Issue 2137 in lilypond: Patch: Doc: NR improve 'visibility' of 'q' operation, lilypond, 10:37
  • Re: Issue 2093 in lilypond: Doc: NR alternativeNumberingStyle (fix issue 2059) needs to be documented, lilypond, 10:32
  • Re: Issue 2163 in lilypond: Web: Added 'Ripple' to easier-editing section, lilypond, 10:26
  • Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers, Carl Sorensen, 07:55
  • Re: Issue 1629 in lilypond: Tuplet line collides with fingering, lilypond, 07:45
  • Re: Issue 2198 in lilypond: Document use of PATH statement in Windows, lilypond, 07:25
  • Re: Issue 2211 in lilypond: illogical placement of the the Note in AU: -e,--evaluate section, lilypond, 07:14
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 06:55
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 06:02
  • Re: Issue 2213 in lilypond: Update documentation for \footnotes in Notation Reference, lilypond, 05:51
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 05:47
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 05:30
• January 16, 2012
  • Re: Issue 2180 in lilypond: beams are detached from stems, lilypond, 20:21
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 20:17
  • Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers, Carl Sorensen, 19:54
  • Re: Issue 2228 in lilypond: Patch: Fix beaming-pattern for compound meters, lilypond, 19:50
  • Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers, Carl Sorensen, 19:09
  • Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers, Janek Warchoł, 17:41
  • Re: Issue 2070 in lilypond: Patch: Don't wrap EventChord around rhythmic events by default., lilypond, 16:51
  • Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers, Carl Sorensen, 16:19
  • Re: verbose does not work when invoked as -d option, -Eluze, 16:04
  • Re: Issue 2213 in lilypond: Update documentation for \footnotes in Notation Reference, lilypond, 15:54
  • Re: verbose does not work when invoked as -d option, Ralph Palmer, 15:18
  • Re: Issue 2228 in lilypond: Patch: Fix beaming-pattern for compound meters, lilypond, 15:17
  • Re: Issue 2228 in lilypond: Patch: Fix beaming-pattern for compound meters, lilypond, 14:59
  • Issue 2228 in lilypond: Patch: Fix beaming-pattern for compound meters, lilypond, 14:54
  • Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers, Carl Sorensen, 13:25
  • Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers, Carl Sorensen, 13:09
  • Re: Issue 2227 in lilypond: Patch: changes.tely: mention Flag changes, remove duplicate "does", lilypond, 12:37
  • Re: Issue 2225 in lilypond: Patch: Docs: Explain the difference between ritardando and rallentando, lilypond, 12:33
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 12:29
  • Re: Issue 2200 in lilypond: Dots shouldn't always be placed in one column, lilypond, 12:25
  • Re: Issue 2217 in lilypond: Chord names collide with notes (vertical space missing on second line staff), lilypond, 10:27
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 09:45
  • Re: Issue 2180 in lilypond: beams are detached from stems, lilypond, 09:12
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 08:49
  • Re: Issue 2180 in lilypond: beams are detached from stems, lilypond, 08:45
  • Re: Issue 2180 in lilypond: beams are detached from stems, lilypond, 03:43
  • Re: Issue 2200 in lilypond: Dots shouldn't always be placed in one column, lilypond, 03:16
  • Re: Issue 2200 in lilypond: Dots shouldn't always be placed in one column, lilypond, 02:46
  • Re: Issue 2180 in lilypond: beams are detached from stems, lilypond, 02:14
  • Re: Issue 2209 in lilypond: lilypond-book creates uncompilable latex files (windows), lilypond, 01:49
  • Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved., lilypond, 01:45
  • Re: Issue 2210 in lilypond: Patch: Build: Top-level GNUmakefile, lilypond, 01:41
  • Re: Issue 2226 in lilypond: Patch: Docs: Explain the difference between ritardando and rallentando, lilypond, 00:51
  • Re: Issue 2225 in lilypond: Patch: Docs: Explain the difference between ritardando and rallentando, lilypond, 00:47
• January 15, 2012
  • Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved., lilypond, 23:40
  • Re: Issue 2209 in lilypond: lilypond-book creates uncompilable latex files (windows), lilypond, 23:35
  • Re: Issue 2210 in lilypond: Patch: Build: Top-level GNUmakefile, lilypond, 23:31
  • Re: Issue 1700 in lilypond: Chord names collide when several note-columns lay in between, lilypond, 20:10
  • Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers, Carl Sorensen, 20:04
  • Issue 2227 in lilypond: Patch: changes.tely: mention Flag changes, remove duplicate "does", lilypond, 19:44
  • Re: Issue 2226 in lilypond: Patch: Docs: Explain the difference between ritardando and rallentando, lilypond, 19:40
  • Issue 2226 in lilypond: Patch: Docs: Explain the difference between ritardando and rallentando, lilypond, 19:32
  • Issue 2225 in lilypond: Patch: Docs: Explain the difference between ritardando and rallentando, lilypond, 18:54
  • Re: Issue 2205 in lilypond: Breathing sign is positioned incorrectly after changing Staff or TabStaff size, lilypond, 17:36
  • Re: Issue 2214 in lilypond: "fatal error" reported when version is too old but correct output is still generated, Janek Warchoł, 17:20
  • Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers, Janek Warchoł, 17:07
  • wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers, Martin Straeten, 16:51
  • Re: Issue 1933 in lilypond: Lilypond-book subprocess doesn't work on mingw, lilypond, 12:45
  • Re: Issue 2224 in lilypond: LM: clickable examples in the docs have stopped working., lilypond, 12:41
  • Re: Clickable examples in the docs, James, 12:37
  • Issue 2224 in lilypond: LM: clickable examples in the docs have stopped working., lilypond, 12:37
  • Re: Issue 2206 in lilypond: Patch: Let \footnote do the job of \footnote, \footnoteGrob, \autoFootnote and \autoFootnoteGrob, David Kastrup, 10:48
  • Re: Issue 2028 in lilypond: Make doc always recreates HTML files, lilypond, 10:31
  • Re: Issue 2206 in lilypond: Patch: Let \footnote do the job of \footnote, \footnoteGrob, \autoFootnote and \autoFootnoteGrob, Colin Campbell, 10:31
  • verbose does not work when invoked as -d option, -Eluze, 10:29
  • Re: Issue 2158 in lilypond: Patch: Sketch of not remaking html files, lilypond, 10:27
  • Re: Issue 2028 in lilypond: Make doc always recreates HTML files, lilypond, 10:23
  • Re: Issue 2213 in lilypond: Update documentation for \footnotes in Notation Reference, lilypond, 10:19
  • Re: Issue 2206 in lilypond: Patch: Let \footnote do the job of \footnote, \footnoteGrob, \autoFootnote and \autoFootnoteGrob, lilypond, 10:15
  • Re: Issue 2206 in lilypond: Patch: Let \footnote do the job of \footnote, \footnoteGrob, \autoFootnote and \autoFootnoteGrob, lilypond, 10:11
  • Re: Issue 2206 in lilypond: Patch: Let \footnote do the job of \footnote, \footnoteGrob, \autoFootnote and \autoFootnoteGrob, lilypond, 10:07
  • Re: Issue 2158 in lilypond: Patch: Sketch of not remaking html files, lilypond, 09:39
  • Re: Issue 2158 in lilypond: Patch: Sketch of not remaking html files, lilypond, 09:35
  • Re: Issue 1700 in lilypond: Chord names collide when several note-columns lay in between, lilypond, 08:36
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 07:40
• January 14, 2012
  • Re: Issue 2222 in lilypond: lilypond-book fails with html input, lilypond, 20:55
  • Re: Issue 2223 in lilypond: Regtest for lilypond-book are not running, lilypond, 20:51
  • Issue 2223 in lilypond: Regtest for lilypond-book are not running, lilypond, 20:47
  • Issue 2222 in lilypond: lilypond-book fails with html input, lilypond, 20:43
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 17:48
  • Re: Issue 2139 in lilypond: Doc AU: command line options - where to use equal signs in short and long term definitions, lilypond, 17:17
  • Re: Issue 2215 in lilypond: lost commits jan 7, lilypond, 16:39
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 14:21
  • Re: Issue 1964 in lilypond: lilydev 2.0, lilypond, 12:16
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 11:45
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 11:37
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 10:57
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 10:39
  • Re: Issue 2215 in lilypond: lost commits jan 7, lilypond, 10:26
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 10:07
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 08:18
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 08:13
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 08:00
  • Re: Issue 2122 in lilypond: Regression in chord-name-exceptions.ly - badly spaced chord names, lilypond, 07:29
  • Re: Issue 2079 in lilypond: website links to 2.13, lilypond, 06:23
  • Re: Issue 2139 in lilypond: Doc AU: command line options - where to use equal signs in short and long term definitions, lilypond, 06:16
  • Re: Issue 2211 in lilypond: illogical placement of the the Note in AU: -e,--evaluate section, lilypond, 06:04
  • Re: Issue 2122 in lilypond: Regression in chord-name-exceptions.ly - badly spaced chord names, lilypond, 06:00
  • Re: Wrong placement of BreathingSign, Janek Warchoł, 04:30
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 04:22
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 04:18
  • Re: Issue 2215 in lilypond: lost commits jan 7, lilypond, 00:42
  • Re: Issue 2215 in lilypond: lost commits jan 7, lilypond, 00:25
• January 13, 2012
  • Re: Issue 1412 in lilypond: programming error: Going back in MIDI time, lilypond, 22:56
  • Re: Issue 2084 in lilypond: script-accidental avoidance fails for articulations, lilypond, 19:04
  • Re: Issue 2122 in lilypond: Regression in chord-name-exceptions.ly - badly spaced chord names, lilypond, 19:00
  • Re: Issue 1947 in lilypond: Stem Tremoli for double-stemmed notes are too short on the right side., lilypond, 18:49
  • Re: Issue 2059 in lilypond: Bar numbering of alternatives, lilypond, 18:45
  • Re: Issue 2123 in lilypond: Patch: Gets cross-staff collisions right for beams., lilypond, 18:41
  • Re: Issue 2153 in lilypond: piano pedal bracket should stop at requested moment, lilypond, 18:37
  • Re: Issue 1412 in lilypond: programming error: Going back in MIDI time, lilypond, 18:33
  • Re: Issue 695 in lilypond: slurs may take too much vertical extent, lilypond, 13:14
  • Re: Problem with convert-ly, Francisco Vila, 12:51
  • Re: Problem with convert-ly, Francisco Vila, 12:24
  • Re: Problem with convert-ly, Julien Rioux, 12:01
  • Problem with convert-ly, Francisco Vila, 10:44
  • Re: Issue 2125 in lilypond: Patch: Build: Don't rebuild everythingeach time unless necessary., Phil Holmes, 10:38
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 10:34
  • Re: Issue 2158 in lilypond: Patch: Sketch of not remaking html files, lilypond, 09:37
  • Re: Issue 2220 in lilypond: Undefined references to node in translated manuals, lilypond, 09:21
  • Re: Issue 2221 in lilypond: Duplicate node errors in snippets, lilypond, 09:17
  • Re: Issue 2198 in lilypond: Document use of PATH statement in Windows, lilypond, 09:06
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 07:59
  • Re: Issue 2198 in lilypond: Document use of PATH statement in Windows, lilypond, 07:47
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 07:41
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 07:36
  • Re: Issue 2191 in lilypond: Web: update to version 2.15, use it in the "site:" part, lilypond, 06:57
  • Re: Issue 2198 in lilypond: Document use of PATH statement in Windows, lilypond, 06:50
  • Re: Issue 2218 in lilypond: Web: Added Concert to Introduction.itexi, lilypond, 06:46
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 03:44
  • Re: internal LilyPond functions instead of -d options, -Eluze, 03:43
  • Re: Issue 2200 in lilypond: Dots shouldn't always be placed in one column, lilypond, 03:40
  • Re: Issue 2220 in lilypond: Undefined references to node in translated manuals, lilypond, 03:36
  • Re: Issue 2180 in lilypond: beams are detached from stems, lilypond, 03:22
  • Re: Issue 2218 in lilypond: Web: Added Concert to Introduction.itexi, lilypond, 03:18
  • Re: Issue 2221 in lilypond: Duplicate node errors in snippets, lilypond, 03:14
  • Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse, lilypond, 03:10
  • Re: Issue 2215 in lilypond: lost commits jan 7, lilypond, 03:06
  • Re: Issue 2215 in lilypond: lost commits jan 7, lilypond, 03:02
  • Re: Issue 2215 in lilypond: lost commits jan 7, lilypond, 02:55
  • Re: Issue 2191 in lilypond: Web: update to version 2.15, use it in the "site:" part, lilypond, 02:51
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 02:46
  • Re: Issue 2200 in lilypond: Dots shouldn't always be placed in one column, lilypond, 02:42
  • Re: Issue 2180 in lilypond: beams are detached from stems, lilypond, 02:38
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 02:34
  • Re: Issue 2204 in lilypond: Patch: Gets rid of PostScript in bar-chords-notation-for-guitar--with-text-spanner.ly, lilypond, 02:30
  • Re: Issue 2220 in lilypond: Undefined references to node in translated manuals, lilypond, 01:11
  • Re: Issue 2221 in lilypond: Duplicate node errors in snippets, lilypond, 01:07
  • Re: Issue 2221 in lilypond: Duplicate node errors in snippets, lilypond, 01:03
  • Re: Issue 2220 in lilypond: Undefined references to node in translated manuals, lilypond, 00:59
  • Re: Issue 2219 in lilypond: Set makeinfo and texi2html error limit to zero, lilypond, 00:55
  • Issue 2221 in lilypond: Duplicate node errors in snippets, lilypond, 00:51
  • Issue 2220 in lilypond: Undefined references to node in translated manuals, lilypond, 00:47
  • Re: Issue 2219 in lilypond: Set makeinfo and texi2html error limit to zero, lilypond, 00:43
  • Issue 2219 in lilypond: Set makeinfo and texi2html error limit to zero, lilypond, 00:39
  • Re: Issue 2125 in lilypond: Patch: Build: Don't rebuild everything each time unless necessary., lilypond, 00:32
• January 12, 2012
  • Re: Issue 2158 in lilypond: Patch: Sketch of not remaking html files, lilypond, 22:07
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 22:03
  • Re: Issue 2198 in lilypond: Document use of PATH statement in Windows, lilypond, 21:59
  • Re: Issue 2203 in lilypond: Patch: separate narrowed accidentals, lilypond, 21:55
  • Re: Issue 2204 in lilypond: Patch: Gets rid of PostScript in bar-chords-notation-for-guitar--with-text-spanner.ly, lilypond, 21:51
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 19:54
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 19:13
  • Re: Issue 2191 in lilypond: Web: update to version 2.15, use it in the "site:" part, lilypond, 14:47
  • Re: Production with LilyPond, James, 14:44
  • Issue 2218 in lilypond: Web: Added Concert to Introduction.itexi, lilypond, 14:43
  • Re: Issue 2214 in lilypond: "fatal error" reported when version is too old but correct output is still generated, -Eluze, 12:05
  • Re: Chord names collide with notes (vertical space missing on second line staff), Ralph Palmer, 10:29
  • Issue 2217 in lilypond: Chord names collide with notes (vertical space missing on second line staff), lilypond, 10:28
  • Re: internal LilyPond functions instead of -d options, Ralph Palmer, 10:19
  • Issue 2216 in lilypond: add the internal functions to the "Application Usage" manual, lilypond, 10:16
  • Re: Issue 2214 in lilypond: "fatal error" reported when version is too old but correct output is still generated, Graham Percival, 09:12
  • Re: Issue 2214 in lilypond: "fatal error" reported when version is too old but correct output is still generated, -Eluze, 05:29
  • Re: Issue 695 in lilypond: slurs may take too much vertical extent, lilypond, 04:04
  • Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse, lilypond, 04:00
  • Re: Issue 695 in lilypond: slurs may take too much vertical extent, lilypond, 03:56
  • Re: Issue 2180 in lilypond: beams are detached from stems, lilypond, 02:48
  • Re: Issue 1405 in lilypond: Web: website Google search-bar should allow to search the website., lilypond, 02:33
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 02:29
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 02:25
  • Re: Issue 2099 in lilypond: error in doc build should point to build/Documentation/out-www/DocName.log, lilypond, 02:21
  • Re: Issue 2209 in lilypond: lilypond-book creates uncompilable latex files (windows), lilypond, 02:17
  • Re: Issue 2210 in lilypond: Patch: Build: Top-level GNUmakefile, lilypond, 02:13
  • Re: Issue 2125 in lilypond: Patch: Build: Don't rebuild everything each time unless necessary., lilypond, 02:09
  • Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved., lilypond, 02:05
  • Re: Issue 2206 in lilypond: Patch: Let \footnote do the job of \footnote, \footnoteGrob, \autoFootnote and \autoFootnoteGrob, lilypond, 02:01
  • Re: Issue 2184 in lilypond: GUB can't download netpbm, lilypond, 01:48
  • Issue 2215 in lilypond: lost commits jan 7, lilypond, 01:39
  • Re: Production with LilyPond, Graham Percival, 01:37
  • Re: Issue 2156 in lilypond: lost commits, lilypond, 01:35
  • Re: Issue 2214 in lilypond: "fatal error" reported when version is too old but correct output is still generated, lilypond, 00:42
• January 11, 2012
  • Re: Issue 2180 in lilypond: beams are detached from stems, Keith OHara, 22:13
  • Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse, lilypond, 21:56
  • Issue 2214 in lilypond: "fatal error" reported when version is too old but correct output is still generated, lilypond, 21:52
  • Re: "fatal error" when output is correctly displayed?!, Brett McCoy, 21:52
  • Re: Issue 1861 in lilypond: DynamicText attached to spacer rest not correctly aligned, lilypond, 21:48
  • Re: Issue 695 in lilypond: slurs may take too much vertical extent, lilypond, 21:44
  • Re: Issue 2166 in lilypond: Copy pdf docs to new website folder, lilypond, 20:40
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 19:08
  • Re: make doc-stage-1 barfs, Ian Hulin, 17:52
  • Re: make doc-stage-1 barfs, Julien Rioux, 16:49
  • Re: Status of break-align-symbol vs. break-align-symbols, Neil Puttock, 16:11
  • Re: Status of break-align-symbol vs. break-align-symbols, Robin Bannister, 16:04
  • make doc-stage-1 barfs, Ian Hulin, 15:59
  • Re: Issue 2180 in lilypond: beams are detached from stems, lilypond, 14:06
  • Re: Issue 1861 in lilypond: DynamicText attached to spacer rest not correctly aligned, lilypond, 14:02
  • Re: Issue 695 in lilypond: slurs may take too much vertical extent, lilypond, 13:31
  • Re: Issue 1597 in lilypond: Windows install can cause PATH to overflow, lilypond, 13:24
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 13:20
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 13:09
  • Re: Issue 1405 in lilypond: Web: website Google search-bar should allow to search the website., lilypond, 12:24
  • Re: Issue 2180 in lilypond: beams are detached from stems, lilypond, 12:16
  • Re: Issue 2193 in lilypond: collision between beams and flags, lilypond, 12:12
  • Re: Issue 1597 in lilypond: Windows install can cause PATH to overflow, lilypond, 12:04
  • Re: Issue 857 in lilypond: translations status html->texinfo, lilypond, 12:00
  • Re: Issue 2206 in lilypond: Patch: Let \footnote do the job of \footnote, \footnoteGrob, \autoFootnote and \autoFootnoteGrob, lilypond, 09:57
  • Re: Issue 2213 in lilypond: Update documentation for \footnotes in Notation Reference, lilypond, 09:53
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 09:48
  • Re: Issue 2125 in lilypond: Patch: Build: Don't rebuild everything each time unless necessary., lilypond, 09:44
  • Re: Issue 2125 in lilypond: Patch: Build: Don't rebuild everything each time unless necessary., lilypond, 09:40
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 09:36
  • Re: Issue 2193 in lilypond: collision between beams and flags, lilypond, 09:32
  • Re: Issue 1907 in lilypond: accidentals in chordNames have diffferent vertical alignment depending on language, lilypond, 09:28
  • Re: Issue 2209 in lilypond: lilypond-book creates uncompilable latex files (windows), lilypond, 09:02
  • Re: Issue 1964 in lilypond: lilydev 2.0, lilypond, 07:53
  • Re: Issue 2203 in lilypond: Patch: separate narrowed accidentals, lilypond, 07:41
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 07:02
  • "fatal error" when output is correctly displayed?!, -Eluze, 06:57
  • Re: Issue 2175 in lilypond: Patch: explain how to add git-cl to PATH, lilypond, 06:47
  • Issue 2213 in lilypond: Update documentation for \footnotes in Notation Reference, lilypond, 06:42
  • Re: Issue 1788 in lilypond: auto numbering footnote checkin doesn't play with \null and \musicglyph, lilypond, 06:29
  • Re: Production with LilyPond, Janek Warchoł, 06:20
  • Re: Issue 2206 in lilypond: Patch: Let \footnote do the job of \footnote, \footnoteGrob, \autoFootnote and \autoFootnoteGrob, lilypond, 06:15
  • Re: Status of break-align-symbol vs. break-align-symbols, Robin Bannister, 04:41
  • Re: Issue 2203 in lilypond: Patch: separate narrowed accidentals, lilypond, 04:18
  • Re: Issue 2090 in lilypond: Add documentation for command line quoting on Windows, lilypond, 03:54
  • Re: Issue 2203 in lilypond: Patch: separate narrowed accidentals, lilypond, 03:10
  • Re: Issue 737 in lilypond: Enhancement: support for footnotes and/or endnotes., lilypond, 02:46
  • Re: Issue 2203 in lilypond: Patch: separate narrowed accidentals, lilypond, 02:42
  • Re: Issue 1661 in lilypond: MIDI dynamics take effect one note too late, lilypond, 01:32
  • Re: Issue 2002 in lilypond: Enhancement: Add \hideNote function for hiding single notes only, lilypond, 01:28
  • Re: Issue 2003 in lilypond: Patch: Implement \once as music function able to operate on complex stuff., lilypond, 01:24
  • Re: Issue 2209 in lilypond: lilypond-book creates uncompilable latex files (windows), lilypond, 01:09
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 01:03
  • Re: Production with LilyPond, Graham Percival, 00:59
  • Re: Issue 2098 in lilypond: Patch: Now use astyle 2.02.1, lilypond, 00:57
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 00:42
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 00:26
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 00:17
• January 10, 2012
  • Re: Issue 2203 in lilypond: Patch: separate narrowed accidentals, lilypond, 23:49
  • Re: Issue 2175 in lilypond: Patch: explain how to add git-cl to PATH, lilypond, 23:45
  • Re: Issue 1906 in lilypond: Build fails on Fedora, lilypond, 21:13
  • Re: Issue 2175 in lilypond: Patch: explain how to add git-cl to PATH, lilypond, 21:06
  • Re: Issue 2183 in lilypond: Patch: hideNotes should also hide rests..., lilypond, 21:02
  • Re: Issue 2191 in lilypond: Web: update to version 2.15, use it in the "site:" part, lilypond, 20:25
  • Issue 2212 in lilypond: WEB: change search to stable and development (see T2191), lilypond, 20:21
  • Re: Issue 2193 in lilypond: collision between beams and flags, lilypond, 20:15
  • Re: Chord names collide with notes (vertical space missing on second line staff), Carl Sorensen, 19:56
  • Re: Issue 2090 in lilypond: Add documentation for command line quoting on Windows, lilypond, 18:19
  • Issue 2211 in lilypond: illogical placement of the the Note in AU: -e,--evaluate section, lilypond, 18:15
  • Re: Issue 2209 in lilypond: lilypond-book creates uncompilable latex files (windows), lilypond, 17:58
  • Re: Issue 2210 in lilypond: Patch: Build: Top-level GNUmakefile, lilypond, 17:54
  • Issue 2210 in lilypond: Patch: Build: Top-level GNUmakefile, lilypond, 17:50
  • Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved., lilypond, 17:46
  • Re: Issue 2209 in lilypond: lilypond-book creates uncompilable latex files (windows), lilypond, 17:42
  • Re: Issue 2209 in lilypond: lilypond-book creates uncompilable latex files (windows), lilypond, 17:38
  • Re: Issue 2104 in lilypond: Patch: Fix .dep file from lilypond-book when include paths are involved., lilypond, 16:58
  • Re: Issue 2203 in lilypond: Patch: separate narrowed accidentals, lilypond, 16:54
  • Re: Issue 2203 in lilypond: Patch: separate narrowed accidentals, lilypond, 16:50
  • Issue 2209 in lilypond: lilypond-book creates uncompilable latex files (windows), lilypond, 16:46
  • Re: Issue 2127 in lilypond: Patch: Directs output of texi2html to log files (GOP 9), lilypond, 16:28
  • Re: Issue 1906 in lilypond: Build fails on Fedora, lilypond, 16:23
  • Re: Issue 2028 in lilypond: Make doc always recreates HTML files, lilypond, 16:19
  • Re: Issue 2158 in lilypond: Patch: Sketch of not remaking html files, lilypond, 16:15
  • Re: Issue 1906 in lilypond: Build fails on Fedora, lilypond, 16:11
  • Re: Issue 1917 in lilypond: Hyperlinks in web-big-page.html do not work, lilypond, 16:07
  • Re: Issue 1927 in lilypond: 2.15.2 doesn't build anymore on Mageia, lilypond, 16:03
  • Re: Issue 1700 in lilypond: Chord names collide when several note-columns lay in between, lilypond, 12:52
  • Chord names collide with notes (vertical space missing on second line staff), Jean-Alexis Montignies, 12:05
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 11:36
  • Re: Production with LilyPond, Xavier Scheuer, 11:03
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 10:01
  • Production with LilyPond, Aurélien Bello, 09:48
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, mike, 09:26
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 09:14
  • Re: Issue 1700 in lilypond: Chord names collide when several note-columns lay in between, lilypond, 07:47
  • Re: Hairpin #'minimum-length does not apply to real length of the hairpin, James, 04:24
  • Re: Issue 2090 in lilypond: Add documentation for command line quoting on Windows, lilypond, 04:16
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 04:05
  • Re: Issue 2206 in lilypond: Patch: Let \footnote do the job of \footnote, \footnoteGrob, \autoFootnote and \autoFootnoteGrob, lilypond, 04:01
  • Re: Issue 2090 in lilypond: Add documentation for command line quoting on Windows, lilypond, 03:03
• January 09, 2012
  • Re: Problem running midi2ly on Mac OS X 10.6.8, Hans Aberg, 18:07
  • Re: Issue 2205 in lilypond: Breathing sign is positioned incorrectly after changing Staff or TabStaff size, lilypond, 17:20
  • Issue 2208 in lilypond: Problem running midi2ly on Mac OS X 10.6.8 : 32- vs. 64-bit code, lilypond, 17:05
  • Re: Problem running midi2ly on Mac OS X 10.6.8, Ralph Palmer, 17:03
  • Issue 2207 in lilypond: Hairpin #'minimum-length does not apply to real length of the hairpin, lilypond, 17:01
  • Re: Hairpin #'minimum-length does not apply to real length of the hairpin, Ralph Palmer, 17:01
  • Issue 2206 in lilypond: Patch: Let \footnote do the job of \footnote, \footnoteGrob, \autoFootnote and \autoFootnoteGrob, lilypond, 15:30
  • Re: Issue 2136 in lilypond: Patch: Doc: Usage --include option layout consistency, lilypond, 12:00
  • internal LilyPond functions instead of -d options, -Eluze, 10:54
  • Re: Wrong placement of BreathingSign, James, 09:12
  • Re: Wrong placement of BreathingSign, Graham Percival, 08:04
  • Re: Wrong placement of BreathingSign, Neil Puttock, 07:37
  • Re: Wrong placement of BreathingSign, address@hidden, 07:35
  • Re: Wrong placement of BreathingSign, Neil Puttock, 07:34
  • Re: Wrong placement of BreathingSign, Neil Puttock, 07:27
  • Re: Wrong placement of BreathingSign, address@hidden, 07:24
  • Re: Wrong placement of BreathingSign, James, 07:20
  • Issue 2205 in lilypond: Breathing sign is positioned incorrectly after changing Staff or TabStaff size, lilypond, 07:19
  • Wrong placement of BreathingSign, Thomas Morley, 06:55
  • Re: Issue 2203 in lilypond: Patch: separate narrowed accidentals, lilypond, 01:53
  • Re: Issue 2203 in lilypond: Patch: separate narrowed accidentals, lilypond, 01:47
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 01:34
  • Re: Issue 2158 in lilypond: Patch: Sketch of not remaking html files, lilypond, 00:29
  • Re: Issue 2198 in lilypond: Document use of PATH statement in Windows, lilypond, 00:25
  • Re: Issue 2204 in lilypond: Patch: Gets rid of PostScript in bar-chords-notation-for-guitar--with-text-spanner.ly, lilypond, 00:21
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 00:17
  • Re: Issue 2189 in lilypond: Doc: NR add to \partial for clearer understanding, lilypond, 00:09
  • Re: Issue 2168 in lilypond: Patch: Fix a few more warnings in clang, lilypond, 00:04
  • Re: Issue 2167 in lilypond: Patch: Doc: selective point and click, lilypond, 00:00
• January 08, 2012
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 22:46
  • Re: Issue 2073 in lilypond: Patch: Allows for framing comments in LilyPond backends., lilypond, 22:35
  • Re: Issue 2116 in lilypond: Patch: Shows Flags in tabFullNotation, lilypond, 22:13
  • Re: Issue 2147 in lilypond: Patch: Fixes width of NR A.11 - List of special character, lilypond, 22:03
  • Re: Issue 2132 in lilypond: Patch: Sends woodwind regtest op to stderr, lilypond, 21:59
  • Re: Issue 1410 in lilypond: Rest in lower voice should be placed above notes in in upper if voices are crossed., lilypond, 21:55
  • Re: Issue 2085 in lilypond: Overriding stencil of StringNumber leads to "programming error" messages, lilypond, 21:39
  • Re: Issue 2113 in lilypond: Beamlet points the wrong way when tuplet sixteenths are beamed with eighths, lilypond, 21:35
  • Re: Issue 2094 in lilypond: spacing-measure-length.ly regtest has time sig overlaying rest, lilypond, 21:31
  • Re: Issue 1875 in lilypond: tests for flower appear to miss instantiations of classes, lilypond, 21:24
  • Re: Issue 2138 in lilypond: Patch: Doc: NR @knownissues for #'ignore-collision, lilypond, 20:21
  • Re: Issue 1410 in lilypond: Rest in lower voice should be placed above notes in in upper if voices are crossed., lilypond, 20:17
  • Re: Issue 2057 in lilypond: Hairpin hits barline at line break, lilypond, 20:13
  • Re: Issue 2130 in lilypond: Hairpin hits barline at line break, lilypond, 20:09
  • Re: Issue 2102 in lilypond: vertical spacing of a nonstaff line below the system, lilypond, 20:00
  • Re: Issue 1968 in lilypond: test full GUB rebuild, lilypond, 19:47
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 19:06
  • Re: Issue 1906 in lilypond: Build fails on Fedora, lilypond, 19:02
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 17:14
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 17:08
  • Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 16:36
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 16:32
  • Re: Issue 2203 in lilypond: Patch: separate narrowed accidentals, lilypond, 16:28
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 16:22
  • Reorganize NR 1.3 Expressive marks, Xavier Scheuer, 16:08
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 16:08
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 16:02
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 15:57
  • Hairpin #'minimum-length does not apply to real length of the hairpin, Xavier Scheuer, 15:40
  • Issue 2204 in lilypond: Patch: Gets rid of PostScript in bar-chords-notation-for-guitar--with-text-spanner.ly, lilypond, 14:42
  • Re: Issue 2158 in lilypond: Patch: Sketch of not remaking html files, lilypond, 13:00
  • Re: PianoStaff, time and grace duplicates the time display, Xavier Scheuer, 12:26
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 11:34
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 10:52
  • Re: Issue 1361 in lilypond: Collision: TupletNumber and Script, lilypond, 10:41
  • Re: Issue 257 in lilypond: collision accent and tuplet bracket, lilypond, 10:37
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 10:33
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 10:21
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 10:08
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 10:03
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 08:55
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 08:13
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 07:51
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 07:47
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 07:14
  • Re: Issue 2190 in lilypond: Tuplet positioning on beamed notes is ugly, lilypond, 07:10
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 06:10
  • Re: Issue 2193 in lilypond: collision between beams and flags, lilypond, 05:52
  • Re: PianoStaff, time and grace duplicates the time display, Xavier Scheuer, 04:36
  • Re: Issue 2198 in lilypond: Document use of PATH statement in Windows, lilypond, 03:44
  • PianoStaff, time and grace duplicates the time display, Romain BEHAR, 03:40
  • Problem running midi2ly on Mac OS X 10.6.8, Owen Saxton, 02:35
  • Re: Issue 2203 in lilypond: Patch: separate narrowed accidentals, lilypond, 01:37
  • Re: Issue 1361 in lilypond: Collision: TupletNumber and Script, lilypond, 00:06
  • Re: Issue 257 in lilypond: collision accent and tuplet bracket, lilypond, 00:02
• January 07, 2012
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 23:16
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 23:12
  • Re: Issue 2193 in lilypond: collision between beams and flags, lilypond, 23:08
  • Re: Issue 2191 in lilypond: Web: update to version 2.15, use it in the "site:" part, lilypond, 23:04
  • Re: Issue 2198 in lilypond: Document use of PATH statement in Windows, lilypond, 22:41
  • Re: Issue 2191 in lilypond: Web: update to version 2.15, use it in the "site:" part, lilypond, 22:37
  • Re: Issue 2191 in lilypond: Web: update to version 2.15, use it in the "site:" part, lilypond, 22:33
  • Re: Issue 2203 in lilypond: Patch: separate narrowed accidentals, lilypond, 22:29
  • Re: Issue 1637 in lilypond: include newest version of Fontforge in Lilydev, lilypond, 20:50
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 20:46
  • Re: Issue 2203 in lilypond: Patch: separate narrowed accidentals, lilypond, 20:07
  • Issue 2203 in lilypond: Patch: separate narrowed accidentals, lilypond, 19:57
  • Re: Issue 1637 in lilypond: include newest version of Fontforge in Lilydev, lilypond, 18:25
  • Issue 2202 in lilypond: issues created by git-cl have status "new" instead of "started", lilypond, 18:21
  • Re: Issue 2175 in lilypond: Patch: explain how to add git-cl to PATH, lilypond, 18:17
  • Re: Issue 2160 in lilypond: document LILYPOND_WEB_MEDIA_GIT, lilypond, 18:13
  • Issue 2201 in lilypond: dots are sometimes placed too far from the notes, lilypond, 18:08
  • Issue 2200 in lilypond: Dots shouldn't always be placed in one column, lilypond, 18:04
  • Re: Issue 2190 in lilypond: Tuplet positioning on beamed notes is ugly, lilypond, 17:40
  • Re: Issue 2189 in lilypond: Doc: NR add to \partial for clearer understanding, lilypond, 16:13
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 16:09
  • Re: Issue 2198 in lilypond: Document use of PATH statement in Windows, lilypond, 16:05
  • Re: Engravers cannot be added at the StaffGroup level, Janek Warchoł, 14:51
  • Issue 2199 in lilypond: Engravers cannot be added at the StaffGroup level, lilypond, 14:51
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 14:15
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 13:21
  • Issue 2198 in lilypond: Document use of PATH statement in Windows, lilypond, 13:17
  • Engravers cannot be added at the StaffGroup level, Xavier Scheuer, 13:12
  • Re: Issue 2189 in lilypond: Doc: NR add to \partial for clearer understanding, lilypond, 12:20
  • Re: Issue 2193 in lilypond: collision between beams and flags, lilypond, 12:16
  • Issue 2197 in lilypond: collision between beams and rests, lilypond, 12:12
  • Re: Issue 2193 in lilypond: collision between beams and flags, lilypond, 12:08
  • Re: Issue 2193 in lilypond: collision between beams and flags, lilypond, 12:04
  • Re: Issue 2170 in lilypond: Patch: Updates makelsr to point to lilypond exe, lilypond, 11:34
  • Re: Issue 2189 in lilypond: Doc: NR add to \partial for clearer understanding, lilypond, 11:30
  • Re: Issue 2193 in lilypond: collision between beams and rests, lilypond, 11:21
  • Re: Issue 2193 in lilypond: collision between beams and rests, lilypond, 11:17
  • Re: Issue 2193 in lilypond: collision between beams and rests, lilypond, 11:13
  • Re: Issue 2189 in lilypond: Doc: NR add to \partial for clearer understanding, lilypond, 11:09
  • Re: Issue 2193 in lilypond: collision between beams and rests, lilypond, 11:05
  • Re: Issue 2193 in lilypond: collision between beams and rests, lilypond, 11:01
  • Re: Issue 2134 in lilypond: Redirect old website / download to new location, Graham Percival, 10:47
  • Re: Issue 2027 in lilypond: make website doesn't have dependencies, lilypond, 10:44
  • Re: Issue 2027 in lilypond: make website doesn't have dependencies, lilypond, 10:37
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, Graham Percival, 10:33
  • Re: Issue 2193 in lilypond: collision between beams and rests, lilypond, 10:23
  • Re: Issue 2193 in lilypond: collision between beams and rests, lilypond, 10:19
  • Re: Issue 2193 in lilypond: collision between beams and rests, lilypond, 10:14
  • Re: Issue 2134 in lilypond: Redirect old website / download to new location, lilypond, 09:55
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 09:16
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 06:34
  • Re: Issue 2196 in lilypond: collision of notehead and beams, lilypond, 06:27
  • Issue 2196 in lilypond: collision of notehead and beams, lilypond, 06:23
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 06:19
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 06:15
  • Re: Issue 2193 in lilypond: collision between beams and rests, lilypond, 06:08
  • Re: Issue 2193 in lilypond: collision between beams and rests, lilypond, 06:04
  • Re: Issue 2193 in lilypond: collision between beams and rests, lilypond, 06:00
  • Issue 2195 in lilypond: shorter beams for middle voices below rests, lilypond, 05:56
  • Re: Issue 2194 in lilypond: Beams from different voices collide, lilypond, 05:23
  • Issue 2194 in lilypond: beam-beam collision, lilypond, 04:21
  • Re: Issue 2192 in lilypond: tighter polyphony, lilypond, 03:11
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 03:05
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 02:59
  • Re: Issue 2192 in lilypond: tighter polyphony, -Eluze, 02:59
  • Re: Issue 2134 in lilypond: Redirect old website / download to new location, lilypond, 02:28
  • Issue 2193 in lilypond: collision between beams and rests, lilypond, 02:01
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 01:57
  • Issue 2192 in lilypond: tighter polyphony, lilypond, 01:53
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 01:43
  • Issue 2191 in lilypond: Web: update to version 2.15, use it in the "site:" part, lilypond, 01:39
  • Re: Issue 2134 in lilypond: Redirect old website / download to new location, lilypond, 01:34
• January 06, 2012
  • Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 23:46
  • Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 22:50
  • Re: Issue 2189 in lilypond: Doc: NR add to \partial for clearer understanding, lilypond, 22:46
  • Re: Issue 2188 in lilypond: Patch: Turns beam translation into a callback., lilypond, 22:42
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 21:53
  • Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 19:46
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, address@hidden, 17:44
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, Trevor Daniels, 16:49
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 16:14
  • Re: Tuplet positioning on beamed notes is ugly, Marek Klein, 15:45
  • Issue 2190 in lilypond: Tuplet positioning on beamed notes is ugly, lilypond, 15:43
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 15:25
  • Re: Issue 2189 in lilypond: Doc: NR add to \partial for clearer understanding, lilypond, 14:52
  • Re: Issue 2189 in lilypond: Doc: NR add to \partial for clearer understanding, lilypond, 14:01
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 13:51
  • Re: Issue 2187 in lilypond: git-cl doesn't 'always' remember (the last) tracker issue number you used, lilypond, 13:25
  • Issue 2189 in lilypond: Doc: NR add to \partial for clearer understanding, lilypond, 13:21
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 12:34
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 12:29
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 12:02
  • Re: Issue 2188 in lilypond: Patch: Turns beam translation into a callback., lilypond, 10:40
  • Re: Issue 2188 in lilypond: Patch: Turns beam translation into a callback., lilypond, 10:06
  • Re: Issue 2188 in lilypond: Patch: Turns beam translation into a callback., lilypond, 10:02
  • Issue 2188 in lilypond: Patch: Turns beam translation into a callback., lilypond, 09:36
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 08:53
  • Issue 2187 in lilypond: git-cl doesn't remember tracker issue number, lilypond, 08:47
  • Issue 2186 in lilypond: git-cl always uses first commit's message, lilypond, 08:42
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 08:37
  • Re: Issue 2184 in lilypond: GUB can't download netpbm, lilypond, 08:32
  • Re: Chord fingering placement bug?, Ralph Palmer, 08:25
  • Issue 2185 in lilypond: Chord fingering placement request, lilypond, 08:24
  • Issue 2184 in lilypond: GUB can't download netpbm, lilypond, 08:16
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, James, 07:49
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 07:43
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 07:17
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 07:12
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, mike, 06:24
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, Graham Percival, 06:14
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 06:08
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 05:40
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 05:21
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 05:17
  • Re: Issue 2175 in lilypond: Patch: explain how to add git-cl to PATH, lilypond, 05:13
  • Re: Issue 1629 in lilypond: Tuplet line collides with fingering, lilypond, 04:51
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., Graham Percival, 04:44
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 04:37
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 04:14
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 04:10
  • Re: Issue 2165 in lilypond: Patch: Modifies broken hairpin height, lilypond, 04:06
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 04:02
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 03:58
  • 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:37
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 02:33
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 02:20
  • Re: Issue 2183 in lilypond: Patch: hideNotes should also hide rests..., lilypond, 01:23
  • Re: Issue 1802 in lilypond: system-system-spacing in lilypond-book-file within a LaTeX file, lilypond, 01:19
  • Re: Issue 2093 in lilypond: Doc: NR alternativeNumberingStyle (fix issue 2059) needs to be documented, lilypond, 01:15
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 01:02
• January 05, 2012
  • Re: Issue 2180 in lilypond: beams are detached from stems, lilypond, 23:58
  • Re: Issue 2183 in lilypond: Patch: hideNotes should also hide rests..., lilypond, 22:43
  • Re: Issue 2169 in lilypond: Patch: Doc: Introduce Voices in the correct order. Mention that hideNotes hides beams, lilypond, 22:39
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 20:43
  • Re: Issue 2169 in lilypond: Patch: Doc: Introduce Voices in the correct order. Mention that hideNotes hides beams, lilypond, 20:39
  • Re: Issue 2167 in lilypond: Patch: Doc: selective point and click, lilypond, 20:37
  • Re: Issue 2168 in lilypond: Patch: Fix a few more warnings in clang, lilypond, 20:35
  • Re: Issue 2165 in lilypond: Patch: Modifies broken hairpin height, lilypond, 20:27
  • Re: Issue 2093 in lilypond: Doc: NR alternativeNumberingStyle (fix issue 2059) needs to be documented, lilypond, 20:23
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 20:19
  • Re: Issue 1802 in lilypond: system-system-spacing in lilypond-book-file within a LaTeX file, lilypond, 20:15
  • Issue 2183 in lilypond: Patch: hideNotes should also hide rests..., lilypond, 19:33
  • Re: Issue 2148 in lilypond: object outlines shouldn't be rectangular, lilypond, 18:07
  • Re: Chord fingering placement bug?, Ralph Palmer, 16:33
  • Issue 2182 in lilypond: Chord fingering placement bug?, lilypond, 16:33
  • Re: inconsistent handling of lilypond cmd with or wi thout -h when LANG=… is not en, Ralph Palmer, 16:27
  • Issue 2181 in lilypond: inconsistent handling of lil ypond cmd with or without -h when LANG=… is not en, lilypond, 16:27
  • Re: Issue 2152 in lilypond: Patch: Removes ugly side bars from learning, lilypond, 15:10
  • Re: Issue 2152 in lilypond: Patch: Removes ugly side bars from learning, lilypond, 12:50
  • Re: Issue 2180 in lilypond: beams are detached from stems, -Eluze, 08:37
  • Issue 2180 in lilypond: beams are detached from stems, lilypond, 05:22
  • Issue 2179 in lilypond: Improve warnings about spanners/lyrics etc. cannot be set from 'outside' to 'inside' << {...} \\ {...} >> constructs, lilypond, 00:57
• January 04, 2012
  • Re: Issue 2175 in lilypond: Patch: explain how to add git-cl to PATH, lilypond, 20:08
  • Re: Chord fingering placement bug?, Nick Payne, 19:10
  • Re: Issue 2160 in lilypond: document LILYPOND_WEB_MEDIA_GIT, lilypond, 18:54
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, Graham Percival, 18:43
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, Graham Percival, 18:41
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, Trevor Daniels, 18:07
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, Reinhold Kainhofer, 16:52
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, address@hidden, 16:48
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 16:07
  • Chord fingering placement bug?, Nick Payne, 15:59
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, address@hidden, 14:41
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, Keith OHara, 14:18
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 14:17
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 14:08
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, address@hidden, 13:15
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 13:11
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 13:07
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, Trevor Daniels, 12:53
  • Re: Issue 2152 in lilypond: Patch: Removes ugly side bars from learning, lilypond, 12:32
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 12:03
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 11:41
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 11:19
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 10:59
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 09:55
  • Re: Doc: Accidental style clarification, David Kastrup, 09:37
  • Re: Issue 2178 in lilypond: NR: clarify the subsection "Automatic accidentals" of section 1.1.3, lilypond, 09:12
  • Issue 2178 in lilypond: NR: clarify the subsection "Automatic accidentals" of section 1.1.3, lilypond, 09:08
  • Re: Doc: Accidental style clarification, James, 09:08
  • Doc: Accidental style clarification, Ole Vedel Villumsen, 08:56
  • Re: How to measure the code coverage of scheme part in Lilypond?, Kai Yu, 08:56
  • Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer., lilypond, 08:52
  • Re: Issue 2166 in lilypond: Copy pdf docs to new website folder, lilypond, 07:46
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 07:32
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 07:18
  • Re: Issue 2166 in lilypond: Copy pdf docs to new website folder, lilypond, 07:14
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 04:29
  • Re: Issue 2176 in lilypond: Move auto-beaming before the engraving stage., lilypond, 04:25
  • Re: Issue 2176 in lilypond: Move auto-beaming before the engraving stage., lilypond, 04:01
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 03:57
  • Re: Issue 1935 in lilypond: Doc: internal ledger lines need to be documented in NR, lilypond, 03:16
  • Re: Issue 2148 in lilypond: object outlines shouldn't be rectangular, lilypond, 03:12
  • Re: Issue 2164 in lilypond: Learning Manual: Better explanation with updated example for \once tweak, lilypond, 03:08
  • Re: Issue 2162 in lilypond: Patch: Doc: NR added @knownissue for beam properties, lilypond, 03:04
  • Re: Issue 2162 in lilypond: Patch: Doc: NR added @knownissue for beam properties, lilypond, 03:00
  • Re: Issue 2137 in lilypond: Patch: Doc: NR improve 'visibility' of 'q' operation, lilypond, 02:56
  • Issue 2176 in lilypond: Move auto-beaming before the engraving stage., lilypond, 02:35
  • Re: Issue 2148 in lilypond: object outlines shouldn't be rectangular, lilypond, 02:14
  • Re: Issue 2162 in lilypond: Patch: Doc: NR added @knownissue for beam properties, lilypond, 01:34
  • Re: Issue 2166 in lilypond: Copy pdf docs to new website folder, lilypond, 00:56
  • Re: Issue 2162 in lilypond: Patch: Doc: NR added @knownissue for beam properties, lilypond, 00:52
  • Re: Issue 2153 in lilypond: piano pedal bracket should stop at requested moment, lilypond, 00:48
  • Re: Issue 2158 in lilypond: Patch: Sketch of not remaking html files, lilypond, 00:44
  • Re: Issue 2149 in lilypond: Patch: Creates non-negative-integer? predicate., lilypond, 00:40
  • Re: Issue 1935 in lilypond: Doc: internal ledger lines need to be documented in NR, lilypond, 00:36
  • Re: Issue 2092 in lilypond: lily-git.tcl should using a "working" branch, lilypond, 00:32
  • Re: Issue 2152 in lilypond: Patch: Removes ugly side bars from learning, lilypond, 00:28
  • Re: Issue 2164 in lilypond: Learning Manual: Better explanation with updated example for \once tweak, lilypond, 00:24
  • Re: Issue 2137 in lilypond: Patch: Doc: NR improve 'visibility' of 'q' operation, lilypond, 00:20
  • Re: Issue 1629 in lilypond: Tuplet line collides with fingering, lilypond, 00:16
• January 03, 2012
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, -Eluze, 18:09
  • Re: Issue 2148 in lilypond: object outlines shouldn't be rectangular, lilypond, 17:29
  • Re: Issue 2174 in lilypond: Patch: CG: clarify what countdown means, lilypond, 17:12
  • Re: Issue 2093 in lilypond: Doc: NR alternativeNumberingStyle (fix issue 2059) needs to be documented, lilypond, 17:08
  • Re: Issue 2174 in lilypond: Patch: CG: clarify what countdown means, lilypond, 17:04
  • inconsistent handling of lilypond cmd w ith or without -h when LANG=… is not en, -Eluze, 16:57
  • Issue 2175 in lilypond: Patch: explain how to add git-cl to PATH, lilypond, 16:49
  • Issue 2174 in lilypond: Patch: CG: clarify what countdown means, lilypond, 16:26
  • Re: Issue 2160 in lilypond: document LILYPOND_WEB_MEDIA_GIT, lilypond, 15:45
  • Re: Issue 2093 in lilypond: Doc: NR alternativeNumberingStyle (fix issue 2059) needs to be documented, lilypond, 15:28
  • Re: Issue 2093 in lilypond: Doc: NR alternativeNumberingStyle (fix issue 2059) needs to be documented, lilypond, 15:24
  • Re: Issue 2109 in lilypond: do not tinker with the position of a pitched rest, lilypond, 15:20
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 15:15
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, Graham Percival, 15:13
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 14:53
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, Keith OHara, 13:36
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 13:15
  • Re: Issue 2173 in lilypond: Deal with file names not encoded in UTF-8, lilypond, 13:10
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 12:36
  • Re: Issue 2165 in lilypond: Patch: Modifies broken hairpin height, lilypond, 10:57
  • Re: Issue 2173 in lilypond: Deal with file names not encoded in UTF-8, lilypond, 07:33
  • Re: Issue 2173 in lilypond: Deal with file names not encoded in UTF-8, lilypond, 07:11
  • Re: Issue 1566 in lilypond: Beam properties won't be changed after the start of the beam, lilypond, 05:45
  • Re: Issue 2173 in lilypond: Deal with file names not encoded in UTF-8, lilypond, 04:44
  • Re: Issue 2173 in lilypond: Deal with file names not encoded in UTF-8, lilypond, 04:03
  • Re: Issue 2100 in lilypond: Patch: CG: explanation of branches for the impatient, lilypond, 00:45
• January 02, 2012
  • Re: Issue 2170 in lilypond: Patch: Updates makelsr to point to lilypond exe, lilypond, 23:01
  • Re: Issue 2169 in lilypond: Patch: Doc: Introduce Voices in the correct order. Mention that hideNotes hides beams, lilypond, 22:57
  • Re: Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 22:53
  • Re: Issue 1802 in lilypond: system-system-spacing in lilypond-book-file within a LaTeX file, lilypond, 22:49
  • Re: Issue 2155 in lilypond: TextScript isn't entirely scaled, while using another "staff-size", lilypond, 17:41
  • Re: Issue 2093 in lilypond: Doc: NR alternativeNumberingStyle (fix issue 2059) needs to be documented, Graham Percival, 16:44
  • Re: Issue 2093 in lilypond: Doc: NR alternativeNumberingStyle (fix issue 2059) needs to be documented, lilypond, 16:32
  • Re: Issue 2166 in lilypond: Copy pdf docs to new website folder, lilypond, 16:27
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 16:23
  • Re: Issue 2093 in lilypond: Doc: NR alternativeNumberingStyle (fix issue 2059) needs to be documented, lilypond, 16:01
  • Issue 2173 in lilypond: Deal with file names not encoded in UTF-8, lilypond, 14:36
  • Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 14:32
  • Re: Issue 2159 in lilypond: Patch: lexer.ll: Warn about non-UTF-8 characters, lilypond, 14:25
  • Re: Issue 2159 in lilypond: Patch: lexer.ll: Warn about non-UTF-8 characters, lilypond, 14:13
  • Re: Docs bug: \once prefix, drippingtone, 13:55
  • Re: Tuplet positioning on beamed notes is ugly, Chris Morgan, 13:54
  • Re: Issue 2159 in lilypond: Patch: lexer.ll: Warn about non-UTF-8 characters, lilypond, 11:17
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 10:32
  • Re: Issue 2127 in lilypond: Patch: Directs output of texi2html to log files (GOP 9), lilypond, 10:28
  • Issue 2172 in lilypond: Get line and column numbers right., lilypond, 09:21
  • Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module, lilypond, 08:29
  • Issue 2171 in lilypond: Patch: Implements DOM-id property for grobs., lilypond, 08:19
  • Re: modern-straight-flag, address@hidden, 07:58
  • modern-straight-flag, Karim Haddad, 07:55
  • Re: wrong italian word in pitches-headword.ly, Phil Holmes, 07:42
  • Issue 2170 in lilypond: Patch: Updates makelsr to point to lilypond exe, lilypond, 07:32
  • Re: Issue 2165 in lilypond: Patch: Modifies broken hairpin height, lilypond, 06:29
  • Re: Issue 1802 in lilypond: system-system-spacing in lilypond-book-file within a LaTeX file, lilypond, 05:32
  • Re: Issue 2142 in lilypond: accidental right-padding should depend on the tightness of music, lilypond, 05:05
  • Re: Issue 2093 in lilypond: Doc: NR alternativeNumberingStyle (fix issue 2059) needs to be documented, lilypond, 04:52
  • Re: Issue 2159 in lilypond: Patch: lexer.ll: Warn about non-UTF-8 characters, David Kastrup, 04:32
  • Re: Issue 2148 in lilypond: object outlines shouldn't be rectangular, lilypond, 04:18
  • Re: Issue 2148 in lilypond: object outlines shouldn't be rectangular, lilypond, 04:10
  • Re: Issue 2159 in lilypond: Patch: lexer.ll: Warn about non-UTF-8 characters, lilypond, 04:10
  • Re: Issue 2148 in lilypond: object outlines shouldn't be rectangular, lilypond, 03:58
  • Issue 2169 in lilypond: Patch: Doc: Introduce Voices in the correct order. Mention that hideNotes hides beams, lilypond, 03:31
  • Re: Issue 2165 in lilypond: Patch: Modifies broken hairpin height, lilypond, 03:27
• January 01, 2012
  • Re: Issue 1802 in lilypond: system-system-spacing in lilypond-book-file within a LaTeX file, lilypond, 23:23
  • Re: Issue 2168 in lilypond: Patch: Fix a few more warnings in clang, lilypond, 22:10
  • Re: Issue 2167 in lilypond: Patch: Doc: selective point and click, lilypond, 22:06
  • Issue 2168 in lilypond: Patch: Fix a few more warnings in clang, lilypond, 20:16
  • Re: Issue 2167 in lilypond: Patch: Doc: selective point and click, lilypond, 20:12
  • Re: Issue 2093 in lilypond: Doc: NR alternativeNumberingStyle (fix issue 2059) needs to be documented, lilypond, 20:08
  • Issue 2167 in lilypond: Patch: Doc: selective point and click, lilypond, 19:51
  • Re: Issue 2165 in lilypond: Patch: Modifies broken hairpin height, lilypond, 19:15
  • Re: Issue 2164 in lilypond: Learning Manual: Better explanation with updated example for \once tweak, lilypond, 19:11
  • Re: Issue 2162 in lilypond: Patch: Doc: NR added @knownissue for beam properties, lilypond, 19:07
  • Re: Issue 2159 in lilypond: Patch: lexer.ll: Warn about non-UTF-8 characters, lilypond, 19:03
  • Re: Issue 2166 in lilypond: Copy pdf docs to new website folder, lilypond, 18:59
  • Issue 2166 in lilypond: Copy pdf docs to new website folder, lilypond, 18:14
  • Re: Issue 2159 in lilypond: Patch: lexer.ll: Warn about non-UTF-8 characters, Hans Aberg, 17:19
  • Re: Issue 2159 in lilypond: Patch: lexer.ll: Warn about non-UTF-8 characters, lilypond, 17:02
  • Re: Issue 1023 in lilypond: User-friendly warnings for invalid character encoding (not UTF-8), lilypond, 16:58
  • Re: Issue 2159 in lilypond: Patch: lexer.ll: Warn about non-UTF-8 characters, lilypond, 16:50
  • Re: Issue 2156 in lilypond: lost commits, lilypond, 16:40
  • Re: Issue 2125 in lilypond: Patch: Build: Don't rebuild everything each time unless necessary., lilypond, 16:36
  • Re: wrong italian word in pitches-headword.ly, Trevor Daniels, 15:19
  • Re: Issue 2165 in lilypond: Patch: Modifies broken hairpin height, lilypond, 15:13
  • Issue 2165 in lilypond: Patch: Modifies broken hairpin height, lilypond, 15:09
  • Re: Issue 2159 in lilypond: Patch: lexer.ll: Warn about non-UTF-8 characters, David Kastrup, 15:07
  • Re: Issue 2159 in lilypond: Patch: lexer.ll: Warn about non-UTF-8 characters, Hans Aberg, 14:59
  • Re: Issue 2159 in lilypond: Patch: lexer.ll: Warn about non-UTF-8 characters, lilypond, 14:30
  • Re: Issue 2159 in lilypond: Patch: lexer.ll: Warn about non-UTF-8 characters, lilypond, 14:22
  • Re: Issue 2164 in lilypond: Learning Manual: Better explanation with updated example for \once tweak, lilypond, 12:27
  • Re: wrong italian word in pitches-headword.ly, David Kastrup, 12:10
  • Re: wrong italian word in pitches-headword.ly, Werner LEMBERG, 12:05
  • Re: Figured bass and rehearsal marks, Nicolas Sceaux, 12:05
  • Re: wrong italian word in pitches-headword.ly, Werner LEMBERG, 11:59
  • Re: Figured bass and rehearsal marks, Neil Puttock, 11:40
  • Re: Figured bass and rehearsal marks, Xavier Scheuer, 11:08
  • Re: wrong italian word in pitches-headword.ly, Phil Holmes, 10:34
  • Figured bass and rehearsal marks, Nicolas Sceaux, 10:19
  • Re: wrong italian word in pitches-headword.ly, David Kastrup, 10:18
  • Re: wrong italian word in pitches-headword.ly, Neil Puttock, 10:09
  • Re: wrong italian word in pitches-headword.ly, Phil Holmes, 09:48
  • Re: wrong italian word in pitches-headword.ly, Neil Puttock, 09:16
  • Re: wrong italian word in pitches-headword.ly, Phil Holmes, 09:09
  • wrong italian word in pitches-headword.ly, Federico Bruni, 08:30
  • Re: Issue 2156 in lilypond: lost commits, lilypond, 08:16
  • Re: Issue 2156 in lilypond: lost commits, lilypond, 07:56
  • Re: Issue 2148 in lilypond: object outlines shouldn't be rectangular, lilypond, 07:35
  • Re: Issue 2156 in lilypond: lost commits, lilypond, 07:27
  • Re: Docs bug: \once prefix, James, 07:19
  • Re: Issue 2164 in lilypond: Learning Manual: Better explanation with updated example for \once tweak, lilypond, 07:19
  • Issue 2164 in lilypond: Learning Manual: Better explanation with updated example for \once tweak, lilypond, 07:15
  • Re: Docs bug: \once prefix, James, 06:47
  • Re: Issue 2163 in lilypond: Web: Added 'Ripple' to easier-editing section, lilypond, 06:30
  • Docs bug: \once prefix, DrippingTone, 06:20

---

[Prev Period]

[Next Period]

---

Mail converted by MHonArc