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

bug-lilypond (thread)

[Date Index][Top][All Lists]

Advanced

[Prev Period]

Last Modified: Tue Jan 31 2012 21:30:53 -0500 Threads in reverse chronological order

[Next Period]

---

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

---

[Prev Period]

[Next Period]

---

Mail converted by MHonArc