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

bug-lilypond (date)

[Thread Index][Top][All Lists]

Advanced

[Prev Period]

Last Modified: Sat Apr 30 2011 20:49:48 -0400 Messages in reverse chronological order

[Next Period]

---

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

---

[Prev Period]

[Next Period]

---

Mail converted by MHonArc