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: Sat Apr 30 2011 20:49:48 -0400 Threads in reverse chronological order

[Next Period]

---

• Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 2011/04/30
• Issue 1641 in lilypond: noBeam disables beaming of prior notes, lilypond, 2011/04/30
  • Re: Issue 1641 in lilypond: noBeam disables beaming of prior notes, lilypond, 2011/04/30
• \noBeam disables beaming of further quavers, Martin Straeten, 2011/04/30
  • Re: \noBeam disables beaming of further quavers, Colin Campbell, 2011/04/30
• Issue 1640 in lilypond: Consecutive glissandos not typeset, lilypond, 2011/04/30
  • Re: Issue 1640 in lilypond: Consecutive glissandos not typeset, lilypond, 2011/04/30
• Issue 1639 in lilypond: Glissando between chords at end of measure prevents break and is sometimes not printed, lilypond, 2011/04/30
  • Re: Issue 1639 in lilypond: Glissando between chords at end of measure prevents break and is sometimes not printed, lilypond, 2011/04/30
  • Re: Issue 1639 in lilypond: Glissando between chords at end of measure prevents break and is sometimes not printed, lilypond, 2011/04/30
• Re: Issue 1163 in lilypond: website "what we wrote", lilypond, 2011/04/30
• Cyclical/mutual includes not detected, Olexa Bilaniuk, 2011/04/29
• Wrong ties when moving Tie_engraver from Voice to Staff, Helge Hafting, 2011/04/29
  • Re: Wrong ties when moving Tie_engraver from Voice to Staff, Neil Puttock, 2011/04/30
• Issue 1638 in lilypond: lilypond-book [quote] hard-codes 5\in, lilypond, 2011/04/28
• Issue 1637 in lilypond: include newest version of Fontforge in Lilydev, lilypond, 2011/04/28
  • Re: Issue 1637 in lilypond: include newest version of Fontforge in Lilydev, lilypond, 2011/04/28
• tags in parallel music gives "Bars in parallel music don't have the same length", Helge Hafting, 2011/04/28
• Bug in 64th-note sloped beams, Bird, 2011/04/26
  • RE: Bug in 64th-note sloped beams, James Lowe, 2011/04/27
  • FW: Bug in 64th-note sloped beams, James Lowe, 2011/04/27
    • Re: Bug in 64th-note sloped beams, Phil Holmes, 2011/04/27
      • Re: Bug in 64th-note sloped beams, address@hidden, 2011/04/27
      • Re: Bug in 64th-note sloped beams, Graham Percival, 2011/04/27
• Drawing systems...ERROR: In procedure min: ERROR: Wrong type: lilyvartmpbh, Nick Payne, 2011/04/26
  • Re: Drawing systems...ERROR: In procedure min: ERROR: Wrong type: lilyvartmpbh, address@hidden, 2011/04/26
    • Re: Drawing systems...ERROR: In procedure min: ERROR: Wrong type: lilyvartmpbh, Nick Payne, 2011/04/27
      • RE: Drawing systems...ERROR: In procedure min: ERROR: Wrong type: lilyvartmpbh, James Lowe, 2011/04/27
• One warning in flower, Patrick Horgan, 2011/04/26
• Re: Issue 984 in lilypond: Noteheads don't merge when one of the voices contains a second, lilypond, 2011/04/26
• Doc: LSR: midi, Keith OHara, 2011/04/26
  • Re: LSR: midi, Phil Holmes, 2011/04/26
• Issue 1636 in lilypond: midiVolume 0.0 not respected, lilypond, 2011/04/25
  • Re: Issue 1636 in lilypond: midiVolume 0.0 not respected, lilypond, 2011/04/26
  • Re: Issue 1636 in lilypond: midiVolume 0.0 not respected, lilypond, 2011/04/26
    • Re: Issue 1636 in lilypond: midiVolume 0.0 not respected, Colin Campbell, 2011/04/26
  • Re: Issue 1636 in lilypond: midiVolume 0.0 not respected, lilypond, 2011/04/30
  • Re: Issue 1636 in lilypond: midiVolume 0.0 not respected, lilypond, 2011/04/30
• Wrong version of midi.so in LilyPond 2.13.60, Hraban, 2011/04/25
• Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/25
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/26
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/26
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/27
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/27
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/27
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/27
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/28
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/28
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/28
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/28
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/29
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/30
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/30
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/30
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/30
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 2011/04/30
• Part Combiner problems, Olexa Bilaniuk, 2011/04/25
• Issue 1634 in lilypond: make find(1) work on BSDs, lilypond, 2011/04/25
  • Re: Issue 1634 in lilypond: make find(1) work on BSDs, lilypond, 2011/04/30
• mergeDifferentlyHeaded inconsistency, address@hidden, 2011/04/25
  • Re: mergeDifferentlyHeaded inconsistency, David Kastrup, 2011/04/25
    • Re: mergeDifferentlyHeaded inconsistency, address@hidden, 2011/04/25
  • Re: mergeDifferentlyHeaded inconsistency, Keith OHara, 2011/04/26
• Re: Issue 1547 in lilypond: Too many colliding rests, lilypond, 2011/04/24
• Issue 1633 in lilypond: pdf utf-16be breaks doc compile, lilypond, 2011/04/23
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, lilypond, 2011/04/23
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, lilypond, 2011/04/23
    • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, Colin Campbell, 2011/04/24
      • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, Reinhold Kainhofer, 2011/04/24
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, lilypond, 2011/04/24
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, lilypond, 2011/04/25
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, lilypond, 2011/04/26
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, lilypond, 2011/04/28
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, lilypond, 2011/04/30
• Issue 1632 in lilypond: beam staff change weird angular beam, lilypond, 2011/04/23
  • Re: Issue 1632 in lilypond: beam staff change weird angular beam, lilypond, 2011/04/23
  • Re: Issue 1632 in lilypond: beam staff change weird angular beam, lilypond, 2011/04/23
  • Re: Issue 1632 in lilypond: beam staff change weird angular beam, lilypond, 2011/04/23
• Doc build segfault, Colin Campbell, 2011/04/23
  • RE: Doc build segfault, James Lowe, 2011/04/23
    • Re: Doc build segfault, Graham Percival, 2011/04/23
      • Re: Doc build segfault, Graham Percival, 2011/04/23
      • Re: Doc build segfault, mike, 2011/04/23
      • Re: Doc build segfault, Graham Percival, 2011/04/23
      • Re: Doc build segfault, address@hidden, 2011/04/23
• Re: Issue 1547 in lilypond: Too many colliding resrts, lilypond, 2011/04/22
• Issue 1631 in lilypond: Feature request: Tuplet bracket style settings, lilypond, 2011/04/22
  • Re: Issue 1631 in lilypond: Feature request: Tuplet bracket style settings, lilypond, 2011/04/22
• Feature request: Tuplet bracket style settings, bruys ., 2011/04/21
  • Re: Feature request: Tuplet bracket style settings, Phil Holmes, 2011/04/22
• http://lilypond.org/doc/v2.13/Documentation/essay-big-page.html, Peter Woods, 2011/04/21
  • Re: http://lilypond.org/doc/v2.13/Documentation/essay-big-page.html, Trevor Daniels, 2011/04/21
    • Re: http://lilypond.org/doc/v2.13/Documentation/essay-big-page.html, Andrew Hawryluk, 2011/04/22
• Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 2011/04/21
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, ornello, 2011/04/27
    • Re: Issue 1630 in lilypond: Completion heads engraver producesduplicate ties, Phil Holmes, 2011/04/27
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 2011/04/27
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 2011/04/29
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 2011/04/29
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 2011/04/29
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 2011/04/29
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 2011/04/29
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 2011/04/30
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 2011/04/30
• Re: Issue 1626 in lilypond: Articulate produces faulty barcheck warnings, lilypond, 2011/04/21
  • Message not available
    • Re: Issue 1626 in lilypond: Articulate produces faulty barcheck warnings, lilypond, 2011/04/21
      • Message not available
      • Re: Issue 1626 in lilypond: Articulate produces faulty barcheck warnings, lilypond, 2011/04/25
• consecutive chordGlissando, Federico Bruni, 2011/04/20
  • Re: consecutive chordGlissando, Carl Sorensen, 2011/04/21
    • Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando], Federico Bruni, 2011/04/21
      • Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando], Graham Percival, 2011/04/23
      • Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando], Federico Bruni, 2011/04/24
      • Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando], Carl Sorensen, 2011/04/24
      • Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando], Federico Bruni, 2011/04/25
      • Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando], Federico Bruni, 2011/04/25
      • Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando], Carl Sorensen, 2011/04/25
      • Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando], Colin Campbell, 2011/04/25
      • Re: emproving Documentation about chordGlissando [WAS:consecutive chordGlissando], address@hidden, 2011/04/25
• Issue 1629 in lilypond: Tuplet line collides with fingering, lilypond, 2011/04/20
• Tuplet line collides with fingering, Ralph Palmer, 2011/04/20
  • Re: Tuplet line collides with fingering, Ralph Palmer, 2011/04/20
    • Re: Tuplet line collides with fingering, Marc Mouries, 2011/04/20
• Issue 1628 in lilypond: Fingerings collide with slurs when used in <>, lilypond, 2011/04/20
  • Re: Issue 1628 in lilypond: Fingerings collide with slurs when used in <>, Ralph Palmer, 2011/04/20
• Issue 1627 in lilypond: global-staff-size effects on grace notes (LilyPond 2.13.58), lilypond, 2011/04/20
• Issue 1626 in lilypond: Atriculate produces faulty barcheck warnings, lilypond, 2011/04/20
• articulate.ly and \mark causes barcheck failures, Helge Hafting, 2011/04/19
  • Re: articulate.ly and \mark causes barcheck failures, Phil Holmes, 2011/04/20
    • Re: articulate.ly and \mark causes barcheck failures, lily, 2011/04/21
• Possible regression in 2.13 series? "no viable configuration" warning, Valentin Villenave, 2011/04/19
  • Re: Possible regression in 2.13 series? "no viable configuration" warning, Graham Percival, 2011/04/19
    • Re: Possible regression in 2.13 series? "no viable configuration" warning, Valentin Villenave, 2011/04/20
      • Re: Possible regression in 2.13 series? "no viable configuration" warning, Han-Wen Nienhuys, 2011/04/20
      • Re: Possible regression in 2.13 series? "no viable configuration" warning, address@hidden, 2011/04/20
      • Re: Possible regression in 2.13 series? "no viable configuration" warning, Valentin Villenave, 2011/04/24
• Issue 1625 in lilypond: Slurs over rests have wrong direction, lilypond, 2011/04/19
  • Re: Issue 1625 in lilypond: Slurs over rests have wrong direction, lilypond, 2011/04/19
• Issue 1624 in lilypond: Segfault with stabel and development versions, lilypond, 2011/04/19
  • Re: Issue 1624 in lilypond: Segfault with stabel and development versions, lilypond, 2011/04/19
  • Re: Issue 1624 in lilypond: Segfault with stabel and development versions, lilypond, 2011/04/19
  • Re: Issue 1624 in lilypond: Segfault with stabel and development versions, lilypond, 2011/04/19
  • Re: Issue 1624 in lilypond: Segfault with stabel and development versions, lilypond, 2011/04/25
  • Re: Issue 1624 in lilypond: Segfault with stabel and development versions, lilypond, 2011/04/25
  • Re: Issue 1624 in lilypond: Segfault with stabel and development versions, lilypond, 2011/04/26
  • Re: Issue 1624 in lilypond: Segfault with stabel and development versions, lilypond, 2011/04/29
  • Re: Issue 1624 in lilypond: Segfault with stabel and development versions, lilypond, 2011/04/29
• global-staff-size effects on grace notes (LilyPond 2.13.58), Pierre Perol-Schneider, 2011/04/19
  • Re: global-staff-size effects on grace notes (LilyPond 2.13.58), Ralph Palmer, 2011/04/20
• Re: Issue 261 in lilypond: \partcombine prints rests (or not) depending on order of voices, lilypond, 2011/04/18
  • Re: Issue 261 in lilypond: \partcombine prints rests (or not) depending on order of voices, Keith OHara, 2011/04/18
• Re: Issue 1622 in lilypond: Dynamic spanner not printed within grace notes, lilypond, 2011/04/18
  • Message not available
    • Re: Issue 1622 in lilypond: Dynamic spanner not printed within grace notes, lilypond, 2011/04/18
      • Message not available
      • Re: Issue 1622 in lilypond: Dynamic spanner not printed within grace notes, lilypond, 2011/04/18
• Re: Change the color of ledger lines, Xavier Scheuer, 2011/04/18
  • Re: Change the color of ledger lines, Valentin Villenave, 2011/04/18
    • Re: Change the color of ledger lines, Xavier Scheuer, 2011/04/18
• beaming bug, Federico Bruni, 2011/04/18
  • Re: beaming bug, address@hidden, 2011/04/18
• Issue 1623 in lilypond: Override Stem #'length-fraction not applied to leger notes, lilypond, 2011/04/17
  • Re: Issue 1623 in lilypond: Override Stem #'length-fraction not applied to leger notes, lilypond, 2011/04/18
  • Re: Issue 1623 in lilypond: Override Stem #'length-fraction not applied to leger notes, lilypond, 2011/04/25
• Issue 1622 in lilypond: Dynamic spanner not pringed within grace notes, lilypond, 2011/04/17
  • Re: Issue 1622 in lilypond: Dynamic spanner not pringed within grace notes, lilypond, 2011/04/17
  • Re: Issue 1622 in lilypond: Dynamic spanner not pringed within grace notes, lilypond, 2011/04/18
• Issue 1621 in lilypond: Alignment of Lyric syllable is wrong after temporary voice closes, lilypond, 2011/04/17
  • Re: Issue 1621 in lilypond: Alignment of Lyric syllable is wrong after temporary voice closes, lilypond, 2011/04/18
• Override Stem #'length-fraction does not shorten stem of ledger notes, Xavier Scheuer, 2011/04/17
  • Re: Override Stem #'length-fraction does not shorten stem of ledger notes, Colin Campbell, 2011/04/17
  • Re: Override Stem #'length-fraction does not shorten stem of ledger notes, Neil Puttock, 2011/04/18
    • Re: Override Stem #'length-fraction does not shorten stem of ledger notes, Xavier Scheuer, 2011/04/19
• Re: Issue 1459 in lilypond: \hideNotes in tablature adds unwanted marks, lilypond, 2011/04/17
  • Message not available
    • Re: Issue 1459 in lilypond: \hideNotes in tablature adds unwanted marks, lilypond, 2011/04/18
      • Message not available
      • Re: Issue 1459 in lilypond: \hideNotes in tablature adds unwanted marks, lilypond, 2011/04/18
• Re: Issue 1073 in lilypond: convert-ly and accented characters, lilypond, 2011/04/17
• Issue 1620 in lilypond: Midi overflow with instrument changes, lilypond, 2011/04/17
  • Re: Issue 1620 in lilypond: Midi overflow with instrument changes, lilypond, 2011/04/17
  • Re: Issue 1620 in lilypond: Midi overflow with instrument changes, lilypond, 2011/04/18
  • Re: Issue 1620 in lilypond: Midi overflow with instrument changes, lilypond, 2011/04/19
  • Re: Issue 1620 in lilypond: Midi overflow with instrument changes, lilypond, 2011/04/19
  • Re: Issue 1620 in lilypond: Midi overflow with instrument changes, lilypond, 2011/04/19
  • Re: Issue 1620 in lilypond: Midi overflow with instrument changes, lilypond, 2011/04/19
  • Re: Issue 1620 in lilypond: Midi overflow with instrument changes, lilypond, 2011/04/19
  • Re: Issue 1620 in lilypond: Midi overflow with instrument changes, lilypond, 2011/04/21
  • Re: Issue 1620 in lilypond: Midi overflow with instrument changes, lilypond, 2011/04/25
  • Re: Issue 1620 in lilypond: Midi overflow with instrument changes, lilypond, 2011/04/29
• Issue 1619 in lilypond: Incorrect beam/stem, lilypond, 2011/04/17
  • Re: Issue 1619 in lilypond: Incorrect beam/stem, lilypond, 2011/04/17
  • Re: Issue 1619 in lilypond: Incorrect beam/stem, lilypond, 2011/04/17
  • Re: Issue 1619 in lilypond: Incorrect beam/stem, lilypond, 2011/04/17
  • Re: Issue 1619 in lilypond: Incorrect beam/stem, lilypond, 2011/04/17
  • Re: Issue 1619 in lilypond: Incorrect beam/stem, lilypond, 2011/04/17
  • Re: Issue 1619 in lilypond: Incorrect beam/stem, lilypond, 2011/04/19
  • Re: Issue 1619 in lilypond: Incorrect beam/stem, lilypond, 2011/04/29
• Re: Issue 1534 in lilypond: midi2ly does not show \breve or if a note lasts longer than one bar, lilypond, 2011/04/17
• Re: Issue 1453 in lilypond: lilydev-creation instructions, lilypond, 2011/04/17
  • Message not available
    • Re: Issue 1453 in lilypond: lilydev-creation instructions, lilypond, 2011/04/17
• Re: Issue 1609 in lilypond: unpredictable change of voicing in partcombine-midi.ly, lilypond, 2011/04/17
  • Message not available
    • Re: Issue 1609 in lilypond: unpredictable change of voicing in partcombine-midi.ly, lilypond, 2011/04/17
      • Message not available
      • Re: Issue 1609 in lilypond: unpredictable change of voicing in partcombine-midi.ly, lilypond, 2011/04/17
      • Message not available
      • Re: Issue 1609 in lilypond: unpredictable change of voicing in partcombine-midi.ly, lilypond, 2011/04/19
      • Message not available
      • Re: Issue 1609 in lilypond: unpredictable change of voicing in partcombine-midi.ly, lilypond, 2011/04/29
• Issue 1618 in lilypond: unpredictable placement of rests, lilypond, 2011/04/17
  • Re: Issue 1618 in lilypond: unpredictable placement of rests, lilypond, 2011/04/22
  • Re: Issue 1618 in lilypond: unpredictable placement of rests, Han-Wen Nienhuys, 2011/04/22
  • Re: Issue 1618 in lilypond: unpredictable placement of rests, lilypond, 2011/04/22
  • Re: Issue 1618 in lilypond: unpredictable placement of rests, lilypond, 2011/04/23
  • Re: Issue 1618 in lilypond: unpredictable placement of rests, lilypond, 2011/04/25
  • Re: Issue 1618 in lilypond: unpredictable placement of rests, lilypond, 2011/04/25
  • Re: Issue 1618 in lilypond: unpredictable placement of rests, lilypond, 2011/04/26
• Beaming problem introduced with 2.13.60, Nick Payne, 2011/04/17
  • Re: Beaming problem introduced with 2.13.60, address@hidden, 2011/04/17
  • Re: Beaming problem introduced with 2.13.60, Phil Holmes, 2011/04/17
• Issue 1617 in lilypond: chordGlissando is a hack that should be replaced with a Glissando property such as 'connect-all, lilypond, 2011/04/16
• Issue 1616 in lilypond: old website link gives false doc suggestion info, lilypond, 2011/04/16
  • Re: Issue 1616 in lilypond: old website link gives false doc suggestion info, lilypond, 2011/04/16
• beam/clef crash, David Bobroff, 2011/04/16
  • Re: beam/clef crash, Xavier Scheuer, 2011/04/16
• Re: Issue 712 in lilypond: alignment of multiple \tempo marks over `church rests', lilypond, 2011/04/16
• Re: branching, Graham Percival, 2011/04/15
• Re: Issue 630 in lilypond: non-synchronized grace note makes voiceOne go stems down, lilypond, 2011/04/15
• Issue 1615 in lilypond: lily-git.tcl not working: savannah no longer likes git fetch --depth, lilypond, 2011/04/15
• Issue 1614 in lilypond: DynamicTextSpanner documentation is wrong, lilypond, 2011/04/15
  • Re: Issue 1614 in lilypond: DynamicTextSpanner documentation is wrong, lilypond, 2011/04/15
  • Re: Issue 1614 in lilypond: DynamicTextSpanner documentation is wrong, lilypond, 2011/04/15
• tie does not avoid collision with sforzato, -Eluze, 2011/04/15
  • Re: tie does not avoid collision with sforzato, -Eluze, 2011/04/17
• Issue with DynamicTextSpanner style override, Olexa Bilaniuk, 2011/04/14
  • Re: Issue with DynamicTextSpanner style override, Phil Holmes, 2011/04/15
• Re: Issue 1582 in lilypond: flag variants patch, lilypond, 2011/04/14
  • Message not available
    • Re: Issue 1582 in lilypond: flag variants patch, lilypond, 2011/04/15
      • Message not available
      • Re: Issue 1582 in lilypond: flag variants patch, lilypond, 2011/04/19
• barchecks in lyrics mode confused by rests, Mark Polesky, 2011/04/14
  • Re: barchecks in lyrics mode confused by rests, Trevor Daniels, 2011/04/14
    • Re: barchecks in lyrics mode confused by rests, Colin Campbell, 2011/04/14
      • Re: barchecks in lyrics mode confused by rests, Mark Polesky, 2011/04/15
      • Re: barchecks in lyrics mode confused by rests, Trevor Daniels, 2011/04/15
• Git master build for V2.13.60 in fresh directory - make docs fails, Ian Hulin, 2011/04/14
  • Re: Git master build for V2.13.60 in fresh directory - make docs fails, Graham Percival, 2011/04/15
    • Re: Git master build for V2.13.60 in fresh directory - make docs fails, Ian Hulin, 2011/04/15
      • Re: Git master build for V2.13.60 in fresh directory - make docs fails, Graham Percival, 2011/04/16
      • Re: Git master build for V2.13.60 in fresh directory - make docs fails, Colin Campbell, 2011/04/16
• Re: Issue 1502 in lilypond: DOcument information in PDF headers requires escapes for accented characters, lilypond, 2011/04/14
  • Message not available
    • Re: Issue 1502 in lilypond: DOcument information in PDF headers requires escapes for accented characters, lilypond, 2011/04/14
      • Message not available
      • Re: Issue 1502 in lilypond: DOcument information in PDF headers requires escapes for accented characters, lilypond, 2011/04/16
      • Message not available
      • Re: Issue 1502 in lilypond: DOcument information in PDF headers requires escapes for accented characters, lilypond, 2011/04/19
• Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice, lilypond, 2011/04/14
  • Re: Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice, lilypond, 2011/04/14
  • Re: Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice, lilypond, 2011/04/15
  • Re: Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice, lilypond, 2011/04/15
    • Re: Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice, Jay Anderson, 2011/04/16
      • Re: Issue 1613 in lilypond: Beamed stems too long when avoiding lownote in other voice, Phil Holmes, 2011/04/17
  • Re: Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice, lilypond, 2011/04/16
  • Re: Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice, lilypond, 2011/04/19
  • Re: Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice, lilypond, 2011/04/22
  • Re: Issue 1613 in lilypond: Beamed stems too long when avoiding low note in other voice, lilypond, 2011/04/28
• Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/04/14
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/04/14
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/04/14
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/04/14
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/04/14
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/04/14
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/04/14
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/04/15
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/04/15
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/04/15
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/04/15
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/04/15
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/04/15
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/04/19
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/04/21
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/04/22
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/04/22
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/04/22
  • Re: Issue 1612 in lilypond: Change staff produces long stems, lilypond, 2011/04/23
• lily-git.tcl not working?, Janek Warchoł, 2011/04/14
  • RE: lily-git.tcl not working?, James Lowe, 2011/04/14
    • Re: lily-git.tcl not working?, Janek Warchoł, 2011/04/16
  • Re: lily-git.tcl not working?, Graham Percival, 2011/04/15
• strange beaming when changing staff, Nathan Chou, 2011/04/14
  • RE: strange beaming when changing staff, James Lowe, 2011/04/14
  • Re: strange beaming when changing staff, Trevor Daniels, 2011/04/14
    • Re: strange beaming when changing staff, Phil Holmes, 2011/04/14
      • Re: strange beaming when changing staff, Nathan Chou, 2011/04/14
• Issue 1611 in lilypond: Midi2ly doesn't convert dynamics, lilypond, 2011/04/13
  • Re: Issue 1611 in lilypond: Midi2ly doesn't convert dynamics, lilypond, 2011/04/14
  • Re: Issue 1611 in lilypond: Midi2ly doesn't convert dynamics, lilypond, 2011/04/14
• Re: header items: use #f or ##f ?, Ralph Palmer, 2011/04/13
• Issue 1610 in lilypond: header items : #f vs. ##f, lilypond, 2011/04/13
• Issue 1609 in lilypond: unpredictable change of voicing, lilypond, 2011/04/13
  • Re: Issue 1609 in lilypond: unpredictable change of voicing, lilypond, 2011/04/15
  • Re: Issue 1609 in lilypond: unpredictable change of voicing, lilypond, 2011/04/15
  • Re: Issue 1609 in lilypond: unpredictable change of voicing, lilypond, 2011/04/15
  • Re: Issue 1609 in lilypond: unpredictable change of voicing, lilypond, 2011/04/16
  • Re: Issue 1609 in lilypond: unpredictable change of voicing, lilypond, 2011/04/16
  • Re: Issue 1609 in lilypond: unpredictable change of voicing, lilypond, 2011/04/16
  • Re: Issue 1609 in lilypond: unpredictable change of voicing, lilypond, 2011/04/16
  • Re: Issue 1609 in lilypond: unpredictable change of voicing, lilypond, 2011/04/16
• Deprecate /cygwin/foo/bar/ online doc links?, Valentin Villenave, 2011/04/11
  • Re: Deprecate /cygwin/foo/bar/ online doc links?, Phil Holmes, 2011/04/11
  • Re: Deprecate /cygwin/foo/bar/ online doc links?, Jan Nieuwenhuizen, 2011/04/11
• Issue 1608 in lilypond: patch to prevent rests from shifting, lilypond, 2011/04/10
  • Re: Issue 1608 in lilypond: patch to prevent rests from shifting, lilypond, 2011/04/10
  • Re: Issue 1608 in lilypond: patch to prevent rests from shifting, lilypond, 2011/04/10
    • Re: Issue 1608 in lilypond: patch to prevent rests from shifting, Colin Campbell, 2011/04/11
      • Re: Issue 1608 in lilypond: patch to prevent rests from shifting, Graham Percival, 2011/04/11
  • Re: Issue 1608 in lilypond: patch to prevent rests from shifting, lilypond, 2011/04/11
  • Re: Issue 1608 in lilypond: patch to prevent rests from shifting, lilypond, 2011/04/17
• Issue 1607 in lilypond: patch for mandolin freboard diagrams, lilypond, 2011/04/10
  • Re: Issue 1607 in lilypond: patch for mandolin freboard diagrams, lilypond, 2011/04/11
  • Re: Issue 1607 in lilypond: patch for mandolin freboard diagrams, lilypond, 2011/04/20
  • Re: Issue 1607 in lilypond: patch for mandolin freboard diagrams, lilypond, 2011/04/25
• Incompatible stem warnings may display nonsensic durations., David Kastrup, 2011/04/10
  • Re: Incompatible stem warnings may display nonsensic durations., Ralph Palmer, 2011/04/13
    • Re: Incompatible stem warnings may display nonsensic durations., David Kastrup, 2011/04/13
      • Re: Incompatible stem warnings may display nonsensic durations., Graham Percival, 2011/04/13
• stemlength II, Friedrich Fischer, 2011/04/10
  • Re: stemlength II, James Lowe, 2011/04/10
    • Re: stemlength II, Phil Holmes, 2011/04/14
      • RE: stemlength II, James Lowe, 2011/04/14
      • Re: stemlength II, Phil Holmes, 2011/04/14
      • Re: stemlength II, David Kastrup, 2011/04/14
      • Re: stemlength II, Phil Holmes, 2011/04/14
      • Re: stemlength II, Han-Wen Nienhuys, 2011/04/14
      • Re: stemlength II, address@hidden, 2011/04/15
      • Re: stemlength II, Han-Wen Nienhuys, 2011/04/15
      • Re: stemlength II, address@hidden, 2011/04/14
• Issue 1606 in lilypond: Slurs avoid collision with beam better than ties, lilypond, 2011/04/10
  • Re: Issue 1606 in lilypond: Slurs avoid collision with beam better than ties, lilypond, 2011/04/10
• Re: Issue 480 in lilypond: collision: tie after line break with sharp/natural accidental, lilypond, 2011/04/10
• Issue 1605 in lilypond: PS -> PDF conversion fails, lilypond, 2011/04/10
  • Re: Issue 1605 in lilypond: PS -> PDF conversion fails, lilypond, 2011/04/10
  • Re: Issue 1605 in lilypond: PS -> PDF conversion fails, lilypond, 2011/04/12
  • Re: Issue 1605 in lilypond: PS -> PDF conversion fails, lilypond, 2011/04/12
  • Re: Issue 1605 in lilypond: PS -> PDF conversion fails, lilypond, 2011/04/12
  • Re: Issue 1605 in lilypond: PS -> PDF conversion fails, lilypond, 2011/04/13
  • Re: Issue 1605 in lilypond: PS -> PDF conversion fails, lilypond, 2011/04/16
  • Re: Issue 1605 in lilypond: PS -> PDF conversion fails, lilypond, 2011/04/17
  • Re: Issue 1605 in lilypond: PS -> PDF conversion fails, lilypond, 2011/04/17
  • Re: Issue 1605 in lilypond: PS -> PDF conversion fails, lilypond, 2011/04/19
  • Re: Issue 1605 in lilypond: PS -> PDF conversion fails, lilypond, 2011/04/29
• snippet "Slides in tablature", NR 2.4.1, Federico Bruni, 2011/04/10
  • Re: [tablatures] snippet "Slides in tablature", NR 2.4.1, Valentin Villenave, 2011/04/10
  • Re: [tablatures] snippet "Slides in tablature", NR 2.4.1, Valentin Villenave, 2011/04/13
    • Re: [tablatures] snippet "Slides in tablature", NR 2.4.1, Federico Bruni, 2011/04/17
      • Re: [tablatures] snippet "Slides in tablature", NR 2.4.1, Patrick Schmidt, 2011/04/17
      • Re: [tablatures] snippet "Slides in tablature", NR 2.4.1, Federico Bruni, 2011/04/17
      • Re: [tablatures] snippet "Slides in tablature", NR 2.4.1, Patrick Schmidt, 2011/04/17
      • Re: [tablatures] snippet "Slides in tablature", NR 2.4.1, Federico Bruni, 2011/04/17
      • Re: [tablatures] snippet "Slides in tablature", NR 2.4.1, Carl Sorensen, 2011/04/17
      • Re: [tablatures] snippet "Slides in tablature", NR 2.4.1, Marc Hohl, 2011/04/18
      • Re: [tablatures] snippet "Slides in tablature", NR 2.4.1, Federico Bruni, 2011/04/18
      • Issue 1459 [was: Re: [tablatures] snippet "Slides in tablature", NR 2.4.1], Marc Hohl, 2011/04/18
• Slurs are better than ties at automatically avoiding collisions, Nick Payne, 2011/04/10
  • Re: Slurs are better than ties at automatically avoiding collisions, Phil Holmes, 2011/04/10
• Re: Issue 1542 in lilypond: [PATCH] Add springs-and-rods callback to DynamicTextSpanner, so minimum-length has an effect (issue4187054), lilypond, 2011/04/10
• Issue 1604 in lilypond: MultiMeasureRest staff position 0 is taken as staff position 2, lilypond, 2011/04/10
  • Re: Issue 1604 in lilypond: MultiMeasureRest staff position 0 is taken as staff position 2, lilypond, 2011/04/11
  • Re: Issue 1604 in lilypond: MultiMeasureRest staff position 0 is taken as staff position 2, lilypond, 2011/04/11
  • Re: Issue 1604 in lilypond: MultiMeasureRest staff position 0 is taken as staff position 2, lilypond, 2011/04/12
  • Re: Issue 1604 in lilypond: MultiMeasureRest staff position 0 is taken as staff position 2, lilypond, 2011/04/16
• Issue 1603 in lilypond: Add some polyphonically directed grobs, lilypond, 2011/04/09
  • Re: Issue 1603 in lilypond: Add some polyphonically directed grobs, lilypond, 2011/04/14
• Incorrect staff positioning of MultiMeasureRests, Olexa Bilaniuk, 2011/04/09
  • Re: Incorrect staff positioning of MultiMeasureRests, Colin Campbell, 2011/04/10
• Starting Grace Notes error: bug?, Javier Ruiz, 2011/04/09
  • Re: Starting Grace Notes error: bug?, David Kastrup, 2011/04/10
  • Re: Starting Grace Notes error: bug?, Phil Holmes, 2011/04/10
    • Re: Starting Grace Notes error: bug?, Xavier Scheuer, 2011/04/10
• Lyric collides with staff line, Phil Holmes, 2011/04/09
  • Re: Lyric collides with staff line, Keith OHara, 2011/04/12
    • Re: Lyric collides with staff line, Phil Holmes, 2011/04/12
      • Re: Lyric collides with staff line, Keith OHara, 2011/04/12
• Re: Status of break-align-symbol vs. break-align-symbols, Robin Bannister, 2011/04/09
  • Re: Status of break-align-symbol vs. break-align-symbols, Phil Holmes, 2011/04/09
• ** LOST ** Many single-system scores produces bad output and overflow, Xavier Scheuer, 2011/04/09
  • Re: ** LOST ** Many single-system scores produces bad output and overflow, David Kastrup, 2011/04/09
    • Re: ** LOST ** Many single-system scores produces bad output andoverflow, Phil Holmes, 2011/04/09
      • Re: ** LOST ** Many single-system scores produces bad output andoverflow, Xavier Scheuer, 2011/04/09
• Issue 1602 in lilypond: website build CG info isn't generated, lilypond, 2011/04/09
  • Re: Issue 1602 in lilypond: website build CG info isn't generated, lilypond, 2011/04/09
  • Re: Issue 1602 in lilypond: website build CG info isn't generated, lilypond, 2011/04/09
• programming error: cannot align on self: empty element, Nick Payne, 2011/04/09
  • Re: programming error: cannot align on self: empty element, Phil Holmes, 2011/04/09
• Re: Issue 572 in lilypond: Feature request: vertical instrumentName alignment should ignore non-stafflike contexts, lilypond, 2011/04/08
  • Message not available
    • Re: Issue 572 in lilypond: Feature request: vertical instrumentName alignment should ignore non-stafflike contexts, lilypond, 2011/04/17
• Issue 1601 in lilypond: Autobeaming in 12/8 produces incorrect result, lilypond, 2011/04/08
  • Re: Issue 1601 in lilypond: Autobeaming in 12/8 produces incorrect result, lilypond, 2011/04/08
  • Re: Issue 1601 in lilypond: Autobeaming in 12/8 produces incorrect result, lilypond, 2011/04/08
  • Re: Issue 1601 in lilypond: Autobeaming in 12/8 produces incorrect result, lilypond, 2011/04/08
  • Re: Issue 1601 in lilypond: Autobeaming in 12/8 produces incorrect result, lilypond, 2011/04/08
  • Re: Issue 1601 in lilypond: Autobeaming in 12/8 produces incorrect result, lilypond, 2011/04/09
  • Re: Issue 1601 in lilypond: Autobeaming in 12/8 produces incorrect result, lilypond, 2011/04/17
• [Regression] Beam_collision_engraver and StaffSymbol overrides, Bertrand Bordage, 2011/04/08
  • Re: [Regression] Beam_collision_engraver and StaffSymbol overrides, Phil Holmes, 2011/04/08
    • Re: [Regression] Beam_collision_engraver and StaffSymbol overrides, Phil Holmes, 2011/04/09
• Re: Issue 1579 in lilypond: Overextended lyrics extenders, lilypond, 2011/04/08
  • Message not available
    • Re: Issue 1579 in lilypond: Overextended lyrics extenders, lilypond, 2011/04/11
• Issue 1600 in lilypond: Allows users to request that beam collision occur on the Voice level, lilypond, 2011/04/07
  • Re: Issue 1600 in lilypond: Allows users to request that beam collision occur on the Voice level, lilypond, 2011/04/08
  • Re: Issue 1600 in lilypond: Allows users to request that beam collision occur on the Voice level, lilypond, 2011/04/08
  • Re: Issue 1600 in lilypond: Allows users to request that beam collision occur on the Voice level, lilypond, 2011/04/17
• Issue 1599 in lilypond: Adds footnote-footer-padding to the paper bloc., lilypond, 2011/04/07
  • Re: Issue 1599 in lilypond: Adds footnote-footer-padding to the paper bloc., lilypond, 2011/04/08
  • Re: Issue 1599 in lilypond: Adds footnote-footer-padding to the paper bloc., lilypond, 2011/04/09
  • Re: Issue 1599 in lilypond: Adds footnote-footer-padding to the paper bloc., lilypond, 2011/04/17
• Re: Issue 1506 in lilypond: \tempo after StopStaff/StartStaff forces extension of staff symbol, lilypond, 2011/04/07
  • Message not available
    • Re: Issue 1506 in lilypond: \tempo after StopStaff/StartStaff forces extension of staff symbol, lilypond, 2011/04/07
      • Message not available
      • Re: Issue 1506 in lilypond: \tempo after StopStaff/StartStaff forces extension of staff symbol, lilypond, 2011/04/08
      • Message not available
      • Re: Issue 1506 in lilypond: \tempo after StopStaff/StartStaff forces extension of staff symbol, lilypond, 2011/04/08
• [small regression?] Demisemiquaver beamException when in 12/8, Bertrand Bordage, 2011/04/07
  • Re: [small regression?] Demisemiquaver beamException when in 12/8, Phil Holmes, 2011/04/08
  • Re: [small regression?] Demisemiquaver beamException when in 12/8, Carl Sorensen, 2011/04/08
• Nouveau projet et personne ressource, Danielle Paquet, 2011/04/07
  • Re: Nouveau projet et personne ressource, address@hidden, 2011/04/07
    • Re: Nouveau projet et personne ressource, Valentin Villenave, 2011/04/07
      • Re: Nouveau projet et personne ressource, address@hidden, 2011/04/07
      • Re: Nouveau projet et personne ressource, Valentin Villenave, 2011/04/08
      • Re: Nouveau projet et personne ressource, address@hidden, 2011/04/08
      • Re: Nouveau projet et personne ressource, Valentin Villenave, 2011/04/08
      • Re: Nouveau projet et personne ressource, Werner LEMBERG, 2011/04/08
      • Re: Nouveau projet et personne ressource, David Kastrup, 2011/04/08
      • Re: Nouveau projet et personne ressource, Valentin Villenave, 2011/04/08
      • Re: Nouveau projet et personne ressource, Han-Wen Nienhuys, 2011/04/08
      • Re: Nouveau projet et personne ressource, address@hidden, 2011/04/08
• Issue 1598 in lilypond: Dynamics staff on lower piano staff shifts PianoStaff name, lilypond, 2011/04/07
  • Re: Issue 1598 in lilypond: Dynamics staff on lower piano staff shifts PianoStaff name, lilypond, 2011/04/08
  • Re: Issue 1598 in lilypond: Dynamics staff on lower piano staff shifts PianoStaff name, lilypond, 2011/04/08
• Issue 1597 in lilypond: Windows install can cause PATH to overflow, lilypond, 2011/04/07
• Issue 1596 in lilypond: Alignment of text mark is lost when an offset is applied, lilypond, 2011/04/07
  • Re: Issue 1596 in lilypond: Alignment of text mark is lost when an offset is applied, lilypond, 2011/04/08
  • Re: Issue 1596 in lilypond: Alignment of text mark is lost when an offset is applied, lilypond, 2011/04/17
  • Re: Issue 1596 in lilypond: Alignment of text mark is lost when an offset is applied, lilypond, 2011/04/18
• Broken piano template w/ centered dynamics, Hinrik ÖrnSigurðsson, 2011/04/07
  • Re: Broken piano template w/ centered dynamics, Phil Holmes, 2011/04/07
• midi bug remains in 2.13.58, 胡海鹏 - Hu Haipeng, 2011/04/07
  • Re: midi bug remains in 2.13.58, Jan Nieuwenhuizen, 2011/04/08
  • Re: midi bug remains in 2.13.58, Phil Holmes, 2011/04/10
  • Re: midi bug remains in 2.13.58, Phil Holmes, 2011/04/10
  • Message not available
    • Message not available
      • Re:Re: midi bug remains in 2.13.58, 胡海鹏 - Hu Haipeng, 2011/04/16
      • Re: midi bug remains in 2.13.58, Jan Nieuwenhuizen, 2011/04/17
      • Re: midi bug remains in 2.13.58, Phil Holmes, 2011/04/17
• Re: Issue 1554 in lilypond: update midi2ly version number, lilypond, 2011/04/07
• Fwd: lilypond v2.13.54, James Lowe, 2011/04/06
  • Re: lilypond v2.13.54, Phil Holmes, 2011/04/07
• monthly "unanswered email" count, Graham Percival, 2011/04/06
• Issue 1595 in lilypond: lilypond-book papersize gives margin warnings, lilypond, 2011/04/06
• Alignment of text mark is lost when an offset is applied, Ed Gordijn, 2011/04/06
  • Re: Alignment of text mark is lost when an offset is applied, Phil Holmes, 2011/04/07
• Issue 1594 in lilypond: In figured bass, _ direction indicator does not work, lilypond, 2011/04/06
• Many single-system scores produces bad output and overflow, Xavier Scheuer, 2011/04/06
  • Re: Many single-system scores produces bad output and overflow, David Kastrup, 2011/04/06
• Arpeggio collision bug, 胡海鹏 - Hu Haipeng, 2011/04/06
  • Re: Arpeggio collision bug, Robin Bannister, 2011/04/07
  • Re:Re: Arpeggio collision bug, 胡海鹏 - Hu Haipeng, 2011/04/08
    • Re: Arpeggio collision bug, Robin Bannister, 2011/04/08
• In figured bass, _ direction indicator does not work (^ and - work), Reinhold Kainhofer, 2011/04/06
  • Re: In figured bass, _ direction indicator does not work (^ and - work), Ralph Palmer, 2011/04/06
• Re: Issue 291 in lilypond: \glissando doesn't work properly with chords, lilypond, 2011/04/06
• Issue 1593 in lilypond: midi output eats rests when absolute dynamics are used, lilypond, 2011/04/05
  • Re: Issue 1593 in lilypond: midi output eats rests when absolute dynamics are used, lilypond, 2011/04/05
  • Re: Issue 1593 in lilypond: midi output eats rests when absolute dynamics are used, lilypond, 2011/04/05
  • Re: Issue 1593 in lilypond: midi output eats rests when absolute dynamics are used, lilypond, 2011/04/05
  • Re: Issue 1593 in lilypond: midi output eats rests when absolute dynamics are used, lilypond, 2011/04/05
    • Re: Issue 1593 in lilypond: midi output eats rests when absolute dynamics are used, David Kastrup, 2011/04/06
  • Re: Issue 1593 in lilypond: midi output eats rests when absolute dynamics are used, lilypond, 2011/04/13
• Issue 1592 in lilypond: regtest for midi output, lilypond, 2011/04/05
  • Re: Issue 1592 in lilypond: regtest for midi output, lilypond, 2011/04/05
  • Re: Issue 1592 in lilypond: regtest for midi output, lilypond, 2011/04/12
  • Re: Issue 1592 in lilypond: regtest for midi output, lilypond, 2011/04/13
• Re: Issue 1548 in lilypond: midi output should map voices to channels, lilypond, 2011/04/05
  • Message not available
    • Re: Issue 1548 in lilypond: midi output should map voices to channels, lilypond, 2011/04/07
      • Message not available
      • Re: Issue 1548 in lilypond: midi output should map voices to channels, lilypond, 2011/04/07
• Issue 1591 in lilypond: doc: midi output is channel-voice, lilypond, 2011/04/05
  • Re: Issue 1591 in lilypond: doc: midi output is channel-voice, lilypond, 2011/04/07
• Re: Issue 1587 in lilypond: midi2ly --key option only reaches first staff, lilypond, 2011/04/05
• Critical bug of midi output in 2.13.57, 胡海鹏 - Hu Haipeng, 2011/04/04
  • Re: Critical bug of midi output in 2.13.57, Werner LEMBERG, 2011/04/05
    • Re: Critical bug of midi output in 2.13.57, Jan Nieuwenhuizen, 2011/04/05
• Impossible or ambiguous (de)crescendo in MIDI, Miguel Ortega, 2011/04/04
  • Re: Impossible or ambiguous (de)crescendo in MIDI, Phil Holmes, 2011/04/04
• Re: Issue 1574 in lilypond: DOC: Need updated/expanded documentation of percent repeat/beat slash, lilypond, 2011/04/04
  • Message not available
    • Re: Issue 1574 in lilypond: DOC: Need updated/expanded documentation of percent repeat/beat slash, lilypond, 2011/04/21
• Re: Issue 1471 in lilypond: accidentals after a clef change are not printed, lilypond, 2011/04/03
  • Message not available
    • Re: Issue 1471 in lilypond: accidentals after a clef change are not printed, lilypond, 2011/04/04
      • Message not available
      • Re: Issue 1471 in lilypond: accidentals after a clef change are not printed, lilypond, 2011/04/04
      • Message not available
      • Re: Issue 1471 in lilypond: accidentals after a clef change are not printed, lilypond, 2011/04/06
      • Message not available
      • Re: Issue 1471 in lilypond: accidentals after a clef change are not printed, lilypond, 2011/04/08
      • Message not available
      • Re: Issue 1471 in lilypond: accidentals after a clef change are not printed, lilypond, 2011/04/08
      • Message not available
      • Re: Issue 1471 in lilypond: accidentals after a clef change are not printed, lilypond, 2011/04/08
      • Message not available
      • Re: Issue 1471 in lilypond: accidentals after a clef change are not printed, lilypond, 2011/04/08
      • Message not available
      • Re: Issue 1471 in lilypond: accidentals after a clef change are not printed, lilypond, 2011/04/08
      • Message not available
      • Re: Issue 1471 in lilypond: accidentals after a clef change are not printed, lilypond, 2011/04/08
      • Message not available
      • Re: Issue 1471 in lilypond: accidentals after a clef change are not printed, lilypond, 2011/04/09
      • Message not available
      • Re: Issue 1471 in lilypond: accidentals after a clef change are not printed, lilypond, 2011/04/10
      • Message not available
      • Re: Issue 1471 in lilypond: accidentals after a clef change are not printed, lilypond, 2011/04/14
      • Message not available
      • Re: Issue 1471 in lilypond: accidentals after a clef change are not printed, lilypond, 2011/04/17
• Re: position of the little '8' in bass clef, Phil Holmes, 2011/04/03
  • Re: position of the little '8' in bass clef, Werner LEMBERG, 2011/04/03
    • Re: position of the little '8' in bass clef, Colin Campbell, 2011/04/03
    • Re: position of the little '8' in bass clef, Phil Holmes, 2011/04/03
• Last line doesn't wrap, Paul Nocero, 2011/04/03
  • Re: Last line doesn't wrap, Xavier Scheuer, 2011/04/03
  • Re: Last line doesn't wrap, Carl Sorensen, 2011/04/03
• Re: Issue 1586 in lilypond: midi cresc happens instantly, lilypond, 2011/04/02
  • Message not available
    • Re: Issue 1586 in lilypond: midi cresc happens instantly, lilypond, 2011/04/02
      • Message not available
      • Re: Issue 1586 in lilypond: midi cresc happens instantly, lilypond, 2011/04/03
      • Message not available
      • Re: Issue 1586 in lilypond: midi cresc happens instantly, lilypond, 2011/04/05
      • Message not available
      • Re: Issue 1586 in lilypond: midi cresc happens instantly, lilypond, 2011/04/05
• Typo in time-signature-settings.scm?, Valentin Villenave, 2011/04/02
  • Re: Typo in time-signature-settings.scm?, Carl Sorensen, 2011/04/02
    • Re: Typo in time-signature-settings.scm?, Carl Sorensen, 2011/04/02
    • Re: Typo in time-signature-settings.scm?, Valentin Villenave, 2011/04/05
      • Re: Typo in time-signature-settings.scm?, Carl Sorensen, 2011/04/06
      • Re: Typo in time-signature-settings.scm?, Valentin Villenave, 2011/04/06
• Chord repetition shortcut doesn't support relative mode in Scheme functions, Valentin Villenave, 2011/04/02
  • Re: Chord repetition shortcut doesn't support relative mode in Scheme functions, Colin Campbell, 2011/04/03
    • Re: Chord repetition shortcut doesn't support relative mode in Scheme functions, Valentin Villenave, 2011/04/04
• Re: Issue 795 in lilypond: Beams do not take grace notes into account, lilypond, 2011/04/02
  • Message not available
    • Re: Issue 795 in lilypond: Beams do not take grace notes into account, lilypond, 2011/04/02
      • Re: Issue 795 in lilypond: Beams do not take grace notes into account, Colin Campbell, 2011/04/02
      • Re: Issue 795 in lilypond: Beams do not take grace notes into account, address@hidden, 2011/04/03
      • Message not available
      • Re: Issue 795 in lilypond: Beams do not take grace notes into account, lilypond, 2011/04/09
      • Message not available
      • Re: Issue 795 in lilypond: Beams do not take grace notes into account, lilypond, 2011/04/17
• Re: Issue 1567 in lilypond: Add documentation for footnotes, lilypond, 2011/04/02
• Re: Issue 1585 in lilypond: LilyPond segfaults on beams with headless stencils, lilypond, 2011/04/02
  • Message not available
    • Re: Issue 1585 in lilypond: LilyPond segfaults on beams with headless stencils, lilypond, 2011/04/02
      • Message not available
      • Re: Issue 1585 in lilypond: LilyPond segfaults on beams with headless stencils, lilypond, 2011/04/02
      • Message not available
      • Re: Issue 1585 in lilypond: LilyPond segfaults on beams with headless stencils, lilypond, 2011/04/02
• Re: Issue 1576 in lilypond: Doc: Added new option 'papersize' to Usage, lilypond, 2011/04/02
  • Message not available
    • Re: Issue 1576 in lilypond: Doc: Added new option 'papersize' to Usage, lilypond, 2011/04/05
• Re: stemlength, Friedrich Fischer, 2011/04/02
  • Re: stemlength, Phil Holmes, 2011/04/03
    • Re: stemlength, Friedrich Fischer, 2011/04/04
• Re: Issue 1588 in lilypond: optimizing lilypond.org speed, lilypond, 2011/04/01
• Re: Issue 1494 in lilypond: including alternate fonts, lilypond, 2011/04/01
• Issue 1590 in lilypond: Suppress continuing LyricHyphen under grace note at start of line, lilypond, 2011/04/01
  • Re: Issue 1590 in lilypond: Suppress continuing LyricHyphen under grace note at start of line, lilypond, 2011/04/09
  • Re: Issue 1590 in lilypond: Suppress continuing LyricHyphen under grace note at start of line, lilypond, 2011/04/17
• Issue 1589 in lilypond: note placement too low, lilypond, 2011/04/01
  • Re: Issue 1589 in lilypond: note placement too low, lilypond, 2011/04/01
  • Re: Issue 1589 in lilypond: note placement too low, lilypond, 2011/04/01
  • Re: Issue 1589 in lilypond: note placement too low, lilypond, 2011/04/02
  • Re: Issue 1589 in lilypond: note placement too low, lilypond, 2011/04/05
• Re: Issue 1219 in lilypond: Broken tie may become a too small dot, lilypond, 2011/04/01
• bug report on version 2.13.56, Mario Bolognani, 2011/04/01
• Re: Critical bug of midi output, Janek Warchoł, 2011/04/01

---

[Prev Period]

[Next Period]

---

Mail converted by MHonArc