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: Wed Jun 30 2010 23:31:29 -0400 Messages in reverse chronological order

[Next Period]

---

• June 30, 2010
  • Re: Bad position of dot in polyphonic disposition with crossed voices, Dmytro O. Redchuk, 23:31
  • Re: Bad position of dot in polyphonic disposition with crossed voices, Ralph Palmer, 19:58
  • Bad position of dot in polyphonic disposition with crossed voices, J . F . Lucarelli, 18:08
  • Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly, lilypond, 17:51
  • Re: Issue 1162 in lilypond: website bibliography, lilypond, 15:42
  • Re: Issue 1162 in lilypond: website bibliography, lilypond, 15:34
  • Re: top-posting check, Graham Percival, 12:42
  • top-posting check, Graham Percival, 12:27
  • Re: Tall system makes 2.13.26 give other systems too much vertical space, drl, 12:05
  • Issue 1163 in lilypond: website "what we wrote", lilypond, 11:32
  • Issue 1162 in lilypond: website bibliography, lilypond, 11:28
  • Issue 1161 in lilypond: Lyrics is not centered with CENTER affinity if there is another Lyrics with one of UP or DOWN, lilypond, 04:16
  • Re: Issue 1160 in lilypond: css overrides for ie7, Phil Holmes, 03:40
  • Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly, lilypond, 03:39
• June 29, 2010
  • Re: Bug in scipt placement in chords?, Neil Puttock, 20:09
  • Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly, lilypond, 19:32
  • Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly, lilypond, 19:23
  • Re: Issue 1157 in lilypond: Ended Lyrics add extra space between notes, lilypond, 19:08
  • Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly, lilypond, 18:58
  • Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly, lilypond, 18:38
  • Re: Issue 1062 in lilypond: Pure-height of a system only takes staves into account, but not other objects, lilypond, 18:34
  • Re: Issue 1159 in lilypond: Fine-tuning manual beaming, lilypond, 18:30
  • Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly, lilypond, 18:15
  • Re: Issue 1160 in lilypond: css overrides for ie7, lilypond, 18:11
  • Re: Issue 1160 in lilypond: css overrides for ie7, lilypond, 16:47
  • Re: Issue 1160 in lilypond: css overrides for ie7, lilypond, 16:14
  • Re: Issue 1160 in lilypond: css overrides for ie7, lilypond, 15:54
  • Re: Issue 1160 in lilypond: css overrides for ie7, lilypond, 15:50
  • Re: Issue 1043 in lilypond: beams no longer count towards boundary boxes, lilypond, 15:35
  • Re: Issue 1160 in lilypond: css overrides for ie7, lilypond, 14:37
  • Re: Bug in scipt placement in chords?, Phil Holmes, 12:31
  • Re: Issue 1160 in lilypond: css overrides for ie7, Trevor Daniels, 12:30
  • Re: Bug in scipt placement in chords?, Graham Percival, 12:16
  • Re: Bug in scipt placement in chords?, Phil Holmes, 12:11
  • Re: Bug in scipt placement in chords?, Graham Percival, 12:06
  • Issue 1160 in lilypond: css overrides for ie7, lilypond, 12:01
  • Issue 1159 in lilypond: Fine-tuning manual beaming, lilypond, 10:23
  • Re: Manual beaming, Phil Holmes, 10:23
  • Re: Manual beaming, Carl Sorensen, 10:10
  • Bug in scipt placement in chords?, Phil Holmes, 10:01
  • Re: Issue 1038 in lilypond: more technical website items, lilypond, 08:28
  • Re: Tall system makes 2.13.26 give other systems too much vertical space, Boris Shingarov, 07:16
  • Issue 1158 in lilypond: [Doc Patch] Re: (2.13.x) bottom-system-spacing, lilypond, 06:44
  • Tall system makes 2.13.26 give other systems too much vertical space, Richard Sabey, 03:50
  • Issue 1157 in lilypond: Ended Lyrics add extra space between notes, lilypond, 02:52
• June 28, 2010
  • Re: issue 1155 in lilypond: remove MODULE_GC_KLUDGE blocks from the code base, lilypond, 19:14
  • Re: issue 1155 in lilypond: remove MODULE_GC_KLUDGE blocks from the code base, lilypond, 18:54
  • Manual beaming, Phil Holmes, 12:36
  • Re: Issue 1137 in lilypond: \bassFigureExtendersOn regression, lilypond, 11:16
  • Re: Issue 1147 in lilypond: Typo in documentation link for 2.13, lilypond, 11:14
  • Re: Issue 1139 in lilypond: 'inter-loose-line-spacing #'stretchability leads to collision under some conditions, lilypond, 11:12
  • Re: Issue 1142 in lilypond: \pageBreak + system-count + lyrics : programming error: bounds of this piece aren't breakable., lilypond, 11:03
  • Re: Issue 1141 in lilypond: \pageBreak "disables" system-count, lilypond, 10:59
  • Re: Issue 1146 in lilypond: Time signature problem in example for large projects, lilypond, 10:55
  • Re: Issue 1123 in lilypond: 16th and shorter notes (not beamed) have ugly defects, lilypond, 10:51
  • Re: Issue 1123 in lilypond: 16th and shorter notes (not beamed) have ugly defects, lilypond, 10:18
  • bug backlog finished; please re-report anything missing, Graham Percival, 10:01
  • lilypond, buffiere, 09:50
  • Re: Issue 1155 in lilypond: remove MODULE_GC_KLUDGE blocks from the code base, lilypond, 02:05
• June 27, 2010
  • Re: Remove kludge in Module Code to support Guile V1.6 (MODULE_GC_KLUDGE conditional compilation), Ian Hulin, 19:39
  • Re: Issue 1117 in lilypond: PATCH Woodwind diagrams (issue1425041), lilypond, 18:06
  • Re: Issue 1134 in lilypond: Notes in different voices do not treat accidentals properly, lilypond, 18:00
  • Re: Issue 1137 in lilypond: \bassFigureExtendersOn regression, lilypond, 17:55
  • Re: Issue 1123 in lilypond: 16th and shorter notes (not beamed) have ugly defects, lilypond, 17:51
  • Re: Issue 804 in lilypond: Code cleaning: checking types-conversion issues and other build warnings, lilypond, 17:47
  • Re: Issue 804 in lilypond: Code cleaning: checking types-conversion issues and other build warnings, lilypond, 17:43
  • Re: Issue 1144 in lilypond: [PATCH] 100+ warnings (issue1724041), lilypond, 17:39
  • Re: Issue 1022 in lilypond: \chordmode neglects point-and-click, lilypond, 17:35
  • Re: Issue 997 in lilypond: RehearsalMarks are not kept inside the page, lilypond, 17:29
  • Re: Issue 1149 in lilypond: Uneven spacing with uniform stretching, lilypond, 17:19
  • Re: Issue 1156 in lilypond: Continuing slur across line containing only spacer rests leads to allocation error, lilypond, 17:15
  • Re: Issue 1156 in lilypond: Continuing slur across line containing only spacer rests leads to allocation error, lilypond, 17:07
  • Re: Issue 1156 in lilypond: Continuing slur across line containing only spacer rests leads to allocation error, lilypond, 16:58
  • Re: Issue 1156 in lilypond: Continuing slur across line containing only spacer rests leads to allocation error, lilypond, 16:50
  • Re: Issue 1156 in lilypond: Continuing slur across line containing only spacer rests leads to allocation error, lilypond, 16:14
  • Re: Windows 7, Graham Percival, 14:05
  • Re: Windows 7, Phil Holmes, 13:50
  • Re: Windows 7, Phil Holmes, 13:47
  • Re: Issue 989 in lilypond: ensure that no information is only intheregtests, Phil Holmes, 11:27
  • Re: Crash on bad_alloc, Carl Sorensen, 10:14
  • Re: Issue 1156 in lilypond: Continuing slur across line containing only spacer rests leads to allocation error, lilypond, 10:01
  • Re: Crash on bad_alloc, Phil Holmes, 05:48
  • Re: Issue 1156 in lilypond: Memory allocation problem, lilypond, 05:43
  • Re: Vertical spacing regression !?, Arno Waschk, 04:35
• June 26, 2010
  • Re: Crash on bad_alloc, Ben Englert, 22:17
  • Re: Vertical spacing regression !?, Joe Neeman, 13:21
  • Re: Crash on bad_alloc, Phil Holmes, 12:51
  • Re: Issue 1062 in lilypond: Pure-height of a system only takes staves into account, but not other objects, lilypond, 12:51
  • Re: Issue 989 in lilypond: ensure that no information is only inthe regtests, Phil Holmes, 12:51
  • Re: Crash on bad_alloc, Carl Sorensen, 12:25
  • Re: Issue 989 in lilypond: ensure that no information is only in the regtests, lilypond, 11:11
  • Re: Issue 989 in lilypond: ensure that no information is only in the regtests, lilypond, 11:07
  • Re: Issue 1153 in lilypond: Regression test broken: measure-grouping.ly, lilypond, 10:34
  • Re: Issue 1015 in lilypond: doc line width, Phil Holmes, 10:31
  • Re: Vertical spacing regression !?, Arno Waschk, 07:50
  • Re: Crash on bad_alloc, Phil Holmes, 06:39
  • Issue 1156 in lilypond: Memory allocation problem, lilypond, 06:38
  • Re: Vertical spacing regression !?, Arno Waschk, 05:33
  • Re: Issue 1152 in lilypond: Regression: collisions with accidentals, lilypond, 05:09
  • Re: Unicode rendering problems, Patrick McCarty, 05:09
  • Re: Issue 1152 in lilypond: Regression: collisions with accidentals, lilypond, 03:56
  • Re: Issue 1152 in lilypond: Regression: collisions with accidentals, lilypond, 02:29
  • Re: Issue 1148 in lilypond: makelsr should look for local convert-ly, lilypond, 02:09
• June 25, 2010
  • Re: Windows 7, Graham Percival, 23:17
  • Re: Font selection problem in Lilypond, Patrick McCarty, 22:00
  • Re: Remove kludge in Module Code to support Guile V1.6 (MODULE_GC_KLUDGE conditional compilation), Patrick McCarty, 21:43
  • Issue 1155 in lilypond: remove MODULE_GC_KLUDGE blocks from the code base, lilypond, 21:43
  • Re: Issue 1149 in lilypond: Uneven spacing with uniform stretching, lilypond, 19:49
  • Re: Issue 1151 in lilypond: cueDuring with 2 quoted voices, lilypond, 19:41
  • RE: Windows 7, James Lowe, 19:34
  • Re: \set tupletSpannerDuration & multiple voices, Xavier Scheuer, 19:13
  • Re: \set tupletSpannerDuration & multiple voices, Nathan Chou, 19:06
  • Re: \set tupletSpannerDuration & multiple voices, Xavier Scheuer, 18:56
  • \set tupletSpannerDuration & multiple voices, Nathan Chou, 18:49
  • Re: Issue 1150 in lilypond: RehearsalMark at start of line should not be printed above the clef, lilypond, 17:55
  • Re: Issue 1150 in lilypond: RehearsalMark at start of line should not be printed above the clef, lilypond, 17:53
  • Re: Issue 1015 in lilypond: doc line width, lilypond, 17:42
  • Re: Bug lists, Xavier Scheuer, 17:28
  • Re: Issue 1118 in lilypond: [PATCH] Experimental support for woff fonts in svg, lilypond, 16:43
  • Re: Issue 1150 in lilypond: RehearsalMark at start of line should not be printed above the clef, lilypond, 16:38
  • Re: Bug lists, Graham Percival, 16:20
  • Re: Issue 1148 in lilypond: makelsr should look for local convert-ly, lilypond, 16:18
  • Re: Issue 1150 in lilypond: RehearsalMark at start of line should not be printed above the clef, lilypond, 16:13
  • Issue 1154 in lilypond: Slur and Tie subproperties for 'details should be documented, lilypond, 16:01
  • Re: Issue 1150 in lilypond: RehearsalMark at start of line should not be printed above the clef, lilypond, 15:51
  • Issue 1153 in lilypond: Regression test broken: measure-grouping.ly, lilypond, 15:48
  • Re: Changing conducting signs, Patrick McCarty, 15:46
  • Re: Issue 1151 in lilypond: cueDuring with 2 quoted voices, lilypond, 15:45
  • Issue 1152 in lilypond: Regression: collisions with accidentals, lilypond, 15:41
  • Re: collision bug?, Patrick McCarty, 15:26
  • Re: Issue 1129 in lilypond: Font styles return to default when font size changed, lilypond, 14:46
  • Re: Vertical spacing regression !?, Joe Neeman, 14:00
  • Crash on bad_alloc, Ben Englert, 13:57
  • Re: Re: Connected arpeggios may collide with previos chord., Phil Holmes, 13:54
  • Issue 1149 in lilypond: Uneven spacing with uniform stretching, lilypond, 13:53
  • Re: uneven spacing with uniform-stretching, Phil Holmes, 13:53
  • Re: RehearsalMark and Barline placement at the beginning of a line, Phil Holmes, 13:53
  • Issue 1150 in lilypond: RehearsalMark at start of line should not be printed above the clef, lilypond, 13:53
  • Re: \cueDuring with 2 quoted voices, Phil Holmes, 13:53
  • Issue 1151 in lilypond: cueDuring with 2 quoted voices, lilypond, 13:53
  • Re: title not centered, Phil Holmes, 13:53
  • Re: why is it taking so long?!?! (was: title not centered), Phil Holmes, 13:53
  • Bug lists, Phil Holmes, 13:53
  • Windows 7, Phil Holmes, 13:51
  • Re: Issue 1015 in lilypond: doc line width, lilypond, 13:51
  • Re: Issue 1015 in lilypond: doc line width, lilypond, 13:51
  • Re: Vertical spacing regression !?, Joe Neeman, 13:47
  • Re: Vertical spacing regression !?, Arno Waschk, 13:45
• June 24, 2010
  • Re: Issue 1147 in lilypond: Typo in documentation link for 2.13, lilypond, 09:11
  • Re: Issue 809 in lilypond: Support for older MS systems is broken, lilypond, 09:07
  • Re: buggy image in documentation?, Graham Percival, 09:04
  • Re: Vertical spacing regression !?, Arno Waschk, 08:05
  • Re: Issue 291 in lilypond: \glissando doesn't work properly with chords, lilypond, 07:31
  • (no subject), Bryan Previte, 05:26
• June 23, 2010
  • Re: Issue 809 in lilypond: Support for older MS systems is broken, lilypond, 19:25
  • Re: Issue 1147 in lilypond: Typo in documentation link for 2.13, lilypond, 19:18
  • Re: Issue 1146 in lilypond: Time signature problem in example for large projects, lilypond, 16:31
  • Re: Issue 1123 in lilypond: 16th and shorter notes (not beamed) have ugly defects, lilypond, 16:27
  • Re: Issue 1146 in lilypond: Time signature problem in example for large projects, lilypond, 16:19
  • Re: Issue 1147 in lilypond: Typo in documentation link for 2.13, lilypond, 16:15
  • Re: Issue 1148 in lilypond: makelsr should look for local convert-ly, lilypond, 15:59
  • Re: Issue 1147 in lilypond: Typo in documentation link for 2.13, lilypond, 12:55
  • Re: Issue 1148 in lilypond: makelsr should look for local convert-ly, lilypond, 12:51
  • Issue 1148 in lilypond: makelsr should look for local convert-ly, lilypond, 12:47
  • Re: Issue 1146 in lilypond: Time signature problem in example for large projects, Dmytro O. Redchuk, 10:16
  • Re: Issue 1146 in lilypond: Time signature problem in example for large projects, Xavier Scheuer, 10:11
  • Re: Issue 1146 in lilypond: Time signature problem in example for large projects, lilypond, 09:39
  • Issue 1147 in lilypond: Typo in documentation link for 2.13, lilypond, 09:35
  • Re: Issue 1146 in lilypond: Time signature problem in example for large projects, lilypond, 09:31
  • Re: buggy image in documentation?, Ralph Palmer, 09:27
  • Re: Issue 1146 in lilypond: Time signature problem in example for large projects, lilypond, 09:26
  • Issue 1146 in lilypond: Time signature problem in example for large projects, lilypond, 09:22
  • Re: q notation for repeated chords should also copy \harmonic...?, James Lowe, 06:30
  • Issue 1145 in lilypond: Enhancement: promote 'use-breve-rest from internal to user-settable, lilypond, 05:03
  • Re: Issue 1014 in lilypond: Full/multi measure rests should be semibreve (for any but 4/2), lilypond, 04:46
  • Issue 1144 in lilypond: [PATCH] 100+ warnings (issue1724041), lilypond, 04:41
  • Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, lilypond, 04:38
  • Issue 1143 in lilypond: [PATCH]New patch for waveforms, lilypond, 04:26
  • Re: q notation for repeated chords should also copy \harmonic...?, David Kastrup, 00:51
• June 22, 2010
  • Re: q notation for repeated chords should also copy \harmonic...?, Arno Waschk, 18:44
  • Re: q notation for repeated chords should also copy \harmonic...?, Carl Sorensen, 18:13
  • Re: Issue 1142 in lilypond: \pageBreak + system-count + lyrics : programming error: bounds of this piece aren't breakable., lilypond, 17:28
  • Re: q notation for repeated chords should also copy \harmonic...?, Neil Puttock, 17:28
  • Re: Issue 1141 in lilypond: \pageBreak "disables" system-count, lilypond, 17:25
  • Re: Issue 1062 in lilypond: Pure-height of a system only takes staves into account, but not other objects, lilypond, 17:22
  • Re: Issue 1139 in lilypond: 'inter-loose-line-spacing #'stretchability leads to collision under some conditions, lilypond, 17:16
  • RE: q notation for repeated chords should also copy \harmonic...?, James Lowe, 17:00
  • q notation for repeated chords should also copy \harmonic...?, Arno Waschk, 14:18
  • buggy image in documentation?, Marek Klein, 11:12
  • Re: Issue 1116 in lilypond: Title not centered, lilypond, 08:31
  • Re: Issue 1142 in lilypond: \pageBreak + system-count + lyrics : programming error: bounds of this piece aren't breakable., lilypond, 06:54
  • Re: Issue 1141 in lilypond: \pageBreak "disables" system-count, lilypond, 06:50
  • Re: Issue 1142 in lilypond: \pageBreak + system-count + lyrics : programming error: bounds of this piece aren't breakable., lilypond, 06:46
  • Re: 2.13.16 crashes while processing old good file (2.8.8 and 2.12.3 do not), Dmytro O. Redchuk, 06:42
  • Issue 1142 in lilypond: \pageBreak + system-count + lyrics : programming error: bounds of this piece aren't breakable., lilypond, 06:42
  • Re: 2.13.16 crashes while processing old good file (2.8.8 and 2.12.3 do not), Dmytro O. Redchuk, 06:14
  • Issue 1141 in lilypond: \pageBreak "disables" system-count, lilypond, 06:13
  • Re: collision bug?, Alexander Kobel, 04:30
  • Re: Issue 1121 in lilypond: [PATCH] (DOC) Clarify vertical spacing with an example, lilypond, 04:01
  • Re: Issue 1138 in lilypond: (minor) regression: Adding a Bar_engraver to the Lyrics context DOES NOT make sure that lyrics do not collide with barlines, Dmytro O. Redchuk, 02:19
  • Re: Issue 1116 in lilypond: Title not centered, lilypond, 01:41
  • Re: Issue 1116 in lilypond: Title not centered, lilypond, 01:31
  • Re: Issue 1121 in lilypond: [PATCH] (DOC) Clarify vertical spacing with an example, lilypond, 01:27
  • Re: Issue 1138 in lilypond: (minor) regression: Adding a Bar_engraver to the Lyrics context DOES NOT make sure that lyrics do not collide with barlines, lilypond, 01:23
  • Re: collision bug?, James Bailey, 01:20
  • Re: collision bug?, James Bailey, 01:20
• June 21, 2010
  • collision bug?, Kieren MacMillan, 15:55
  • Re: Issue 1140 in lilypond: StringNumber documentation, lilypond, 15:04
  • Re: RemoveEmptyStaffContext erases previous setting, Reinhold Kainhofer, 14:32
  • Re: Issue 1138 in lilypond: (minor) regression: Adding a Bar_engraver to the Lyrics context DOES NOT make sure that lyrics do not collide with barlines, lilypond, 14:18
  • Re: Issue 1140 in lilypond: StringNumber documentation, lilypond, 13:46
  • Re: error with StringNumber #'stencil = ##f, Phil Holmes, 11:40
  • Issue 1140 in lilypond: StringNumber documentation, lilypond, 11:40
  • Re: 2.13.16 crashes while processing old good file (2.8.8 and 2.12.3 do not), Dmytro O. Redchuk, 11:06
  • Re: 2.13.16 crashes while processing old good file (2.8.8 and 2.12.3 do not), Dmytro O. Redchuk, 10:44
  • Re: Pedal markings at the end of a piece of music, Phil Holmes, 10:36
  • Re: 2.13.16 crashes while processing old good file (2.8.8 and 2.12.3 do not), Phil Holmes, 10:29
  • account test, Urs Liska, 10:26
  • Re: RemoveEmptyStaffContext erases previous setting, Phil Holmes, 10:10
  • Re: Bug? 'inter-loose-line-spacing #'stretchability leads to collision, Dmytro O. Redchuk, 07:28
  • Issue 1139 in lilypond: 'inter-loose-line-spacing #'stretchability leads to collision under some conditions, lilypond, 07:28
  • Bug? 'inter-loose-line-spacing #'stretchability leads to collision, Dmytro O. Redchuk, 06:52
  • Re: Issue 1116 in lilypond: Title not centered, lilypond, 04:48
  • Issue 1138 in lilypond: (minor) regression: Adding a Bar_engraver to the Lyrics context DOES NOT make sure that lyrics do not collide with barlines, lilypond, 03:38
  • Issue 1137 in lilypond: \bassFigureExtendersOn regression, lilypond, 03:29
  • Re: Issue 1130 in lilypond: Stave spacing not consistent, lilypond, 03:01
  • Re: Issue 1120 in lilypond: Melismata disturb note head distances, lilypond, 02:57
  • Re: Issue 1088 in lilypond: Accidentals for single notes may collide with augmentation dots, lilypond, 02:53
  • Re: Issue 886 in lilypond: ChordNames horizontal extent may affect note spacing, lilypond, 02:49
  • Re: Issue 884 in lilypond: pageBreak resets page-count property, lilypond, 02:45
  • Re: Issue 819 in lilypond: TabVoice confused with ChordNames spacing when using an override., lilypond, 02:38
  • Re: Issue 801 in lilypond: Accidentals in a chord may collide with augmentation dots, lilypond, 02:34
  • Re: Issue 617 in lilypond: X-offset works in a specific way for RehearsalMarks, lilypond, 02:30
  • Re: Multiline \header fields issue (baseline-skip?), Dmytro O. Redchuk, 02:15
  • Issue 1136 in lilypond: Multiline \header fields: wrong baselineskip between and/or inside header fields, lilypond, 02:15
• June 20, 2010
  • Re: Issue 886 in lilypond: ChordNames horizontal extent may affect note spacing, Graham Percival, 17:35
  • Re: Issue 819 in lilypond: TabVoice confused with ChordNames spacing when using an override., lilypond, 17:30
  • Re: Issue 886 in lilypond: ChordNames horizontal extent may affect note spacing, lilypond, 17:28
  • Re: Issue 819 in lilypond: TabVoice confused with ChordNames spacing when using an override., lilypond, 17:20
  • Re: Issue 886 in lilypond: ChordNames horizontal extent may affect note spacing, lilypond, 17:16
  • Re: RemoveEmptyStaffContext erases previous setting, Reinhold Kainhofer, 16:56
  • Re: RemoveEmptyStaffContext erases previous setting, Phil Holmes, 16:53
  • Re: Issue 819 in lilypond: TabVoice confused with ChordNames spacing when using an override., lilypond, 16:37
  • Re: Issue 886 in lilypond: ChordNames horizontal extent may affect note spacing, lilypond, 16:29
  • Re: Issue 1112 in lilypond: before-title-spacing causes underestimation of height: music does not fit on page, lilypond, 16:25
  • Re: Issue 1123 in lilypond: 16th and shorter notes (not beamed) have ugly defects, lilypond, 16:06
  • Re: RemoveEmptyStaffContext erases previous setting, Xavier Scheuer, 14:30
  • Issue 1135 in lilypond: music functions should use funindex instead of findex, lilypond, 14:20
  • Re: Doc -- \shiftDurations is undocumented., Graham Percival, 14:20
  • Re: RemoveEmptyStaffContext erases previous setting, Reinhold Kainhofer, 14:01
  • Re: Enhancement request, Phil Holmes, 13:22
  • Issue 1134 in lilypond: Notes in different voices do not treat accidentals properly, lilypond, 13:22
  • Issue 1133 in lilypond: Linebreaking calculation problem, lilypond, 13:02
  • Re: Issue 1130 in lilypond: Stave spacing not consistent, lilypond, 12:58
  • Re: Line breaks and text positioning, Phil Holmes, 12:55
  • Re: Issue 1062 in lilypond: Pure-height of a system only takes staves into account, but not other objects, lilypond, 12:54
  • Re: Issue 1112 in lilypond: before-title-spacing causes underestimation of height: music does not fit on page, lilypond, 12:50
  • Re: Issue 1123 in lilypond: 16th and shorter notes (not beamed) have ugly defects, lilypond, 12:46
  • Re: 2.13.24-1 install problem, Phil Holmes, 12:45
  • Re: Vertical spacing regression !?, Joe Neeman, 12:41
  • Re: RhythmicStaff Multimeasure Rests, Phil Holmes, 12:40
  • Re: RhythmicStaff Multimeasure Rests, Phil Holmes, 12:31
  • Re: 2.13.24-1 install problem, Graham Percival, 12:28
  • Re: 2.13.24-1 install problem, Phil Holmes, 12:20
  • Issue 1132 in lilypond: Header oddity, lilypond, 12:13
  • Re: Wierd behaviour of \header in \bookpart in \version 2.12.2, Phil Holmes, 12:13
  • Re: Issue 1022 in lilypond: \chordmode reglects point-and-click, lilypond, 12:03
  • Re: Spacing bug with above lyrics, Phil Holmes, 12:01
  • Issue 1131 in lilypond: Spacing bug with above lyrics, lilypond, 11:59
  • Re: Documented but unimplemented feature for beam subdivisions?, Graham Percival, 11:47
  • Re: 2.13.24-1 install problem, Xavier Scheuer, 11:45
  • Re: Documented but unimplemented feature for beam subdivisions?, Phil Holmes, 11:39
  • 2.13.24-1 install problem, Phil Holmes, 11:33
  • Re: is \new Score really needed in the docs?, Phil Holmes, 11:22
  • Re: Vertical spacing regression !?, James Bailey, 10:46
  • Re: Doc -- \shiftDurations is undocumented., Graham Percival, 10:45
  • Re: RemoveEmptyStaffContext erases previous setting, Graham Percival, 10:43
  • Re: chordmode neglects point-and-click, Phil Holmes, 10:40
  • Re: Doc -- \shiftDurations is undocumented., Phil Holmes, 10:34
  • Re: \fermataMarkup positioned higher then \fermata... in some specific cases, Phil Holmes, 10:27
  • Vertical spacing regression !?, Arno Waschk, 10:19
  • Re: RemoveEmptyStaffContext erases previous setting, Phil Holmes, 10:18
  • Re: Issue 1129 in lilypond: Font styles return to default when fontsize changed, Phil Holmes, 09:45
  • Re: Issue 1130 in lilypond: Stave spacing not consistent, lilypond, 09:43
  • Re: Wierd behaviour of \header in \bookpart in \version 2.12.2, Graham Percival, 08:59
  • Re: Issue 1116 in lilypond: Title not centered, lilypond, 08:57
  • Re: Pango font tree not handled at non-default score size, Graham Percival, 08:56
  • Re: Issue 1129 in lilypond: Font styles return to default when font size changed, lilypond, 08:53
  • Re: Issue 1130 in lilypond: Stave spacing not consistent, lilypond, 08:49
  • Re: secundary score header causes shorter distance between scores, Phil Holmes, 08:28
  • Issue 1130 in lilypond: Stave spacing not consistent, lilypond, 08:28
  • Re: Pango font tree not handled at non-default score size, Phil Holmes, 08:06
  • Issue 1129 in lilypond: Font styles return to default when font size changed, lilypond, 08:02
  • Re: Sustain pedal at end of piece, Phil Holmes, 07:48
  • Issue 1128 in lilypond: Text pedal mark not closed at music end, lilypond, 07:46
  • Re: Pango font tree not handled at non-default score size, Carl Sorensen, 07:13
  • Re: Pango font tree not handled at non-default score size, Phil Holmes, 07:05
  • Re: Wierd behaviour of \header in \bookpart in \version 2.12.2, Phil Holmes, 06:58
• June 19, 2010
  • Re: Issue 1124 in lilypond: implement \eyeglasses using a 'path expression, lilypond, 23:16
  • Re: Issue 1124 in lilypond: implement \eyeglasses using a 'path expression, lilypond, 23:11
  • Re: Issue 1125 in lilypond: implement a \path markup command, lilypond, 23:07
  • Re: Multiline \header fields issue (baseline-skip?), Xavier Scheuer, 14:46
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 14:02
  • Re: Issue 1083 in lilypond: subdivideBeams fails at the beginning of a pattern, lilypond, 12:34
  • Re: Issue 1083 in lilypond: subdivideBeams fails at the beginning of a pattern, lilypond, 12:30
  • Re: Issue 1083 in lilypond: subdivideBeams fails at the beginning of a pattern, lilypond, 12:26
  • Re: Issue 1121 in lilypond: [PATCH] (DOC) Clarify vertical spacing with an example, lilypond, 10:08
  • Issue 1127 in lilypond: Piano staff centred dynamics, lilypond, 10:04
  • Re: Tie positioning in chords with largeintervals [engraving-nitpick?], Phil Holmes, 09:51
  • Issue 1126 in lilypond: Tie positioning not as expected, lilypond, 09:49
  • Re: Lilly Pond not installing, James Bailey, 09:49
  • Lilly Pond not installing, Mike Kehl, 08:30
  • Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly, lilypond, 04:48
• June 18, 2010
  • Re: Issue 1125 in lilypond: implement a \path markup command, lilypond, 23:07
  • Re: Issue 1124 in lilypond: implement \eyeglasses using a 'path expression, lilypond, 23:03
  • Issue 1125 in lilypond: implement a \path markup command, lilypond, 22:59
  • Issue 1124 in lilypond: implement \eyeglasses using a 'path expression, lilypond, 22:48
  • Re: Issue 1092 in lilypond: Overriding head-direction for LaissezVibrerTie or LaissezVibrerTieColumn to RIGHT causes segfault, lilypond, 15:31
  • Re: Issue 1123 in lilypond: 16th and shorter notes (not beamed) have ugly defects, lilypond, 15:27
  • Re: Issue 1123 in lilypond: 16th and shorter notes (not beamed) have ugly defects, lilypond, 15:23
  • Re: Issue 1120 in lilypond: Melismata disturb note head distances, lilypond, 15:20
  • Re: Issue 1123 in lilypond: 16th and shorter notes (not beamed) have ugly defects, lilypond, 14:20
  • Re: Issue 1123 in lilypond: 16th and shorter notes (not beamed) have ugly defects, lilypond, 13:15
  • Re: Issue 1123 in lilypond: 16th and shorter notes (not beamed) have ugly defects, lilypond, 13:07
  • Issue 1123 in lilypond: 16th and shorter notes (not beamed) have ugly defects, lilypond, 12:53
  • Re: (2.13.x) bottom-system-spacing, Alexander Kobel, 11:32
  • Re: (2.13.x) bottom-system-spacing, Graham Percival, 11:02
  • Re: (2.13.x) bottom-system-spacing, Alexander Kobel, 10:58
  • Re: (2.13.x) bottom-system-spacing, Joe Neeman, 10:02
  • Re: (2.13.x) bottom-system-spacing, Alexander Kobel, 09:48
  • Re: Issue 884 in lilypond: pageBreak resets page-count property, lilypond, 09:29
  • Re: (2.13.x) bottom-system-spacing, Joe Neeman, 08:31
  • Re: Issue 884 in lilypond: pageBreak resets page-count property, lilypond, 07:18
  • (2.13.x) bottom-system-spacing, Alexander Kobel, 07:08
  • Re: show-break-places, a fantasy, Dmytro O. Redchuk, 03:40
  • Issue 1122 in lilypond: Enhancement: log file (stderr) to reflect measures distribution by systems and pages, lilypond, 03:39
• June 17, 2010
  • Re: Issue 884 in lilypond: pageBreak resets page-count property, lilypond, 18:05
  • Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly, lilypond, 16:47
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 16:24
  • Re: Issue 908 in lilypond: ImageMagick `compare' commands need some investigating, lilypond, 16:13
  • Re: Issue 908 in lilypond: ImageMagick `compare' commands need some investigating, lilypond, 16:09
  • Re: Issue 1120 in lilypond: Melismata disturb note head distances, lilypond, 15:52
  • Re: Issue 884 in lilypond: pageBreak resets page-count property, lilypond, 13:44
  • Re: Issue 908 in lilypond: ImageMagick `compare' commands need some investigating, lilypond, 12:59
  • Re: Issue 884 in lilypond: pageBreak resets page-count property, lilypond, 06:55
  • show-break-places, a fantasy, 胡海鹏 - Hu Haipeng, 06:54
  • Re: Issue 878 in lilypond: Bowing indications need higher priority than fingerings, lilypond, 03:48
  • Re: Issue 1088 in lilypond: Accidentals for single notes may collide with augmentation dots, lilypond, 03:39
  • Re: Issue 801 in lilypond: Accidentals in a chord may collide with augmentation dots, lilypond, 03:35
  • Issue 1121 in lilypond: [PATCH] (DOC) Clarify vertical spacing with an example, lilypond, 02:37
  • Re: Issue 884 in lilypond: pageBreak resets page-count property, lilypond, 02:09
• June 16, 2010
  • Re: Issue 869 in lilypond: input/regression/ renaming to regression/, lilypond, 18:40
  • Re: Issue 878 in lilypond: Bowing indications need higher priority than fingerings, lilypond, 18:25
  • Re: Issue 884 in lilypond: pageBreak resets page-count property, lilypond, 13:43
  • Re: Issue 884 in lilypond: pageBreak resets page-count property, lilypond, 13:15
  • Re: Issue 884 in lilypond: pageBreak resets page-count property, lilypond, 12:33
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 10:50
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 10:33
  • Re: Issue 884 in lilypond: pageBreak resets page-count property, lilypond, 10:27
  • Re: Issue 884 in lilypond: pageBreak resets page-count property, lilypond, 10:20
  • Re: Issue 884 in lilypond: pageBreak resets page-count property, lilypond, 10:11
  • Re: Issue 884 in lilypond: pageBreak resets page-count property, lilypond, 10:06
  • Re: Issue 884 in lilypond: pageBreak resets page-count property, lilypond, 10:02
  • Re: Issue 884 in lilypond: pageBreak resets page-count property, lilypond, 09:58
  • Re: Issue 809 in lilypond: Support for older MS systems is broken, lilypond, 09:55
  • Re: Regression?: Melismata disturb note head distances in 2.13.x, Dmytro O. Redchuk, 09:34
  • Issue 1120 in lilypond: Melismata disturb note head distances, lilypond, 09:33
  • Re: Regression?: Melismata disturb note head distances in 2.13.x, Alexander Kobel, 09:18
  • Re: Issue 809 in lilypond: Support for older MS systems is broken, lilypond, 09:16
  • Re: Issue 1026 in lilypond: Documentation: adapting Lyrics when using \repeatTie, lilypond, 09:11
  • Re: Issue 884 in lilypond: pageBreak resets page-count property, lilypond, 08:55
  • Re: Changing conducting signs, Carl Sorensen, 08:55
  • Regression?: Melismata disturb note head distances in 2.13.x, Alexander Kobel, 05:31
  • Re: Issue 1082 in lilypond: Completion_heads_engraver misbehaves in multi-staff case, lilypond, 04:05
  • Re: Issue 1029 in lilypond: \thumb should behave like other fingerings, lilypond, 04:01
  • Re: Issue 1018 in lilypond: colors in web->examples would be nice, lilypond, 03:57
  • Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication, lilypond, 03:53
• June 15, 2010
  • Re: Issue 917 in lilypond: Regression: Full-bar rests take more space at the beginning of a line, lilypond, 11:15
  • Re: Issue 917 in lilypond: Regression: Full-bar rests take more space at the beginning of a line, lilypond, 10:42
  • Re: Issue 617 in lilypond: X-offset works in a specific way for RehearsalMarks, lilypond, 10:31
  • Re: Issue 617 in lilypond: X-offset works in a specific way for RehearsalMarks, lilypond, 06:33
• June 14, 2010
  • Re: beatLength / beaming in 4/4, Carl Sorensen, 20:28
  • Re: beatLength / beaming in 4/4, Xavier Scheuer, 20:00
  • Re: beatLength / beaming in 4/4, Carl Sorensen, 19:17
  • Re: beatLength / beaming in 4/4, Xavier Scheuer, 19:08
  • Re: Issue 1116 in lilypond: Title not centered, Alexander Kobel, 16:55
  • Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, lilypond, 15:38
  • Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly, lilypond, 15:22
  • Re: Issue 1112 in lilypond: before-title-spacing causes underestimation of height: music does not fit on page, lilypond, 15:18
  • Re: Issue 1112 in lilypond: before-title-spacing causes underestimation of height: music does not fit on page, lilypond, 15:05
  • Re: Issue 1112 in lilypond: before-title-spacing causes underestimation of height: music does not fit on page, lilypond, 15:01
  • Re: \quoteDuring at the beginning, Neil Puttock, 14:41
  • Re: Issue 382 in lilypond: misaligned nested \fill-lines, lilypond, 14:31
  • Re: Issue 1112 in lilypond: before-title-spacing causes underestimation of height: music does not fit on page, lilypond, 14:12
  • Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly, lilypond, 13:45
  • Re: Issue 1112 in lilypond: before-title-spacing causes underestimation of height: music does not fit on page, lilypond, 13:42
  • Issue 1119 in lilypond: [PATCH] fix ly:parser-parse-file in an ly file (issue1345041), lilypond, 08:03
  • Issue 1118 in lilypond: [PATCH] Experimental support for woff fonts in svg, lilypond, 07:57
  • Issue 1117 in lilypond: PATCH Woodwind diagrams (issue1425041), lilypond, 07:55
  • Re: \quoteDuring at the beginning, David Kastrup, 06:48
  • Re: \quoteDuring at the beginning, Reinhold Kainhofer, 06:38
  • Re: Inconsistent line height with Cambodian Unicode, Dmytro O. Redchuk, 06:31
  • Re: \quoteDuring at the beginning, David Kastrup, 06:29
  • Re: why is it taking so long?!?! (was: title not centered), Valentin Villenave, 06:00
  • Re: \quoteDuring at the beginning, Reinhold Kainhofer, 05:52
  • \quoteDuring at the beginning, Christian Hitz, 05:17
  • notation software, Shuta Shimmyo, 03:20
• June 13, 2010
  • Re: Issue 1116 in lilypond: Title not centered, lilypond, 17:58
  • Issue 1116 in lilypond: Title not centered, lilypond, 17:44
  • Re: Issue 878 in lilypond: Bowing indications need higher priority than fingerings, lilypond, 16:59
  • why is it taking so long?!?! (was: title not centered), Graham Percival, 13:53
  • Re: Issue 617 in lilypond: X-offset works in a specific way for RehearsalMarks, lilypond, 12:12
  • Re: Issue 878 in lilypond: Bowing indications need higher priority than fingerings, lilypond, 09:49
  • Re: Issue 878 in lilypond: Bowing indications need higher priority than fingerings, lilypond, 09:45
  • Re: Issue 1115 in lilypond: makelsr.py strips blank lines out of files; different behavior with full and local updates, lilypond, 09:07
  • Re: Issue 1115 in lilypond: makelsr.py strips blank lines out of files, lilypond, 08:59
  • Inconsistent line height with Cambodian Unicode, Didi Kanjahn, 06:09
  • Re: Issue 1115 in lilypond: makelsr.py strips blank lines out of files, lilypond, 02:28
  • Re: Issue 1115 in lilypond: makelsr.py strips blank lines out of files, lilypond, 01:34
  • Re: Issue 1115 in lilypond: makelsr.py strips blank lines out of files, lilypond, 01:17
  • Re: Issue 1115 in lilypond: makelsr.py strips blank lines out of files, lilypond, 00:58
  • Re: Issue 1115 in lilypond: makelsr.py strips blank lines out of files, lilypond, 00:41
• June 12, 2010
  • Re: Issue 1115 in lilypond: makelsr.py strips blank lines out of files, lilypond, 21:57
  • Issue 1115 in lilypond: makelsr.py strips blank lines out of files, lilypond, 21:53
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 12:50
  • Re: RehearsalMark and Barline placement at the beginning of a line, Neil Puttock, 12:13
• June 11, 2010
  • Re: title not centered, James Bailey, 18:45
  • Re: Issue 1029 in lilypond: \thumb should behave like other fingerings, lilypond, 17:49
  • Re: title not centered, Xavier Scheuer, 17:41
  • Re: title not centered, Xavier Scheuer, 17:14
  • title not centered, James Bailey, 16:47
  • Re: Issue 617 in lilypond: X-offset works in a specific way for RehearsalMarks, lilypond, 16:46
  • Re: Issue 897 in lilypond: key signatures should be inherited by all Voices (no matter their accidental style), lilypond, 16:13
  • Re: Issue 878 in lilypond: Bowing indications need higher priority than fingerings, lilypond, 16:09
  • Re: Issue 897 in lilypond: key signatures should be inherited by all Voices (no matter their accidental style), lilypond, 15:50
  • Re: Issue 617 in lilypond: X-offset works in a specific way for RehearsalMarks, lilypond, 12:07
  • Re: Please implement merge-rests-on-positioning, Graham Percival, 11:25
  • Re: Issue 617 in lilypond: X-offset works in a specific way for RehearsalMarks, lilypond, 11:23
  • Re: \cueDuring with 2 quoted voices, Xavier Scheuer, 10:37
  • Please implement merge-rests-on-positioning, Xavier Scheuer, 10:27
  • Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication, lilypond, 10:01
  • Re: Updated CG 7 Issues, draft 3, Carl Sorensen, 09:43
  • Re: RehearsalMark and Barline placement at the beginning of a line, Xavier Scheuer, 09:39
  • Re: Issue 617 in lilypond: X-offset works in a specific way for RehearsalMarks, lilypond, 09:39
  • Re: Issue 1109 in lilypond: makelsr.py should strip right-hand whitespace, lilypond, 09:25
  • Re: Issue 617 in lilypond: X-offset works in a specific way for RehearsalMarks, lilypond, 09:15
  • Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication, lilypond, 09:06
  • Re: Issue 1108 in lilypond: [PATCH]Add independent control of thickness and offset for underline markup (issue1347041), lilypond, 08:44
  • Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication, lilypond, 08:25
  • Re: Issue 1109 in lilypond: makelsr.py should strip right-hand whitespace, lilypond, 08:20
  • Re: Issue 617 in lilypond: X-offset works in a specific way for RehearsalMarks, lilypond, 08:15
  • Updated CG 7 Issues, draft 3, Graham Percival, 08:12
  • Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication, lilypond, 08:03
  • Re: Issue 1109 in lilypond: makelsr.py should strip right-hand whitespace, lilypond, 05:35
  • Re: Issue 617 in lilypond: X-offset works in a specific way for RehearsalMarks, lilypond, 03:57
• June 10, 2010
  • Re: Tie positioning in chords with large intervals [engraving-nitpick?], Alexander Kobel, 19:21
  • Re: Issue 617 in lilypond: X-offset works in a specific way for RehearsalMarks, lilypond, 17:20
  • Re: Issue 617 in lilypond: X-offset works in a specific way for RehearsalMarks, lilypond, 17:05
  • Re: Issue 382 in lilypond: misaligned nested \fill-lines, lilypond, 16:52
  • Re: Issue 915 in lilypond: Multi-measure rests dependent on prefatory matter in other staves, lilypond, 16:48
  • Re: Issue 1029 in lilypond: \thumb should behave like other fingerings, lilypond, 16:10
  • Re: Issue 617 in lilypond: X-offset works in a specific way for RehearsalMarks, lilypond, 15:53
  • Re: Issue 1073 in lilypond: convert-ly and accented characters, lilypond, 13:28
  • Re: Issue 815 in lilypond: Enhancement: AJAX-powered search auto-completion for the online documentation, lilypond, 13:00
  • Re: Issue 617 in lilypond: X-offset works in a specific way for RehearsalMarks, lilypond, 12:55
  • Re: What's the deal with this "programming error"?, Graham Percival, 12:08
  • Re: Issue 617 in lilypond: X-offset works in a specific way for RehearsalMarks, lilypond, 12:00
  • Re: What's the deal with this "programming error"?, David Kastrup, 11:38
  • Re: What's the deal with this "programming error"?, Graham Percival, 11:30
  • Re: What's the deal with this "programming error"?, David Kastrup, 11:25
  • Re: What's the deal with this "programming error"?, Graham Percival, 10:17
  • Re: What's the deal with this "programming error"?, Valentin Villenave, 09:32
  • Re: What's the deal with this "programming error"?, Graham Percival, 09:23
  • Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication, lilypond, 03:55
  • Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, lilypond, 03:52
  • Re: Issue 1113 in lilypond: score with Ambitus_engraver and voice with spacers only produces "programming error", lilypond, 03:32
  • Re: A later note's stem can be to the left of an earlier note's stem, Dmytro O. Redchuk, 02:55
  • Issue 1114 in lilypond: A later note's stem can be to the left of an earlier note's stem, lilypond, 02:54
  • Re: Issue 1113 in lilypond: score with Ambitus_engraver and voice with spacers only produces "programming error", lilypond, 02:48
  • Re: What's the deal with this "programming error"?, Dmytro O. Redchuk, 02:47
  • Issue 1113 in lilypond: score with Ambitus_engraver and voice with spacers only produces "programming error", lilypond, 02:44
  • Re: Issue 1104 in lilypond: Enhancement: 'offset for \underline markup function needed (and proposed), lilypond, 02:40
  • Re: Issue 1108 in lilypond: [PATCH]Add independent control of thickness and offset for underline markup (issue1347041), lilypond, 02:36
  • Re: Issue 1029 in lilypond: \thumb should behave like other fingerings, lilypond, 02:32
• June 09, 2010
  • Re: BUG? VerticalAxisGroup #'next-staff-spacing and \RemoveEmptyStaffContext, Joe Neeman, 21:36
  • Re: Issue 834 in lilypond: midi2ly broken on Windows systems, Jan Nieuwenhuizen, 15:33
  • Re: What's the deal with this "programming error"?, David Kastrup, 12:30
  • Issue 1112 in lilypond: before-title-spacing causes underestimation of height: music does not fit on page, lilypond, 12:29
  • Re: What's the deal with this "programming error"?, Graham Percival, 12:12
  • Re: What's the deal with this "programming error"?, James Bailey, 11:55
  • Re: Virus in lilypond-2.13.23-1.mingw.exe, James Bailey, 11:50
  • Re: What's the deal with this "programming error"?, David Kastrup, 11:37
  • Re: What's the deal with this "programming error"?, Graham Percival, 11:28
  • Re: What's the deal with this "programming error"?, David Kastrup, 11:19
  • Re: What's the deal with this "programming error"?, Graham Percival, 11:17
  • Re: What's the deal with this "programming error"?, Reinhold Kainhofer, 11:14
  • Re: What's the deal with this "programming error"?, Dmytro O. Redchuk, 11:10
  • Re: What's the deal with this "programming error"?, David Kastrup, 10:53
  • Virus in lilypond-2.13.23-1.mingw.exe, Jose, 10:20
  • Re: Issue 834 in lilypond: midi2ly broken on Windows systems, lilypond, 09:34
  • Re: Issue 678 in lilypond: Enhancement: Add option to make moll chords small, lilypond, 09:30
  • Re: Issue 1090 in lilypond: [PATCH] Doc: NR: Using \partial with \repeat. (issue1136044), lilypond, 09:26
  • Re: Issue 1077 in lilypond: [Patch] generalized markup-command and markup-command-list signatures (969046), lilypond, 09:23
  • Re: Issue 1068 in lilypond: [PATCH] Eliminate PDF deletion in Windows 1027042, lilypond, 09:21
  • (no subject), Bryan Previte, 05:39
• June 08, 2010
  • Re: RehearsalMark and Barline placement at the beginning of a line, Neil Puttock, 16:02
  • Re: RehearsalMark and Barline placement at the beginning of a line, Xavier Scheuer, 12:25
  • Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication, lilypond, 09:30
  • Re: Issue 1095 in lilypond: [PATCH] python LilyLib: error and warning as functions, program_name and _version as variables, lilypond, 08:55
  • Re: Issue 305 in lilypond: positioning of hairpins and dynamics, lilypond, 08:31
• June 07, 2010
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 20:08
  • Re: Issue 1043 in lilypond: beams no longer count towards boundary boxes, lilypond, 19:20
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 18:59
  • Re: Issue 1013 in lilypond: lilypond-book regression test, lilypond, 13:58
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 13:46
  • Re: [2.13.11] Overriding font-name in markups increases font-size [was:] strange problem with markup in \tempo, Neil Puttock, 12:48
  • Re: RehearsalMark and Barline placement at the beginning of a line, Neil Puttock, 12:37
  • Re: Issue 305 in lilypond: positioning of hairpins and dynamics, lilypond, 12:34
  • Re: [2.13.11] Overriding font-name in markups increases font-size [was:] strange problem with markup in \tempo, Phil Holmes, 12:25
  • Re: Pango font tree not handled at non-default score size, Phil Holmes, 12:15
  • Re: Tie positioning in chords with large intervals [engraving-nitpick?], Phil Holmes, 12:10
  • Re: header may be covered unintentionally by music, Phil Holmes, 12:05
  • Re: Textual tempo markers in adjacent bars are stacked, Phil Holmes, 11:57
  • Re: Wierd behaviour of \header in \bookpart in \version 2.12.2, Phil Holmes, 11:51
  • RehearsalMark and Barline placement at the beginning of a line, Xavier Scheuer, 11:17
  • Re: Issue 678 in lilypond: Enhancement: Add option to make moll chords small, Carl Sorensen, 10:33
  • Re: Issue 678 in lilypond: Enhancement: Add option to make moll chords small, David Kastrup, 10:10
  • Re: Issue 1013 in lilypond: lilypond-book regression test, lilypond, 09:54
  • Re: BUG? VerticalAxisGroup #'next-staff-spacing and \RemoveEmptyStaffContext, Joe Neeman, 09:41
  • Re: Issue 678 in lilypond: Enhancement: Add option to make moll chords small, lilypond, 09:29
  • Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, lilypond, 09:25
  • Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, lilypond, 09:18
  • Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, lilypond, 08:52
  • Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, lilypond, 08:04
  • Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, lilypond, 07:56
  • Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, lilypond, 06:47
  • Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, lilypond, 06:43
  • Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, lilypond, 06:26
  • Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, lilypond, 06:20
  • Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, lilypond, 06:09
  • Re: Issue 715 in lilypond: \bookparts omit first page number, even when that page number is not 1, lilypond, 04:03
  • Re: Issue 678 in lilypond: Enhancement: Add option to make moll chords small, lilypond, 03:59
  • Re: Issue 305 in lilypond: positioning of hairpins and dynamics, lilypond, 03:55
• June 06, 2010
  • Re: Issue 1018 in lilypond: colors in web->examples would be nice, lilypond, 13:15
  • Re: Page Spacer gets confused by next-space leading to unusable layout, Neil Puttock, 10:43
  • Re: Page Spacer gets confused by next-space leading to unusable layout, Joe Neeman, 10:11
  • Re: Issue 1043 in lilypond: beams no longer count towards boundary boxes, lilypond, 09:46
  • Re: Strange page breaking issue in 2.13.10, Neil Puttock, 09:33
  • Re: Strange page breaking issue in 2.13.10, Phil Holmes, 09:02
  • Re: Numeric note heads for singers, Phil Holmes, 08:55
  • Re: Issue 1082 in lilypond: Completion_heads_engraver misbehaves in multi-staff case, lilypond, 08:54
  • Re: Issue 1018 in lilypond: colors in web->examples would be nice, lilypond, 07:50
  • Re: Vertical spacing: over-estimation of markups height, Nicolas Sceaux, 05:30
  • Re: Issue 1029 in lilypond: \thumb should behave like other fingerings, Frédéric Bron, 00:55
  • Re: Issue 1029 in lilypond: \thumb should behave like other fingerings, lilypond, 00:54
• June 05, 2010
  • Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, lilypond, 21:13
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 21:03
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 20:45
  • Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly, lilypond, 20:13
  • Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly, lilypond, 19:42
  • Re: Vertical spacing: over-estimation of markups height, Boris Shingarov, 18:59
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 17:30
  • Re: Issue 989 in lilypond: ensure that no information is only in the regtests, lilypond, 15:59
  • Re: Issue 989 in lilypond: ensure that no information is only in the regtests, lilypond, 15:55
  • Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, lilypond, 15:34
  • Re: Issue 1026 in lilypond: Documentation: adapting Lyrics when using \repeatTie, lilypond, 14:20
  • Re: Updated CG 7 Issues, draft 2, Graham Percival, 13:04
  • Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, lilypond, 13:03
  • Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, lilypond, 12:59
  • Re: Updated CG 7 Issues, draft 2, Carl Sorensen, 12:56
  • Re: Issue 1103 in lilypond: Typo in engraver name while defining new contexts causes lilypond to segfault, lilypond, 12:55
  • Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, lilypond, 12:51
  • Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, lilypond, 12:43
  • Re: Updated CG 7 Issues, draft 2, James Bailey, 12:33
  • BUG? VerticalAxisGroup #'next-staff-spacing and \RemoveEmptyStaffContext, Xavier Scheuer, 10:55
  • Re: Vertical spacing: over-estimation of markups height, Nicolas Sceaux, 10:02
  • Re: Updated CG 7 Issues, draft 2, Carl Sorensen, 09:51
  • Re: Vertical spacing: over-estimation of markups height, Xavier Scheuer, 09:43
  • Vertical spacing: over-estimation of markups height, Nicolas Sceaux, 09:38
  • Re: Updated CG 7 Issues, draft 2, Graham Percival, 09:17
  • Re: Updated CG 7 Issues, draft 2, Carl Sorensen, 08:24
  • Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 06:03
  • Updated CG 7 Issues, draft 2, Graham Percival, 05:49
  • Error Message, Richard Lockwood, 02:45
  • Re: Issue 1029 in lilypond: \thumb should behave like other fingerings, Frédéric Bron, 00:18
• June 04, 2010
  • Re: Issue 1029 in lilypond: \thumb should behave like other fingerings, Carl Sorensen, 19:02
  • Re: Issue 1029 in lilypond: \thumb should behave like other fingerings, Xavier Scheuer, 18:04
  • Re: Issue 1029 in lilypond: \thumb should behave like other fingerings, lilypond, 16:42
  • Re: What's the deal with this "programming error"?, David Kastrup, 11:52
  • Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel, lilypond, 11:22
  • Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel, lilypond, 11:18
  • Re: Issue 1043 in lilypond: beams no longer count towards boundary boxes, lilypond, 11:13
  • Re: Updated CG 7 Issues -- new policies for Bug Squad, Graham Percival, 10:54
  • Re: Updated CG 7 Issues -- new policies for Bug Squad, Graham Percival, 10:47
  • Re: Issue 1018 in lilypond: colors in web->examples would be nice, lilypond, 10:33
  • Re: Issue 1026 in lilypond: Documentation: adapting Lyrics when using \repeatTie, lilypond, 08:24
  • Re: Updated CG 7 Issues -- new policies for Bug Squad, Dmytro O. Redchuk, 03:05
  • Re: Updated CG 7 Issues -- new policies for Bug Squad, James Bailey, 01:35
• June 03, 2010
  • Re: Updated CG 7 Issues -- new policies for Bug Squad, Graham Percival, 16:12
  • Re: Updated CG 7 Issues -- new policies for Bug Squad, Carl Sorensen, 16:05
  • Updated CG 7 Issues -- new policies for Bug Squad, Graham Percival, 15:52
  • Re: Issue 1018 in lilypond: colors in web->examples would be nice, lilypond, 13:15
  • [Priorities]: Issue 884 is a regression, Alexander Kobel, 09:33
  • Re: Issue 1018 in lilypond: colors in web->examples would be nice, lilypond, 08:48
  • What's the deal with this "programming error"?, David Kastrup, 08:35
  • Re: Issue 1018 in lilypond: colors in web->examples would be nice, lilypond, 07:57
• June 02, 2010
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 22:04
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 15:43
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 15:08
  • Re: Issue 1098 in lilypond: Unable to print long scores, -Eluze, 13:11
  • Re: [Priorities]: Issue 884 is a regression, Dmytro O. Redchuk, 10:37
  • Re: Issue 884 in lilypond: pageBreak resets page-count property, lilypond, 10:12
  • [Priorities]: Issue 884 is a regression, Alexander Kobel, 09:36
  • Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication, lilypond, 09:33
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 08:53
  • Issue 1109 in lilypond: makelsr.py should strip right-hand whitespace, lilypond, 08:49
  • Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication, lilypond, 08:36
  • Re: [Priorities]: Issue 884 is a regression, Alexander Kobel, 06:58
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 06:49
  • Issue 1108 in lilypond: [PATCH]Add independent control of thickness and offset for underline markup (issue1347041), lilypond, 06:45
  • Re: Issue 245 in lilypond: partcombine multiple tuplet brackets false warning, lilypond, 02:15
  • Re: Issue 1107 in lilypond: Wrong and irrelevant warning "no tuplet to end" when quoting (and tuplet isn't part of the desired cue), lilypond, 02:11
• June 01, 2010
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 19:35
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 19:04
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 18:36
  • Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication, lilypond, 13:54
  • Re: Issue 715 in lilypond: \bookparts omit first page number, even when that page number is not 1, lilypond, 13:50
  • Re: Issue 1107 in lilypond: Wrong and irrelevant warning "no tuplet to end" when quoting (and tuplet isn't part of the desired cue), lilypond, 11:47
  • Re: cueDuring + tuplet warning, Dmytro O. Redchuk, 09:34
  • Issue 1107 in lilypond: Wrong and irrelevant warning "no tuplet to end" when quoting (and tuplet isn't part of the desired cue), lilypond, 09:33
  • Re: Issue 1089 in lilypond: DynamicTextSpanner not printed, lilypond, 02:36

---

[Prev Period]

[Next Period]

---

Mail converted by MHonArc