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: Thu Mar 31 2011 22:30:19 -0400 Messages in reverse chronological order

[Next Period]

---

• March 31, 2011
  • Re: Issue 795 in lilypond: Beams do not take grace notes into account, lilypond, 22:30
  • Re: Issue 795 in lilypond: Beams do not take grace notes into account, lilypond, 22:26
  • Issue 1588 in lilypond: optimizing lilypond.org speed, lilypond, 21:45
  • Re: Issue 1585 in lilypond: LilyPond segfaults on beams with headless stencils, lilypond, 17:48
  • Re: Issue 1587 in lilypond: midi2ly --key option only reaches first staff, lilypond, 16:22
  • Re: Issue 1587 in lilypond: midi2ly --key option only reaches first staff, lilypond, 16:11
  • Issue 1587 in lilypond: midi2ly --key option only reaches first staff, lilypond, 16:07
  • Re: Issue 400 in lilypond: collision clef and beam, lilypond, 14:43
  • Re: Issue 76 in lilypond: beams should not collide with accidentals, lilypond, 14:39
  • Re: Issue 76 in lilypond: beams should not collide with accidentals, lilypond, 11:32
  • Re: Issue 400 in lilypond: collision clef and beam, lilypond, 11:28
  • Re: Issue 795 in lilypond: Beams do not take grace notes into account, lilypond, 11:24
  • Re: Issue 1586 in lilypond: midi cresc happens instantly, lilypond, 11:15
  • Re: Fw: Critical bug of midi output, Graham Percival, 11:11
  • Issue 1586 in lilypond: midi cresc happens instantly, lilypond, 11:11
  • Re: Issue 742 in lilypond: Delayed ties influence lyrics (even with tieWaitForNote unset), lilypond, 11:02
  • Re: Issue 1534 in lilypond: midi2ly does not show \breve or if a note lasts longer than one bar, lilypond, 10:58
  • Issue 1585 in lilypond: LilyPond segfaults on beams with headless stencils, lilypond, 08:59
  • header items: use #f or ##f ?, -Eluze, 06:32
  • Re: stemlength, Phil Holmes, 05:45
  • Re: Issue 742 in lilypond: Delayed ties influence lyrics (even with tieWaitForNote unset), lilypond, 04:52
  • Fw: Critical bug of midi output, Phil Holmes, 04:28
  • Re: Issue 1584 in lilypond: removing parser DIGIT rule, lilypond, 03:53
  • stemlength, Friedrich Fischer, 03:40
  • Re: Issue 1534 in lilypond: midi2ly does not show \breve or if a note lasts longer than one bar, lilypond, 00:16
• March 30, 2011
  • Issue 1584 in lilypond: removing parser DIGIT rule, lilypond, 21:29
  • Re: Issue 688 in lilypond: grace notes may add an hyphen at the beginning of a lyric line, lilypond, 21:25
  • Re: Issue 742 in lilypond: Delayed ties influence lyrics (even with tieWaitForNote unset), lilypond, 21:21
  • Re: Issue 839 in lilypond: Enhancement: improving midi2ly conversion, lilypond, 21:17
  • Re: Issue 1534 in lilypond: midi2ly does not show \breve or if a note lasts longer than one bar, lilypond, 21:13
  • Re: Issue 1549 in lilypond: midi2ly should output rests by default, lilypond, 21:09
  • Re: Issue 1573 in lilypond: Downstem 64th and 128th flag touchup, lilypond, 21:04
  • Re: Issue 1575 in lilypond: midi2ly --duration-quant=16 fails to display first duration, lilypond, 21:00
  • Re: Issue 1580 in lilypond: midi2ly creates invalid LilyPond input for a staff with more than four voices, lilypond, 20:56
  • Re: Issue 1578 in lilypond: Enhancement: Allows glissandi to be continuous at line breaks, lilypond, 20:52
  • Re: Issue 1569 in lilypond: 2.13.54 breaks NoteNames vertical spacing, lilypond, 20:48
  • Re: Issue 1504 in lilypond: Feathered beams reset at line break, lilypond, 20:44
  • Re: Issue 1504 in lilypond: Feathered beams reset at line break, lilypond, 20:40
  • Re: Issue 1578 in lilypond: Enhancement: Allows glissandi to be continuous at line breaks, lilypond, 20:35
  • Re: horizontal spacing: note too close to barline when time signature changes after line break, Ralph Palmer, 16:10
  • Issue 1583 in lilypond: horizontal spacing: note too close to barline when time signature changes after line break, lilypond, 16:00
  • Re: Issue 1579 in lilypond: Overextended lyrics extenders, lilypond, 10:46
  • Re: dynamic placement problem with slurred notes, Dmytro O. Redchuk, 09:03
  • dynamic placement problem with slurred notes, Peter Sisak, 08:45
• March 29, 2011
  • Re: Issue 742 in lilypond: Delayed ties influence lyrics (even with tieWaitForNote unset), lilypond, 04:10
• March 28, 2011
  • Issue 1582 in lilypond: flag variants patch, lilypond, 17:17
  • Re: Issue 1579 in lilypond: Overextended lyrics extenders, lilypond, 17:10
  • Re: \pitchedTrill causes warning when used with tie, Neil Puttock, 16:34
  • Issue 1581 in lilypond: Pitched trill between tied notes causes `unterminated tie' warning, lilypond, 16:34
  • Re: Issue 1580 in lilypond: midi2ly creates invalid LilyPond input for a staff with more than four voices, lilypond, 14:47
  • Re: Issue 1574 in lilypond: DOC: Need updated/expanded documentation of percent repeat/beat slash, lilypond, 14:40
  • Re: Issue 1580 in lilypond: midi2ly creates invalid LilyPond input for a staff with more than four voices, lilypond, 14:33
  • Issue 1580 in lilypond: midi2ly creates invalid LilyPond input for a staff with more than four voices, lilypond, 14:29
  • Re: Issue 1530 in lilypond: [PATCH] Fret diagram fixes (Issue 4176056), lilypond, 12:12
  • Re: Issue 688 in lilypond: grace notes may add an hyphen at the beginning of a lyric line, lilypond, 12:01
  • Re: Issue 773 in lilypond: melisma centered i.s.o. left-aligned when using \melisma, lilypond, 09:12
  • Re: Issue 1577 in lilypond: GrandStaff cannot contaiin RhythmicStaff, lilypond, 09:08
  • Re: Issue 1576 in lilypond: Doc: Added new option 'papersize' to Usage, lilypond, 07:13
  • Re: Issue 1579 in lilypond: Overextended lyrics extenders, lilypond, 03:53
  • Re: Issue 37 in lilypond: collision notehead and beams, lilypond, 03:01
  • Re: Issue 1518 in lilypond: DOC: add explanation of part combine functions, lilypond, 02:57
  • Re: Issue 1530 in lilypond: [PATCH] Fret diagram fixes (Issue 4176056), lilypond, 02:53
  • Re: Overextended extenders, Dmytro O. Redchuk, 02:48
  • Issue 1579 in lilypond: Overextended lyrics extenders, lilypond, 02:48
• March 27, 2011
  • Issue 1578 in lilypond: Enhancement: Allows glissandi to be continuous at line breaks, lilypond, 23:11
  • Re: Placement of outside-staff objects: bug and behaviour changebetween 2.12.3 and 2.13.54, Carl Sorensen, 18:51
  • Re: Overextended extenders, Michael Welsh Duggan, 15:05
  • Re: Overextended extenders, Michael Welsh Duggan, 14:59
  • Re: Overextended extenders, Reinhold Kainhofer, 13:00
  • Re: Overextended extenders, Phil Holmes, 12:30
  • Re: Placement of outside-staff objects: bug and behaviour changebetween 2.12.3 and 2.13.54, James Lowe, 12:24
  • Re: Overextended extenders, Phil Holmes, 12:23
  • Re: Placement of outside-staff objects: bug and behaviour changebetween 2.12.3 and 2.13.54, Frédéric Bron, 12:21
  • Re: Issue 76 in lilypond: beams should not collide with accidentals, lilypond, 12:20
  • Re: Overextended extenders, -Eluze, 12:01
  • Re: Placement of outside-staff objects: bug and behaviour changebetween 2.12.3 and 2.13.54, Trevor Daniels, 11:02
  • Re: Placement of outside-staff objects: bug and behaviour changebetween 2.12.3 and 2.13.54, Frédéric Bron, 10:50
  • Re: Placement of outside-staff objects: bug and behaviour changebetween 2.12.3 and 2.13.54, Trevor Daniels, 09:37
  • Re: Issue 76 in lilypond: beams should not collide with accidentals, lilypond, 09:26
  • Re: Issue 37 in lilypond: collision notehead and beams, lilypond, 09:22
  • Re: Issue 37 in lilypond: collision notehead and beams, lilypond, 09:18
  • Re: Issue 37 in lilypond: collision notehead and beams, lilypond, 09:14
  • Re: Placement of outside-staff objects: bug and behaviour changebetween 2.12.3 and 2.13.54, Phil Holmes, 07:29
  • Re: Placement of outside-staff objects: bug and behaviour changebetween 2.12.3 and 2.13.54, Frédéric Bron, 02:56
• March 26, 2011
  • Overextended extenders, Michael Welsh Duggan, 20:45
  • Re: Issue 1573 in lilypond: Downstem 64th and 128th flag touchup, lilypond, 18:59
  • Re: Beam collides with accidental, James Lowe, 15:01
  • Re: Issue 1569 in lilypond: 2.13.54 breaks NoteNames verticalspacing, Carl Sorensen, 14:54
  • Re: Issue 1569 in lilypond: 2.13.54 breaks NoteNames vertical spacing, lilypond, 14:49
  • Re: Beam collides with accidental, address@hidden, 14:16
  • Beam collides with accidental, Xavier Scheuer, 13:30
  • Re: Issue 1577 in lilypond: GrandStaff cannot contaiin RhythmicStaff, lilypond, 10:42
  • Re: Issue 742 in lilypond: Delayed ties influence lyrics (even with tieWaitForNote unset), lilypond, 09:39
  • Re: Issue 1569 in lilypond: 2.13.54 breaks NoteNames verticalspacing, Trevor Daniels, 04:30
  • Re: Issue 1569 in lilypond: 2.13.54 breaks NoteNames vertical spacing, lilypond, 00:48
  • Re: Issue 1569 in lilypond: 2.13.54 breaks NoteNames vertical spacing, lilypond, 00:44
• March 24, 2011
  • Re: Issue 773 in lilypond: melisma centered i.s.o. left-aligned when using \melisma, lilypond, 18:47
  • Re: Issue 773 in lilypond: melisma centered i.s.o. left-aligned when using \melisma, lilypond, 18:40
  • Re: Issue 688 in lilypond: grace notes may add an hyphen at the beginning of a lyric line, lilypond, 14:51
  • Re: spacing error possibly related to Issue 1472, Paul Scott, 14:23
  • Re: spacing error possibly related to Issue 1472, Phil Holmes, 11:35
  • Re: bug report on version 2.13.55, Phil Holmes, 11:27
  • bug report on version 2.13.55, Mario Bolognani, 09:40
  • Re: spacing error possibly related to Issue 1472, Paul Scott, 09:40
  • Re: Repeated embedded fonts in PDF documentation, Werner LEMBERG, 06:27
  • Re: Repeated embedded fonts in PDF documentation, Nick Payne, 06:23
  • Re: Repeated embedded fonts in PDF documentation, Werner LEMBERG, 04:36
  • Re: Repeated embedded fonts in PDF documentation, Carl Sorensen, 03:51
  • Re: Repeated embedded fonts in PDF documentation, Werner LEMBERG, 00:25
• March 23, 2011
  • Repeated embedded fonts in PDF documentation, Nick Payne, 23:42
  • Re: Issue 1570 in lilypond: Fixes accidental suggestions in the beam collision engraver, lilypond, 23:38
  • Re: Issue 897 in lilypond: key signatures should be inherited by all Voices (no matter their accidental style), lilypond, 23:25
  • Re: Issue 1516 in lilypond: Crash with empty \markuplines, lilypond, 23:21
  • Re: Issue 1565 in lilypond: Changing staff with manual beaming can give very long stems, lilypond, 23:12
  • Re: Issue 1569 in lilypond: 2.13.54 breaks NoteNames vertical spacing, lilypond, 22:54
  • Re: Issue 1554 in lilypond: update midi2ly version number, lilypond, 18:44
  • Re: spacing error possibly related to Issue 1472, Phil Holmes, 13:10
  • Re: Collision between acciaccatura and time signature, Phil Holmes, 13:00
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 11:47
  • Re: Issue 1569 in lilypond: 2.13.54 breaks NoteNames vertical spacing, lilypond, 09:17
  • Issue 1577 in lilypond: GrandStaff cannot contaiin RhythmicStaff, lilypond, 08:53
• March 22, 2011
  • Issue 1576 in lilypond: Doc: Added new option 'papersize' to Usage, lilypond, 22:30
  • spacing error possibly related to Issue 1472, Paul Scott, 20:08
  • Re: Issue 773 in lilypond: melisma centered i.s.o. left-aligned when using \melisma, lilypond, 19:14
  • Re: lilypond v2.13.54, -Eluze, 19:08
  • Re: Collision between maxima and lyric, address@hidden, 18:23
  • Re: Collision between maxima and lyric, Neil Puttock, 18:20
  • Re: Issue 1570 in lilypond: Fixes accidental suggestions in the beam collision engraver, lilypond, 16:31
  • Re: Issue 1575 in lilypond: midi2ly --duration-quant=16 fails to display first duration, lilypond, 16:23
  • Issue 1575 in lilypond: midi2ly --duration-quant=16 fails to display first duration, lilypond, 16:19
  • Re: Issue 1573 in lilypond: Downstem 64th and 128th flag touchup, lilypond, 16:04
  • Re: Placement of outside-staff objects: bug and behaviour change between 2.12.3 and 2.13.54, Trevor Daniels, 13:25
  • Re: Placement of outside-staff objects: bug and behaviour changebetween 2.12.3 and 2.13.54, Trevor Daniels, 13:21
  • RE: Placement of outside-staff objects: bug and behaviour change between 2.12.3 and 2.13.54, James Lowe, 11:42
  • RE: Lilypond not working on Win7 sp1, James Lowe, 11:17
  • RE: Lilypond not working on Win7 sp1, James Lowe, 11:17
  • Collision between maxima and lyric, address@hidden, 11:12
  • Collision between acciaccatura and time signature, Mick Killick, 11:00
  • Re: Lilypond not working on Win7 sp1, Colin Campbell, 09:07
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 09:06
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 07:46
  • RE: Lilypond not working on Win7 sp1, James Lowe, 07:40
  • Re: Issue 1496 in lilypond: Update Pango to 1.28.3, lilypond, 01:18
• March 21, 2011
  • Re: Placement of outside-staff objects: bug and behaviour change between 2.12.3 and 2.13.54, Joe Neeman, 22:19
  • Issue 1574 in lilypond: DOC: Need updated/expanded documentation of percent repeat/beat slash, lilypond, 21:53
  • Re: Fwd: Re: \repeat percent does not use the beat-slash stencil, Colin Campbell, 21:47
  • Re: Placement of outside-staff objects: bug and behaviour change between 2.12.3 and 2.13.54, Trevor Daniels, 20:20
  • Re: Lilypond not working on Win7 sp1, Robbie Rousseau, 20:07
  • Re: Lilypond not working on Win7 sp1, James Lowe, 19:38
  • Re: Placement of outside-staff objects: bug and behaviour change between 2.12.3 and 2.13.54, Frédéric Bron, 17:24
  • Lilypond not working on Win7 sp1, Robbie Rousseau, 15:30
  • Issue 1573 in lilypond: Downstem 64th and 128th flag touchup, lilypond, 09:16
  • Fwd: Re: \repeat percent does not use the beat-slash stencil, Colin Campbell, 08:54
  • RE: lilypond v2.13.54, James Lowe, 07:59
  • Re: Issue 34 in lilypond: Grace synchronization, lilypond, 07:44
  • Re: Issue 1571 in lilypond: ficta and manual beaming -> too long stems, lilypond, 07:22
  • Re: Issue 1571 in lilypond: ficta and manual beaming -> too long stems, lilypond, 07:18
  • Re: Issue 1570 in lilypond: Fixes accidental suggestions in the beam collision engraver, lilypond, 07:14
  • Re: Issue 1571 in lilypond: ficta and manual beaming -> too long stems, lilypond, 07:10
  • Re: Issue 1073 in lilypond: convert-ly and accented characters, lilypond, 06:05
  • Re: midi2ly crashed with UnicodeDecodeError in convert_midi(), Francisco Vila, 06:01
  • Re: Issue 1571 in lilypond: ficta and manual beaming -> too long stems, lilypond, 05:47
  • Re: midi2ly crashed with UnicodeDecodeError in convert_midi(), Dmytro O. Redchuk, 05:46
  • Re: Issue 1228 in lilypond: \override RestCollision #'positioning-done = #merge-rests-on-positioning, lilypond, 05:43
  • Re: Change chord name separator and inversion separator, separately, Dmytro O. Redchuk, 05:39
  • Issue 1572 in lilypond: Enhancement req: Change chord name separator and inversion separator, separately, lilypond, 05:39
  • Re: Release candidate 3 of 2.14 - LilyPond 2.13.54 released, Francisco Vila, 05:37
  • Re: big format for Notation Manual: unsupported compression type, Francisco Vila, 05:35
  • Re: ficta bug, Dmytro O. Redchuk, 05:30
  • Issue 1571 in lilypond: ficta and manual beaming -> too long stems, lilypond, 05:29
  • Re: Possible bug on \addlyrics in Lilypond 2.13.54, Francisco Vila, 05:25
  • ficta bug, MARC LANOISELEE, 04:20
  • Re: lilypond v2.13.54, Janek Warchoł, 02:29
  • Issue 1570 in lilypond: Fixes accidental suggestions in the beam collision engraver, lilypond, 00:15
• March 20, 2011
  • Re: Placement of outside-staff objects: bug and behaviour change between 2.12.3 and 2.13.54, Colin Campbell, 23:41
  • Re: 2.13.54 breaks NoteNames vertical spacing, Colin Campbell, 23:33
  • Issue 1569 in lilypond: 2.13.54 breaks NoteNames vertical spacing, lilypond, 23:32
  • Re: \repeat percent does not use the beat-slash stencil, Colin Campbell, 23:16
  • Re: Release candidate 3 of 2.14 - LilyPond 2.13.54 released, Frédéric Bron, 17:47
  • Re: tempo causes insertion of empty staff line, Reinhold Kainhofer, 17:42
  • Re: tempo causes insertion of empty staff line, Phil Holmes, 17:22
  • Re: Possible bug on \addlyrics in Lilypond 2.13.54, Carl Sorensen, 17:12
  • tempo causes insertion of empty staff line, Philip Stolz, 16:30
  • big format for Notation Manual: unsupported compression type, Frédéric Bron, 16:27
  • Re: Issue 1269 in lilypond: Doc: using #'non-break-align-symbols = #'() to align MetronomeMark should be documented, lilypond, 15:39
  • Issue 1568 in lilypond: ENHANCEMENT: Adds the Articulate script with documentation, lilypond, 12:21
  • critical issues, Graham Percival, 10:52
  • Issue 1567 in lilypond: Add documentation for footnotes, lilypond, 09:30
  • Re: Issue 1560 in lilypond: Lyrics can not be aligned below ossia staff, lilypond, 05:10
  • Re: Possible bug on \addlyrics in Lilypond 2.13.54, Francisco Vila, 03:26
  • Placement of outside-staff objects: bug and behaviour change between 2.12.3 and 2.13.54, Frédéric Bron, 02:53
  • Re: Issue 1566 in lilypond: Flagged notes lose flags with autobeaming and hidenotes, lilypond, 02:18
• March 19, 2011
  • Re: Release candidate 3 of 2.14 - LilyPond 2.13.54 released, Xavier Scheuer, 20:12
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 19:39
  • Re: Beaming rules may cause oddness when using hideNotes, Valentin Villenave, 19:16
  • Re: Possible bug on \addlyrics in Lilypond 2.13.54, Wim van Dommelen, 18:41
  • Possible bug on \addlyrics in Lilypond 2.13.54, Wim van Dommelen, 18:18
  • Re: lilypond v2.13.54, Trevor Daniels, 17:37
  • \repeat percent does not use the beat-slash stencil, Ed Gordijn, 14:20
  • Re: Beaming rules may cause oddness when using hideNotes, Phil Holmes, 14:17
  • Re: Beaming rules may cause oddness when using hideNotes, Carl Sorensen, 12:59
  • Re: Issue 1349 in lilypond: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used., lilypond, 12:53
  • Issue 1566 in lilypond: Flagged notes lose flags with autobeaming and hidenotes, lilypond, 09:00
  • Re: Beaming rules may cause oddness when using hideNotes, Phil Holmes, 09:00
  • Re: Beaming rules may cause oddness when using hideNotes, Xavier Scheuer, 08:32
  • Re: Beaming rules may cause oddness when using hideNotes, Phil Holmes, 07:58
  • Re: lilypond v2.13.54, Trevor Daniels, 04:11
• March 18, 2011
  • Re: lilypond v2.13.54, James Lowe, 20:27
  • Re: midi2ly crashed with UnicodeDecodeError in convert_midi(), Francisco Vila, 19:10
  • Re: midi2ly crashed with UnicodeDecodeError in convert_midi(), Jan Nieuwenhuizen, 18:58
  • Re: midi2ly crashed with UnicodeDecodeError in convert_midi(), Graham Percival, 18:53
  • Re: midi2ly crashed with UnicodeDecodeError in convert_midi(), Francisco Vila, 18:50
  • Beaming rules may cause oddness when using hideNotes, Valentin Villenave, 15:50
  • Re: midi2ly crashed with UnicodeDecodeError in convert_midi(), Jan Nieuwenhuizen, 14:26
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 14:20
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 14:16
  • Re: midi2ly crashed with UnicodeDecodeError in convert_midi(), Francisco Vila, 13:57
  • RE: midi2ly crashed with UnicodeDecodeError in convert_midi(), Jan Nieuwenhuizen, 13:20
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 12:15
  • Re: midi2ly crashed with UnicodeDecodeError in convert_midi(), Jan Nieuwenhuizen, 12:07
  • Re: midi2ly crashed with UnicodeDecodeError in convert_midi(), Francisco Vila, 12:03
  • Re: midi2ly crashed with UnicodeDecodeError in convert_midi(), Jan Nieuwenhuizen, 11:20
  • Re: Issue 1349 in lilypond: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used., lilypond, 11:08
  • Re: Issue 1073 in lilypond: convert-ly and accented characters, lilypond, 09:00
  • Re: Issue 839 in lilypond: Enhancement: improving midi2ly conversion, lilypond, 08:10
  • Re: Issue 1565 in lilypond: Changing staff with manual beaming can give very long stems, lilypond, 08:06
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 08:02
  • Re: midi2ly crashed with UnicodeDecodeError in convert_midi(), Francisco Vila, 07:46
  • Re: lilypond v2.13.54, Phil Holmes, 05:54
  • Re: Issue 773 in lilypond: melisma centered i.s.o. left-aligned when using \melisma, lilypond, 05:37
  • Re: midi2ly, Hans Aberg, 04:23
  • Re: lilypond v2.13.54, James Lowe, 04:08
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 03:41
• March 17, 2011
  • Re: Issue 400 in lilypond: collision clef and beam, lilypond, 23:30
  • Re: Issue 400 in lilypond: collision clef and beam, lilypond, 23:27
  • Re: Issue 400 in lilypond: collision clef and beam, lilypond, 23:06
  • Re: Issue 1349 in lilypond: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used., lilypond, 22:52
  • Re: Issue 1565 in lilypond: Changing staff with manual beaming can give very long stems, lilypond, 22:47
  • Re: Issue 1565 in lilypond: Changing staff with manual beaming can give very long stems, lilypond, 22:43
  • Re: Issue 1565 in lilypond: Changing staff with manual beaming can give very long stems, lilypond, 22:06
  • Re: Issue 1565 in lilypond: Changing staff with manual beaming can give very long stems, lilypond, 18:39
  • Re: Issue 1565 in lilypond: Changing staff with manual beaming can give very long stems, lilypond, 17:15
  • Re: midi2ly, Hans Aberg, 15:51
  • Re: lilypond v2.13.54, -Eluze, 13:53
  • midi2ly, Sam Britton, 13:15
  • Re: lilypond v2.13.54, Phil Holmes, 12:14
  • Re: lilypond v2.13.54, -Eluze, 11:51
  • Re: lilypond v2.13.54, Phil Holmes, 09:18
  • Re: Issue 1349 in lilypond: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used., lilypond, 09:08
  • Re: lilypond v2.13.54, -Eluze, 08:15
  • Re: lilypond v2.13.54, Phil Holmes, 05:50
• March 16, 2011
  • Re: Issue 1349 in lilypond: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used., lilypond, 19:02
  • Re: merge-rests.ily w/ text on full measure rest segfault 2.13.53 (and from git), Neil Puttock, 10:28
• March 15, 2011
  • Re: Issue 1565 in lilypond: Changing staff with manual beaming can give very long stems, lilypond, 09:23
  • Re: Issue 1565 in lilypond: Changing staff with manual beaming can give very long stems, Trevor Daniels, 09:05
  • Issue 1565 in lilypond: Changing staff with manual beaming can give very long stems, lilypond, 06:59
  • Re: Odd slur placement/collisions with stems and flags, Trevor Daniels, 04:46
  • Re: Issue 1504 in lilypond: Feathered beams reset at line break, Colin Campbell, 00:37
• March 14, 2011
  • Re: Odd slur placement/collisions with stems and flags, Bryan Previte, 19:50
  • Odd slur placement/collisions with stems and flags, Bryan Previte, 19:43
  • Change chord name separator and inversion separator, separately, Arnout Engelen, 19:19
  • Re: Issue 1504 in lilypond: Feathered beams reset at line break, Phil Holmes, 11:38
  • Re: Issue 1163 in lilypond: website "what we wrote", lilypond, 11:00
  • Re: Issue 980 in lilypond: separate git repositories for lilypad and/or gub, lilypond, 10:56
  • Re: Issue 1494 in lilypond: including alternate fonts, lilypond, 10:52
  • Re: \pitchedTrill causes warning when used with tie, Jeremy Crabtree, 09:53
  • Re: midi2ly crashed with UnicodeDecodeError in convert_midi(), Jan Nieuwenhuizen, 07:48
  • Re: midi2ly crashed with UnicodeDecodeError in convert_midi(), Graham Percival, 07:31
  • Re: Unicode: MUSICAL SYMBOL LEFT REPEAT SIGN, Mathias Linkerhand, 07:29
  • RE: \pitchedTrill causes warning when used with tie, James Lowe, 07:23
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 07:12
  • Re: midi2ly crashed with UnicodeDecodeError in convert_midi(), Jan Nieuwenhuizen, 05:26
  • Issue 1564 in lilypond: Lyrics with no attched staff slightly mispositioned, lilypond, 05:23
  • Re: Lyrics with no attched staff slightly mispositioned, Dmytro O. Redchuk, 05:22
  • Re: midi2ly crashed with UnicodeDecodeError in convert_midi(), Dmytro O. Redchuk, 05:16
  • Issue 1563 in lilypond: strange vertical line at staff begin using StaffSymbol #'staff-space, lilypond, 05:13
  • Re: strange vertical line at staff begin using StaffSymbol #'staff-space, Dmytro O. Redchuk, 05:13
  • Re: MIDI output, Jan Nieuwenhuizen, 05:12
  • Re: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, Dmytro O. Redchuk, 05:08
  • Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 05:08
  • Re: \pitchedTrill causes warning when used with tie, Dmytro O. Redchuk, 05:01
  • Issue 1561 in lilypond: emacs stuff: indent problem, lilypond, 05:00
  • Re: indent problem, Dmytro O. Redchuk, 04:59
  • MIDI output, Mario Bolognani, 04:55
  • Issue 1560 in lilypond: Lyrics can not be aligned below ossia staff, lilypond, 04:42
  • Re: Can't align lyrics below ossia staff, Dmytro O. Redchuk, 04:42
  • Re: Footnotes: empty fill-lines in header & footer, Dmytro O. Redchuk, 04:28
  • Issue 1559 in lilypond: Footnotes: empty fill-lines in header & footer, lilypond, 04:28
• March 13, 2011
  • Re: Issue 1504 in lilypond: Feathered beams reset at line break, lilypond, 22:39
  • Re: Footnotes: empty fill-lines in header & footer, Mike Solomon, 17:08
  • Re: Issue 1558 in lilypond: shorten unbeamed 32nd notes, lilypond, 15:25
  • Re: unbeamed 32nd stem is shortened by 0.25 ss to fit beamed stems better. (issue4243071), Graham Percival, 15:23
  • Re: unbeamed 32nd stem is shortened by 0.25 ss to fit beamed stems better. (issue4243071), Jan Warchoł, 14:53
  • Footnotes: empty fill-lines in header & footer, Nicolas Sceaux, 14:53
  • Re: unbeamed 32nd stem is shortened by 0.25 ss to fit beamed stems better. (issue4243071), Graham Percival, 14:16
  • Re: unbeamed 32nd stem is shortened by 0.25 ss to fit beamed stems better. (issue4243071), Graham Percival, 10:18
  • Issue 1558 in lilypond: shorten unbeamed 32nd notes, lilypond, 10:16
  • Re: Issue 1530 in lilypond: [PATCH] Fret diagram fixes (Issue 4176056), lilypond, 07:45
  • Re: unbeamed 32nd stem is shortened by 0.25 ss to fit beamed stems better. (issue4243071), Jan Warchoł, 07:36
  • Re: regression test ‘midi-volume-equaliser.ly ’, Keith OHara, 04:49
• March 12, 2011
  • Re: merge-rests.ily w/ text on full measure rest segfault 2.13.53 (and from git), Graham Percival, 19:35
  • merge-rests.ily w/ text on full measure rest segfault 2.13.53 (and from git), Jay Anderson, 18:37
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 16:59
  • Re: Problem with MIDI volume level, Jan Nieuwenhuizen, 16:21
  • Re: midi channel warning is gone, Jan Nieuwenhuizen, 16:20
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 15:49
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 08:50
• March 11, 2011
  • Re: Issue 1557 in lilypond: See if texi2html version 5.0 will work with LilyPond, lilypond, 22:51
  • Re: Issue 1557 in lilypond: See if texi2html version 5.0 will work with LilyPond, lilypond, 22:47
  • Re: Unicode: MUSICAL SYMBOL LEFT REPEAT SIGN, Patrick McCarty, 22:39
  • Re: Issue 1557 in lilypond: See if texi2html version 5.0 will work with LilyPond, lilypond, 21:50
  • Issue 1557 in lilypond: See if texi2html version 5.0 will work with LilyPond, lilypond, 20:24
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 19:10
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 19:04
  • Re: Issue 1556 in lilypond: internals and glossary should not be created for languages, lilypond, 19:00
  • Re: Issue 1418 in lilypond: regtests "cells:" field isn't documented in the CG, lilypond, 18:36
  • Issue 1556 in lilypond: internals and glossary should not be created for languages, lilypond, 18:21
  • Lyrics with no attched staff slightly mispositioned, Keith OHara, 17:59
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 17:53
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 17:26
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 15:29
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 13:16
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 12:45
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 12:30
  • midi2ly crashed with UnicodeDecodeError in convert_midi(), Christian Fillion, 11:35
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 11:33
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 10:58
  • Re: regression test ‘midi-volume-equaliser .ly’, Trevor Daniels, 10:05
  • Re: Issue 1418 in lilypond: regtests "cells:" field isn't documented in the CG, lilypond, 09:23
  • Re: Issue 1554 in lilypond: update midi2ly version number, lilypond, 07:38
  • Re: Issue 1554 in lilypond: update midi2ly version number, lilypond, 07:19
  • Re: Issue 1518 in lilypond: DOC: add explanation of part combine functions, lilypond, 07:15
  • Re: Issue 1516 in lilypond: Crash with empty \markuplines, lilypond, 07:11
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 07:07
  • Re: Issue 1516 in lilypond: Crash with empty \markuplines, lilypond, 07:02
• March 10, 2011
  • Re: Issue 1548 in lilypond: midi output should map voices to channels, lilypond, 21:48
  • midi channel warning is gone, Keith OHara, 21:48
  • Re: Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 21:38
  • Re: Issue 1516 in lilypond: Crash with empty \markuplines, lilypond, 21:35
  • Re: Issue 1518 in lilypond: DOC: add explanation of part combine functions, lilypond, 21:31
  • regression test ‘midi-volume-equaliser.ly ’, Keith E OHara, 21:23
  • Re: Issue 1325 in lilypond: Volta bracket going over to next line, lilypond, 16:53
  • Re: Issue 702 in lilypond: "Moment is not increasing" error when combining Lyrics in a sequential way, lilypond, 15:42
  • Re: strange vertical line at staff begin using StaffSymbol#'staff-space, Phil Holmes, 13:08
  • Re: strange vertical line at staff begin using StaffSymbol #'staff-space, Trevor Daniels, 12:54
  • Re: strange vertical line at staff begin using StaffSymbol #'staff-space, Neil Puttock, 12:36
  • Re: strange vertical line at staff begin using StaffSymbol #'staff-space, -Eluze, 12:35
  • Re: strange vertical line at staff begin using StaffSymbol #'staff-space, Trevor Daniels, 12:26
  • Re: strange vertical line at staff begin using StaffSymbol #'staff-space, Phil Holmes, 12:14
  • strange vertical line at staff begin using StaffSymbol #'staff-space, -Eluze, 12:03
  • Re: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, Graham Percival, 09:43
  • Re: Staff Stretching problem in 2.13.50+, Graham Percival, 09:39
  • Re: Issue 1418 in lilypond: regtests "cells:" field isn't documented in the CG, lilypond, 09:18
  • Re: Issue 1418 in lilypond: regtests "cells:" field isn't documented, lilypond, 08:24
  • Issue 1555 in lilypond: Multiple warnings concerning staff-affinities, lilypond, 08:10
  • Re: Issue 1553 in lilypond: Staff stretching problem in 2.13.50+, lilypond, 07:11
  • Re: Issue 1554 in lilypond: update midi2ly version number, lilypond, 07:06
  • Re: \pitchedTrill causes warning when used with tie, Phil Holmes, 04:54
  • Re: Issue 1554 in lilypond: Midi2ly has hardcoded LP version, lilypond, 01:13
• March 09, 2011
  • Re: Issue 1533 in lilypond: midi2ly makes octave mistakes for subsequent voices in relative mode, lilypond, 23:23
  • Issue 1554 in lilypond: Midi2ly has hardcoded LP version, lilypond, 23:19
  • Re: \pitchedTrill causes warning when used with tie, Jeremy Crabtree, 17:33
  • Re: How to tell lilypond some barlines have width, Laura Conrad, 17:21
  • Re: How to tell lilypond some barlines have width, Neil Puttock, 16:40
  • Re: Issue 737 in lilypond: Enhancement: support for footnotes and/or endnotes., lilypond, 16:18
  • Re: \pitchedTrill causes warning when used with tie, James Lowe, 15:05
  • Re: Issue 1553 in lilypond: Staff stretching problem in 2.13.50+, lilypond, 13:38
  • Re: \pitchedTrill causes warning when used with tie, Phil Holmes, 13:35
  • Re: Staff Stretching problem in 2.13.50+, James Lowe, 13:10
  • Re: Issue 1553 in lilypond: Staff stretching problem in 2.13.50+, lilypond, 12:49
  • \pitchedTrill causes warning when used with tie, Jeremy Crabtree, 12:40
  • Re: indent problem, David Bobroff, 12:39
  • Re: Issue 1553 in lilypond: Staff stretching problem in 2.13.50+, lilypond, 12:36
  • Re: indent problem, Graham Percival, 12:34
  • Re: Staff Stretching problem in 2.13.50+, Keith OHara, 12:25
  • Re: How to tell lilypond some barlines have width, Laura Conrad, 11:02
  • Re: indent problem, David Bobroff, 09:38
  • Re: indent problem, Phil Holmes, 09:32
  • Re: Issue 1533 in lilypond: midi2ly makes octave mistakes for subsequent voices in relative mode, lilypond, 09:28
  • Re: Staff Stretching problem in 2.13.50+, Colin Campbell, 08:51
  • Issue 1553 in lilypond: Staff stretching problem in 2.13.50+, lilypond, 08:50
  • Re: Staff Stretching problem in 2.13.50+, Graham Percival, 07:54
  • Re: Staff Stretching problem in 2.13.50+, James Lowe, 07:36
  • Re: Issue 1541 in lilypond: [PATCH] Cleaning Feta flags code (issue4236043), lilypond, 06:37
  • indent problem, address@hidden, 03:35
  • Re: Issue 1552 in lilypond: Style 'voice accidentals incorrectly typeset when two voices immediately preceded by different single voice, lilypond, 03:28
  • Re: Staff Stretching problem in 2.13.50+, Keith OHara, 03:18
  • Staff Stretching problem in 2.13.50+, James Lowe, 01:50
• March 08, 2011
  • Re: Issue 1534 in lilypond: midi2ly does not show \breve or if a note lasts longer than one bar, lilypond, 23:00
  • Re: Issue 1533 in lilypond: midi2ly makes octave mistakes for subsequent voices in relative mode, lilypond, 22:12
  • Re: Issue 1533 in lilypond: midi2ly makes octave mistakes for subsequent voices in relative mode, lilypond, 21:26
  • Re: Problem with MIDI volume level, Neil Puttock, 16:29
  • Issue 1552 in lilypond: Style 'voice accidentals incorrectly typeset when two voices immediately preceded by different single voice, lilypond, 11:18
  • Re: Issue 897 in lilypond: key signatures should be inherited by all Voices (no matter their accidental style), lilypond, 09:24
  • Re: Issue 897 in lilypond: key signatures should be inherited by all Voices (no matter their accidental style), lilypond, 09:20
  • Re: Issue 897 in lilypond: key signatures should be inherited by all Voices (no matter their accidental style), lilypond, 08:04
  • Re: Issue 897 in lilypond: key signatures should be inherited by all Voices (no matter their accidental style), lilypond, 04:56
  • Problem with MIDI volume level, Zoltan Selyem, 04:35
  • Re: Issue 1059 in lilypond: left-over strings in bibliography, lilypond, 00:21
  • Re: Issue 1450 in lilypond: Collision between slur and text in les-nereides regtest, lilypond, 00:10
• March 07, 2011
  • Re: Issue 897 in lilypond: key signatures should be inherited by all Voices (no matter their accidental style), lilypond, 18:48
  • Re: Issue 649 in lilypond: Let accidentals on tied notes across a break be valid for subsequent notes, lilypond, 17:45
  • Re: Issue 1518 in lilypond: DOC: add explanation of part combine functions, lilypond, 17:30
  • Re: Issue 748 in lilypond: Modes should support quarter-tones, lilypond, 17:26
  • Re: Issue 649 in lilypond: Let accidentals on tied notes across a break not be valid for subsequent notes, lilypond, 17:19
  • Re: Unnecessary accidental after tied note at the beginning of a new system, James Lowe, 14:52
  • Re: Issue 1488 in lilypond: [PATCH]harmonics and slides (issue3590041), lilypond, 08:08
  • horizontal spacing: note too close to barline when time signature changes after line break, Janek Warchoł, 02:48
  • Re: lilypond-book crashes on missing .ly file, Laura Conrad, 01:18
• March 06, 2011
  • Re: Issue 1518 in lilypond: DOC: add explanation of part combine functions, lilypond, 23:47
  • Re: Unnecessary accidental after tied note at the beginning of a new system, Keith OHara, 23:03
  • Re: Issue 737 in lilypond: Enhancement: support for footnotes and/or endnotes., lilypond, 21:39
  • Re: Issue 1516 in lilypond: Crash with empty \markuplines, lilypond, 21:32
  • Re: Issue 1518 in lilypond: DOC: add explanation of part combine functions, lilypond, 21:23
  • Re: Issue 1516 in lilypond: Crash with empty \markuplines, lilypond, 21:18
  • Re: lilypond-book crashes on missing .ly file, Colin Campbell, 21:09
  • Re: Issue 1488 in lilypond: [PATCH]harmonics and slides (issue3590041), lilypond, 17:02
  • Re: Issue 1550 in lilypond: Cannot place ossia staves with lyrics correctly, lilypond, 16:50
  • Re: Issue 1545 in lilypond: Volta repeat marks are misplaced in some circumstances, lilypond, 16:47
  • Re: Issue 1540 in lilypond: erroneous output from \displayLilyMusic when chord has only 1 note, lilypond, 16:46
  • Re: Issue 1551 in lilypond: Lyrics to the end of an ossia staff cause errors, lilypond, 16:14
  • Re: Issue 1488 in lilypond: [PATCH]harmonics and slides (issue3590041), lilypond, 13:41
  • Re: Unnecessary accidental after tied note at the beginning of a new system, Neil Puttock, 13:35
  • RE: Unnecessary accidental after tied note at the beginning of a new system, Peter Sisak, 11:42
  • Unnecessary accidental after tied note at the beginning of a new system, Zoltan Selyem, 11:34
  • Re: Issue 1550 in lilypond: Cannot place ossia staves with lyrics correctly, lilypond, 09:26
  • Re: Spacing problems, James Lowe, 08:29
  • Re: Issue 1550 in lilypond: Cannot place ossia staves with lyrics correctly, lilypond, 06:11
  • Re: Issue 1551 in lilypond: Lyrics to the end of an ossia staff cause errors, lilypond, 01:08
• March 05, 2011
  • Re: Issue 1550 in lilypond: Cannot place ossia staves with lyrics correctly, lilypond, 19:21
  • Re: Issue 1550 in lilypond: Cannot place ossia staves with lyrics correctly, lilypond, 18:35
  • Re: Issue 897 in lilypond: key signatures should be inherited by all Voices (no matter their accidental style), lilypond, 17:20
  • Re: Issue 1488 in lilypond: [PATCH]harmonics and slides (issue3590041), lilypond, 13:30
  • Re: Issue 1541 in lilypond: [PATCH] Cleaning Feta flags code (issue4236043), lilypond, 13:26
  • Issue 1551 in lilypond: Lyrics to the end of an ossia staff cause errors, lilypond, 11:54
  • Re: Spacing problems, Phil Holmes, 11:49
  • Issue 1550 in lilypond: Cannot place ossia staves with lyrics correctly, lilypond, 11:47
  • Re: Spacing problems, Neil Puttock, 10:47
  • Re: Spacing problems, Phil Holmes, 10:01
  • Re: Issue 1488 in lilypond: [PATCH]harmonics and slides (issue3590041), lilypond, 09:38
  • Re: Spacing problems, Joe Neeman, 09:29
  • Re: Spacing problems, Neil Puttock, 09:18
  • Re: Spacing problems, Neil Puttock, 09:07
  • Re: Spacing problems, Joe Neeman, 08:38
  • Re: Spacing problems, Phil Holmes, 07:23
• March 04, 2011
  • Re: Spacing problems, Carl Sorensen, 19:33
  • Re: Issue 737 in lilypond: Enhancement: support for footnotes and/or endnotes., lilypond, 16:17
  • Re: Issue 1467 in lilypond: [PATCH] Doc: Rewrite NR 3.2 Titles and headers. (issue3667041), lilypond, 16:13
  • Re: Issue 1494 in lilypond: including alternate fonts, lilypond, 16:11
  • Re: Issue 1496 in lilypond: Update Pango to 1.28.3, lilypond, 16:04
  • Re: Issue 1549 in lilypond: midi2ly should output rests by default, lilypond, 15:35
  • Issue 1549 in lilypond: midi2ly should output rests by default, lilypond, 15:14
  • Re: Spacing problems, Neil Puttock, 15:10
  • Re: Issue 1488 in lilypond: [PATCH]harmonics and slides (issue3590041), lilypond, 15:10
  • Spacing problems, Phil Holmes, 13:25
  • Re: Issue 1059 in lilypond: left-over strings in bibliography, lilypond, 11:30
  • Re: Issue 1548 in lilypond: midi output should map voices to channels, lilypond, 08:12
  • Issue 1548 in lilypond: midi output should map voices to channels, lilypond, 08:07
  • Re: Issue 839 in lilypond: Enhancement: improving midi2ly conversion, lilypond, 08:03
  • lilypond-book crashes on missing .ly file, Laura Conrad, 07:57
  • Re: Issue 748 in lilypond: Modes should support quarter-tones, lilypond, 07:34
• March 03, 2011
  • Can't align lyrics below ossia staff, Dénes Harmath, 19:17
  • Re: Issue 1059 in lilypond: left-over strings in bibliography, lilypond, 15:51
  • Re: Issue 1059 in lilypond: left-over strings in bibliography, lilypond, 15:03
  • Re: Issue 1535 in lilypond: [PATCH] Adding the Tweak_engraver tothe Dynamics context, Colin Campbell, 11:53
  • Re: Issue 1516 in lilypond: Crash with empty \markuplines, lilypond, 09:02
  • Re: Issue 1516 in lilypond: Crash with empty \markuplines, lilypond, 07:38
  • Re: Issue 1522 in lilypond: Windows - problem with accented characters in file name, lilypond, 07:32
  • Re: abandoned bug reports, Graham Percival, 06:58
  • Re: Issue 1535 in lilypond: [PATCH] Adding the Tweak_engraver tothe Dynamics context, Phil Holmes, 06:17
  • Re: Issue 1535 in lilypond: [PATCH] Adding the Tweak_engraver tothe Dynamics context, Graham Percival, 06:04
  • Re: Issue 897 in lilypond: key signatures should be inherited by all Voices (no matter their accidental style), lilypond, 05:54
  • Re: Issue 1522 in lilypond: Windows - problem with accented characters in file name, lilypond, 05:32
  • Re: Issue 1454 in lilypond: lilybuntu 3, lilypond, 05:29
  • Re: Issue 1517 in lilypond: Add dots to tocItemMarkup, lilypond, 05:25
  • Re: Issue 1528 in lilypond: clarinet key names, lilypond, 05:21
  • Re: Issue 1533 in lilypond: midi2ly makes octave mistakes for subsequent voices in relative mode, lilypond, 05:16
  • Re: Issue 1535 in lilypond: [PATCH] Adding the Tweak_engraver tothe Dynamics context, Phil Holmes, 05:13
  • Re: Issue 1534 in lilypond: midi2ly does not show \breve or if a note lasts longer than one bar, lilypond, 05:12
  • Re: Issue 1211 in lilypond: [PATCH]Optimizations for pure-height approximations. (issue1817045), lilypond, 05:08
  • Re: Issue 1510 in lilypond: DOC: add explanation of -dlinclude-settings cmd line option, lilypond, 05:04
  • Re: Issue 1535 in lilypond: [PATCH] Adding the Tweak_engraver tothe Dynamics context, Graham Percival, 05:01
  • Re: Issue 1527 in lilypond: exact modal inversion, lilypond, 04:50
  • Re: Issue 1535 in lilypond: [PATCH] Adding the Tweak_engraver to the Dynamics context, lilypond, 04:46
  • Re: Issue 1535 in lilypond: [PATCH] Adding the Tweak_engraver tothe Dynamics context, Phil Holmes, 04:45
  • Re: Issue 1445 in lilypond: Doc: Snippet addition in NR 2.1 Vocal music, lilypond, 04:41
  • Re: Issue 1445 in lilypond: Doc: Snippet addition in NR 2.1 Vocal music, lilypond, 04:37
• March 02, 2011
  • Re: Issue 1545 in lilypond: Volta repeat marks are misplaced in some circumstances, lilypond, 20:32
  • Re: Issue 1442 in lilypond: staff-staff padding all appears after the last nonstaff, lilypond, 19:04
  • Re: Issue 1527 in lilypond: exact modal inversion, Trevor Daniels, 18:59
  • Re: Issue 1535 in lilypond: [PATCH] Adding the Tweak_engraver to the Dynamics context, Trevor Daniels, 18:56
  • Re: skipTypesetting skipping more, Robin Bannister, 14:58
  • Re: Issue 1535 in lilypond: [PATCH] Adding the Tweak_engraver to the Dynamics context, lilypond, 14:55
  • Re: Issue 1527 in lilypond: exact modal inversion, lilypond, 13:51
  • Re: Issue 1536 in lilypond: [PATCH] Doc -- Clarify instructions on autobeam settings, lilypond, 13:47
  • Re: Issue 1535 in lilypond: [PATCH] Adding the Tweak_engraver to the Dynamics context, lilypond, 13:43
  • Re: Issue 1538 in lilypond: improving the transition between full-length and shortened stems, lilypond, 13:38
  • Re: Issue 1532 in lilypond: completion_heads_engraver mangles original durations, lilypond, 13:34
  • Re: Issue 1445 in lilypond: Doc: Snippet addition in NR 2.1 Vocal music, lilypond, 13:33
  • Re: Issue 1531 in lilypond: midi2ly eats notes, lilypond, 13:31
  • Re: Issue 1528 in lilypond: clarinet key names, lilypond, 13:22
  • Re: Issue 1527 in lilypond: exact modal inversion, lilypond, 13:18
  • Re: Issue 1522 in lilypond: Windows - problem with accented characters in file name, lilypond, 13:14
  • Re: Issue 1519 in lilypond: StaffGrouper properties does not apply to "second level" StaffGroup, lilypond, 13:10
  • Re: skipTypesetting skipping more, Neil Puttock, 13:09
  • Re: Issue 1470 in lilypond: Change keep-inside-line defaults to true, lilypond, 13:06
  • Re: Issue 1445 in lilypond: Doc: Snippet addition in NR 2.1 Vocal music, lilypond, 13:02
  • Re: Issue 1442 in lilypond: staff-staff padding all appears after the last nonstaff, lilypond, 12:58
  • Re: Issue 1399 in lilypond: extraNatural is quietly set to #f as part of setting the modern-* or piano-* styles, lilypond, 12:54
  • Re: Issue 1399 in lilypond: extraNatural is quietly set to #f as part of setting the modern-* or piano-* styles, lilypond, 12:49
  • Re: Issue 1450 in lilypond: Collision between slur and text in les-nereides regtest, lilypond, 11:14
  • Re: Issue 1521 in lilypond: transition between full-length and shortened stems, lilypond, 10:52
  • Re: Issue 1544 in lilypond: Error with including custom text fonts, lilypond, 09:49
  • Re: abandoned bug reports, Phil Holmes, 09:35
  • Re: Absence, Phil Holmes, 09:31
  • Absence, Ralph Palmer, 07:48
  • Re: abandoned bug reports, Ralph Palmer, 07:44
  • Re: abandoned bug reports, Ralph Palmer, 07:35
  • Re: Too many colliding rests, Ralph Palmer, 07:26
  • Issue 1547 in lilypond: Too many colliding resrts, lilypond, 07:24
  • Re: Issue 1318 in lilypond: midi2ly broken on Mac OS X, lilypond, 05:57
  • Re: skipTypesetting skipping more, Robin Bannister, 04:59
  • Re: Issue 1264 in lilypond: Enhancement: defining dynamics on-the-fly (with postfix syntax), lilypond, 03:22
  • Re: Issue 1543 in lilypond: Skiptypesetting overrides \break and barline type, lilypond, 03:09
  • Issue 1546 in lilypond: breve collides with heads in other voice in short intervals, lilypond, 02:46
  • Re: Issue 748 in lilypond: Modes should support quarter-tones, lilypond, 02:28
  • Re: Issue 1530 in lilypond: [PATCH] Fret diagram fixes (Issue 4176056), lilypond, 02:06
  • Re: Issue 1545 in lilypond: Volta repeat marks are misplaced in some circumstances, lilypond, 01:40
• March 01, 2011
  • Re: No Lilypond output with XeLaTex, Joe Neeman, 19:25
  • Re: Issue 1540 in lilypond: erroneous output from \displayLilyMusic when chord has only 1 note, lilypond, 18:37
  • Re: Issue 1543 in lilypond: Skiptypesetting overrides \break and barline type, lilypond, 18:15
  • RE: No Lilypond output with XeLaTex, James Lowe, 12:55
  • Re: Issue 1545 in lilypond: Volta repeat marks are misplaced in somecircumstances, Phil Holmes, 11:21
  • Issue 1545 in lilypond: Volta repeat marks are misplaced in some circumstances, lilypond, 11:18
  • Re: Bass figures are not horizontally aligned to whole notes, Reinhold Kainhofer, 10:35
  • Re: Bass figures are not horizontally aligned to whole notes, Bertrand Bordage, 09:56
  • Re: Bass figures are not horizontally aligned to whole notes, Francisco Vila, 09:48
  • Re: Bass figures are not horizontally aligned to whole notes, Bertrand Bordage, 09:30
  • Re: Bass figures are not horizontally aligned to whole notes, Dmytro O. Redchuk, 09:23
  • Re: Bass figures are not horizontally aligned to whole notes, Francisco Vila, 09:14
  • Bass figures are not horizontally aligned to whole notes, Bertrand Bordage, 08:03
  • Re: Issue 1470 in lilypond: Change keep-inside-line defaults to true, lilypond, 04:12
  • Re: Issue 1517 in lilypond: Add dots to tocItemMarkup, lilypond, 04:08
  • Re: Unicode: MUSICAL SYMBOL LEFT REPEAT SIGN, Mathias Linkerhand, 02:47

---

[Prev Period]

[Next Period]

---

Mail converted by MHonArc