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: Mon May 31 2010 21:57:09 -0400 Messages in reverse chronological order

[Next Period]

---

• May 31, 2010
  • Re: Issue 678 in lilypond: Enhancement: Add option to make moll chords small, lilypond, 21:57
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 20:54
  • Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication, lilypond, 18:24
  • Re: Issue 1098 in lilypond: Unable to print long scores, lilypond, 13:18
  • Re: Issue 1098 in lilypond: Unable to print long scores, lilypond, 13:14
  • Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication, lilypond, 12:50
  • Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication, lilypond, 12:32
  • Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication, lilypond, 12:28
  • Re: Issue 1017 in lilypond: migrate old essay, lilypond, 11:53
  • Re: Issue 1017 in lilypond: migrate old essay, lilypond, 11:25
  • Re: Issue 1097 in lilypond: better skylines for volta brackets, lilypond, 10:28
  • Re: Issue 678 in lilypond: Enhancement: Add option to make moll chords small, lilypond, 10:12
  • Re: Issue 1097 in lilypond: better skylines for volta brackets, lilypond, 10:03
  • Re: Issue 1095 in lilypond: [PATCH] python LilyLib: error and warning as functions, program_name and _version as variables, lilypond, 09:58
  • Re: Issue 1098 in lilypond: Unable to print long scores, lilypond, 09:54
  • Re: BUG? (+ workaround) \change Staff produces wrong stem lengths (2.13.22), Alexander Kobel, 09:52
  • Re: Issue 487 in lilypond: stems of beamed notes too long before staff change, lilypond, 09:50
  • Re: BUG? (+ workaround) \change Staff produces wrong stem lengths (2.13.22), Neil Puttock, 09:31
  • BUG? (+ workaround) \change Staff produces wrong stem lengths (2.13.22), Alexander Kobel, 09:13
  • Re: Issue 1036 in lilypond: Links to accented anchors, lilypond, 08:20
  • Re: Fwd: Extend "Completion_heads_engraver" to drums?, Dmytro O. Redchuk, 07:59
  • Issue 1106 in lilypond: Enhancement: "Completion_heads_engraver" to deal with drums, lilypond, 07:58
  • Re: Issue 305 in lilypond: positioning of hairpins and dynamics, lilypond, 07:03
• May 30, 2010
  • Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel, lilypond, 20:32
  • Re: Text cresc *without dashed line* and Y-offset, Jay Anderson, 19:41
  • Re: Issue 1103 in lilypond: Typo in engraver name while defining new contexts causes lilypond to segfault, lilypond, 19:06
  • Re: Issue 1103 in lilypond: Typo in engraver name while defining new contexts causes lilypond to segfault, lilypond, 19:02
  • Re: Issue 1103 in lilypond: Typo in engraver name while defining new contexts causes lilypond to segfault, lilypond, 18:16
  • Re: How I can control a name of midi output, file?, Ian Hulin, 18:05
  • Re: [frogs] Naming output files – dig ou t, Xavier Scheuer, 17:27
  • Re: [frogs] Naming output files – dig out, Graham Percival, 17:09
  • Re: Text cresc *without dashed line* and Y-offset, Neil Puttock, 17:03
  • Naming output files – dig out, Xavier Scheuer, 17:00
  • Re: Issue 1103 in lilypond: Typo in engraver name while defining new contexts causes lilypond to segfault, lilypond, 16:36
  • Re: How I can control a name of midi output, file?, Oleksandr Gavenko, 16:06
  • Re: How I can control a name of midi output, file?, Xavier Scheuer, 15:17
  • How I can control a name of midi output, file?, Oleksandr Gavenko, 14:40
  • Re: Issue 1036 in lilypond: Links to accented anchors, lilypond, 14:01
  • Re: Issue 1036 in lilypond: Links to accented anchors, lilypond, 13:44
  • Issue 1105 in lilypond: clean up our css files, lilypond, 12:09
  • Re: Page Spacer gets confused by next-space leading to unusable layout, Boris Shingarov, 05:08
  • Re: Page Spacer gets confused by next-space leading to unusable layout, Joe Neeman, 03:52
  • Re: Issue 1029 in lilypond: \thumb should behave like other fingerings, lilypond, 02:06
  • cueDuring + tuplet warning, Jay Anderson, 00:02
• May 29, 2010
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 20:53
  • Re: Issue 1089 in lilypond: DynamicTextSpanner not printed, Graham Percival, 11:44
  • Re: Issue 1092 in lilypond: Overriding head-direction for LaissezVibrerTie or LaissezVibrerTieColumn to RIGHT causes segfault, lilypond, 11:43
  • Re: Issue 1089 in lilypond: DynamicTextSpanner not printed, Xavier Scheuer, 11:40
• May 28, 2010
  • Re: Issue 1089 in lilypond: DynamicTextSpanner not printed, Reinhold Kainhofer, 18:16
  • Re: Issue 1092 in lilypond: Overriding head-direction for LaissezVibrerTie or LaissezVibrerTieColumn to RIGHT causes segfault, lilypond, 17:22
  • Multiline \header fields issue (baseline-skip?), Xavier Scheuer, 17:22
  • Re: Issue 1103 in lilypond: Typo in engraver name while defining new contexts causes lilypond to segfault, lilypond, 17:02
  • Re: Issue 1103 in lilypond: Typo in engraver name while defining new contexts causes lilypond to segfault, lilypond, 16:44
  • Re: Issue 1100 in lilypond: \line inside \concat should keep its 'word-space, lilypond, 15:56
  • Re: Issue 1092 in lilypond: Overriding head-direction for LaissezVibrerTie or LaissezVibrerTieColumn to RIGHT causes segfault, lilypond, 15:52
  • Re: Issue 1089 in lilypond: DynamicTextSpanner not printed, Carl Sorensen, 14:32
  • Re: Issue 1092 in lilypond: Overriding head-direction for LaissezVibrerTie or LaissezVibrerTieColumn to RIGHT causes segfault, lilypond, 13:04
  • Fwd: Extend "Completion_heads_engraver" to drums?, Xavier Scheuer, 13:01
  • Re: Text cresc *without dashed line* and Y-offset, Xavier Scheuer, 12:49
  • Re: Issue 1092 in lilypond: Overriding head-direction for LaissezVibrerTie or LaissezVibrerTieColumn to RIGHT causes segfault, lilypond, 12:32
  • Re: Issue 1089 in lilypond: DynamicTextSpanner not printed, Xavier Scheuer, 12:31
  • Re: Issue 1104 in lilypond: Enhancement: 'offset for \underline markup function needed (and proposed), lilypond, 12:28
  • Re: Issue 963 in lilypond: check dependency versions for 2.14, lilypond, 08:15
  • Re: Issue 771 in lilypond: Instrument names should be centered accordingly to StartSystem objects in other staves, lilypond, 08:11
  • Re: Issue 805 in lilypond: Irrelevant configure message with autoconf and gettext test, lilypond, 08:07
  • Re: Issue 815 in lilypond: Enhancement: AJAX-powered search auto-completion for the online documentation, lilypond, 08:03
  • Re: Issue 881 in lilypond: Arpeggios may collide with laissezVibrer ties, lilypond, 03:42
  • Re: Issue 1056 in lilypond: Pure-height of stems does not accurately estimate height, lilypond, 03:33
  • Re: Issue 1080 in lilypond: Regression: bar lines in double bar are positioned too close together, lilypond, 03:24
• May 27, 2010
  • Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly, lilypond, 22:42
  • Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly, lilypond, 22:23
  • Re: Issue 1103 in lilypond: Typo in engraver name while defining new contexts causes lilypond to segfault, lilypond, 17:45
  • Re: Issue 1104 in lilypond: Enhancement: "underline" markup function needed (and proposed), lilypond, 11:05
  • Re: Issue 1089 in lilypond: DynamicTextSpanner not printed, lilypond, 10:51
  • Issue 1104 in lilypond: Enhancement: "underline" markup function needed (and proposed), lilypond, 10:47
  • Re: Issue 1089 in lilypond: DynamicTextSpanner not printed, lilypond, 10:39
  • Re: Issue 881 in lilypond: Arpeggios may collide with laissezVibrer ties, lilypond, 10:18
  • Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel, lilypond, 10:01
  • Re: Issue 1013 in lilypond: lilypond-book regression test, lilypond, 09:55
  • Re: Issue 1101 in lilypond: PATCH: accessors for note-column's dot-column, accidentals, lilypond, 09:52
  • Re: Issue 1013 in lilypond: lilypond-book regression test, lilypond, 09:39
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 09:35
  • Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel, lilypond, 09:23
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 09:19
  • Re: Issue 1101 in lilypond: PATCH: accessors for note-column's dot-column, accidentals, lilypond, 09:15
  • Re: Issue 1013 in lilypond: lilypond-book regression test, lilypond, 09:04
  • Re: New Essay:nitpicking, James Lowe, 08:44
  • Issue 1103 in lilypond: Typo in engraver name while defining new contexts causes lilypond to segfault, lilypond, 06:52
  • Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel, lilypond, 06:33
  • Re: Issue 1063 in lilypond: Reverting nested property fails to restore default value if preceded by override in same grob, lilypond, 00:07
• May 26, 2010
  • Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel, lilypond, 23:51
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 21:34
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 20:45
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 20:12
  • Re: Issue 1089 in lilypond: DynamicTextSpanner not printed, lilypond, 19:30
  • Re: Issue 1102 in lilypond: [PATCH] Build: require all glyphs for `font-table.ly', lilypond, 11:58
  • Issue 1100 in lilypond: \line inside \concat should keep its 'word-space, lilypond, 11:06
  • Issue 1101 in lilypond: PATCH: accessors for note-column's dot-column, accidentals, lilypond, 11:06
  • Issue 1102 in lilypond: [PATCH] Build: require all glyphs for `font-table.ly', lilypond, 10:38
  • Re: \concat + \line = unexpected behaviour [?], Kieren MacMillan, 10:19
  • Re: \concat + \line = unexpected behaviour [?], Dmytro O. Redchuk, 10:15
  • Re: \concat + \line = unexpected behaviour [?], Werner LEMBERG, 09:56
  • Re: \concat + \line = unexpected behaviour [?], Kieren MacMillan, 08:29
  • Issue 1099 in lilypond: flat collides with stem in some cases, lilypond, 07:58
  • Re: \concat + \line = unexpected behaviour [?], Werner LEMBERG, 01:51
• May 25, 2010
  • Re: \concat + \line = unexpected behaviour [?], Kieren MacMillan, 23:11
  • Re: \concat + \line = unexpected behaviour [?], Neil Puttock, 23:07
  • Re: Issue 1013 in lilypond: lilypond-book regression test, lilypond, 14:25
  • Re: Issue 1063 in lilypond: Reverting nested property fails to restore default value if preceded by override in same grob, lilypond, 09:22
• May 24, 2010
  • 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, 17:21
  • Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly, lilypond, 17:02
  • \concat + \line = unexpected behaviour [?], Kieren MacMillan, 16:00
  • Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly, lilypond, 15:42
  • Re: [Documentation] Typographical error, Francisco Vila, 15:15
  • [Documentation] Typographical error, Stemby, 13:35
  • Re: Issue 687 in lilypond: Enhancement: inequal MIDI quantization of equal durations (swing, rubato), lilypond, 10:31
  • Re: Issue 1098 in lilypond: Unable to print long scores, lilypond, 07:34
  • Issue 1098 in lilypond: Unable to print long scores, lilypond, 05:54
• May 23, 2010
  • Re: Issue 351 in lilypond: warning "reverse rods" with ambitus, clef_8, and note above staff, lilypond, 08:33
  • Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel, lilypond, 07:07
  • Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly, lilypond, 05:49
  • Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly, lilypond, 02:08
• May 22, 2010
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 15:09
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 10:52
  • Issue 1097 in lilypond: better skylines for volta brackets, lilypond, 10:46
• May 21, 2010
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 12:57
  • Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel, lilypond, 07:05
  • Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel, lilypond, 07:02
  • Re: Issue 834 in lilypond: midi2ly broken on Windows systems, lilypond, 06:35
  • Re: Issue 881 in lilypond: Arpeggios may collide with laissezVibrer ties, lilypond, 03:00
  • Issue 1095 in lilypond: [PATCH] python LilyLib: error and warning as functions, program_name and _version as variables, lilypond, 02:51
  • Re: Collision NoteHead with MultiMeasureRest, Dmytro O. Redchuk, 02:11
  • Issue 1094 in lilypond: MultiMeasureRest in one voice collides with noteheads in another, lilypond, 02:09
• May 20, 2010
  • Re: Page Spacer gets confused by next-space leading to unusable layout, Joe Neeman, 21:12
  • Re: Collision NoteHead with MultiMeasureRest, Chris Snyder, 17:03
  • Re: Collision NoteHead with MultiMeasureRest, Xavier Scheuer, 16:08
  • Collision NoteHead with MultiMeasureRest, Chris Snyder, 14:41
  • Re: Issue 1036 in lilypond: Links to accented anchors, lilypond, 14:39
  • Re: Issue 1093 in lilypond: automatic negative offset for instrument name positining, lilypond, 14:27
  • Re: Enhancement to #771, Graham Percival, 13:59
  • Issue 1093 in lilypond: automatic negative offset for instrument name positining, lilypond, 13:59
  • Enhancement to #771, Francisco Vila, 13:27
  • Re: Issue 771 in lilypond: Instrument names should be centered accordingly to StartSystem objects in other staves, lilypond, 11:37
  • Re: Issue 771 in lilypond: Instrument names should be centered accordingly to StartSystem objects in other staves, lilypond, 04:12
  • Re: Issue 1092 in lilypond: Overriding head-direction for LaissezVibrerTie or LaissezVibrerTieColumn to RIGHT causes segfault, lilypond, 02:12
• May 19, 2010
  • Re: Issue 1090 in lilypond: [PATCH] Doc: NR: Using \partial with \repeat. (issue1136044), lilypond, 19:14
  • Re: Issue 1092 in lilypond: Overriding head-direction for LaissezVibrerTie or LaissezVibrerTieColumn to RIGHT causes segfault, lilypond, 19:10
  • Re: Issue 1092 in lilypond: Overriding head-direction for LaissezVibrerTie or LaissezVibrerTieColumn to RIGHT causes segfault, lilypond, 17:55
  • Re: Issue 1077 in lilypond: [Patch] generalized markup-command and markup-command-list signatures (969046), lilypond, 17:51
  • Re: Issue 771 in lilypond: Instrument names should be centered accordingly to StartSystem objects in other staves, lilypond, 11:22
  • Re: Issue 771 in lilypond: Instrument names should be centered accordingly to StartSystem objects in other staves, lilypond, 10:44
  • Re: Issue 834 in lilypond: midi2ly broken on Windows systems, lilypond, 10:37
  • Re: Issue 834 in lilypond: midi2ly broken on Windows systems, lilypond, 10:04
  • Re: Issue 834 in lilypond: midi2ly broken on Windows systems, lilypond, 10:00
  • Issue 1092 in lilypond: Overriding head-direction for LaissezVibrerTie or LaissezVibrerTieColumn to RIGHT causes segfault, lilypond, 09:56
  • Teacher, olle påhlsson, 01:25
• May 18, 2010
  • Re: Issue 1082 in lilypond: Completion_heads_engraver misbehaves in multi-staff case, lilypond, 08:34
  • Re: Issue 1082 in lilypond: Completion_heads_engraver misbehaves in multi-staff case, lilypond, 06:53
• May 17, 2010
  • Re: Page Spacer gets confused by next-space leading to unusable layout, Boris Shingarov, 23:59
  • Re: repeat marks, 1st and 2nd etc endings, coda sign. how to, Mark Polesky, 22:40
  • repeat marks, 1st and 2nd etc endings, coda sign. how to, james kelly, 21:25
  • Re: Issue 539 in lilypond: accidental missing in alternative, lilypond, 20:41
  • Re: Issue 355 in lilypond: \repeat bar lines get messed up, lilypond, 20:18
  • Re: Issue 1090 in lilypond: [PATCH] Doc: NR: Using \partial with \repeat. (issue1136044), lilypond, 20:08
  • Fwd: Remove kludge in Module Code to support Guile V1.6 (MODULE_GC_KLUDGE conditional compilation), Ian Hulin, 13:44
  • Issue 1091 in lilypond: Dot in \voiceOne collides with stem in \voiceThree in short intervals, lilypond, 03:59
• May 16, 2010
  • Re: 'make doc' fails, Graham Percival, 17:46
  • 'make doc' fails, Arnout Engelen, 17:40
  • Re: Issue 1080 in lilypond: Regression: bar lines in double bar are positioned too close together, lilypond, 16:28
  • Re: Issue 1090 in lilypond: [PATCH] Doc: NR: Using \partial with \repeat. (issue1136044), lilypond, 14:40
  • Issue 1090 in lilypond: [PATCH] Doc: NR: Using \partial with \repeat. (issue1136044), lilypond, 14:36
  • Re: Issue 746 in lilypond: Automatic code indentation improvement (and replacing tabs with spaces), lilypond, 11:52
  • Re: Issue 1080 in lilypond: Regression: bar lines in double bar are positioned too close together, lilypond, 04:27
• May 15, 2010
  • Re: Issue 1088 in lilypond: Accidentals for single notes may collide with augmentation dots, lilypond, 23:48
  • uneven spacing with uniform-stretching, Mark Polesky, 22:27
  • Re: Issue 1077 in lilypond: [Patch] generalized markup-command and markup-command-list signatures (969046), lilypond, 19:32
  • Re: Issue 1056 in lilypond: Pure-height of stems does not accurately estimate height, lilypond, 17:50
  • Re: Issue 1077 in lilypond: [Patch] generalized markup-command and markup-command-list signatures (969046), lilypond, 16:26
  • Re: Issue 1088 in lilypond: Accidentals for single notes may collide with augmentation dots, lilypond, 15:21
  • Re: Issue 1089 in lilypond: DynamicTextSpanner not printed, lilypond, 15:17
  • Re: Issue 1089 in lilypond: DynamicTextSpanner not printed, lilypond, 15:00
  • Re: Text cresc *without dashed line* and Y-offset, Xavier Scheuer, 12:34
  • Re: Text cresc *without dashed line* and Y-offset, Neil Puttock, 12:11
  • Re: Text cresc *without dashed line* and Y-offset, Reinhold Kainhofer, 11:51
  • Re: Text cresc *without dashed line* and Y-offset, Neil Puttock, 08:19
  • Re: DynamicTextSpanner not printed, Patrick McCarty, 03:54
  • Re: DynamicTextSpanner not printed, Xavier Scheuer, 03:40
• May 14, 2010
  • Issue 1089 in lilypond: DynamicTextSpanner not printed, lilypond, 23:01
  • Re: DynamicTextSpanner not printed, Patrick McCarty, 23:01
  • Re: Issue 801 in lilypond: Accidentals in a chord may collide with augmentation dots, lilypond, 22:20
  • Issue 1088 in lilypond: Accidentals for single notes may collide with augmentation dots, lilypond, 22:19
  • Re: collision dotted rest and accidental, Patrick McCarty, 22:18
  • Re: Issue 801 in lilypond: Accidentals in a chord may collide with augmentation dots, lilypond, 22:06
  • Re: collision dotted rest and accidental, Xavier Scheuer, 18:40
  • Re: Text cresc *without dashed line* and Y-offset, Graham Percival, 18:30
  • Re: collision dotted rest and accidental, Graham Percival, 18:23
  • Re: Text cresc *without dashed line* and Y-offset, Xavier Scheuer, 17:57
  • collision dotted rest and accidental, Torsten, 17:25
  • Re: DynamicTextSpanner not printed, Xavier Scheuer, 17:14
  • Re: Issue 815 in lilypond: Enhancement: AJAX-powered search auto-completion for the online documentation, lilypond, 13:22
  • lost bug reports (was: Text cresc *without dashed line* and Y-offset), Graham Percival, 13:14
  • Re: DynamicTextSpanner not printed, Reinhold Kainhofer, 13:08
  • Re: Text cresc *without dashed line* and Y-offset, Reinhold Kainhofer, 13:07
  • Re: DynamicTextSpanner not printed, James Bailey, 12:54
  • DynamicTextSpanner not printed, Xavier Scheuer, 10:32
  • Re: Issue 1075 in lilypond: Regression: flag glyphs have changed shape, lilypond, 02:43
• May 13, 2010
  • Re: Issue 1083 in lilypond: subdivideBeams fails at the beginning of a pattern, lilypond, 08:46
• May 12, 2010
  • Issue 1087 in lilypond: cross-staff unstemmed tremolos are not centered between staves, lilypond, 14:47
  • Re: Issue 1080 in lilypond: Regression: bar lines in double bar are positioned too close together, lilypond, 14:22
  • Re: Issue 1085 in lilypond: [PATCH]Doc: Reorganize music functions material. (issue1031044), lilypond, 11:02
  • Re: Issue 1086 in lilypond: [PATCH] Doc: LM: Reformat ly code. (issue1056041), lilypond, 10:58
  • Re: Issue 1086 in lilypond: [PATCH] Doc: LM: Reformat ly code. (issue1056041), lilypond, 10:54
  • Issue 1086 in lilypond: [PATCH] Doc: LM: Reformat ly code. (issue1056041), lilypond, 05:15
  • Issue 1085 in lilypond: [PATCH]Doc: Reorganize music functions material. (issue1031044), lilypond, 05:09
• May 11, 2010
  • Re: subdivideBeams fails, Patrick McCarty, 17:36
  • Re: Issue 1083 in lilypond: subdivideBeams fails at the beginning of a pattern, lilypond, 17:36
  • Re: subdivideBeams fails, Bernhard Ott, 16:25
  • Re: Issue 1072 in lilypond: PATCH: Doc: Clarify \relative inside \repeat issue., lilypond, 15:26
  • Re: subdivideBeams fails, Neil Puttock, 15:22
  • Re: subdivideBeams fails, Xavier Scheuer, 14:51
  • Re: Issue 1036 in lilypond: Links to accented anchors, lilypond, 14:20
  • Re: Issue 1036 in lilypond: Links to accented anchors, lilypond, 13:56
  • Re: Issue 1036 in lilypond: Links to accented anchors, lilypond, 12:31
• May 10, 2010
  • Re: Issue 943 in lilypond: input/regression/slur-broken-trend.ly broken, lilypond, 15:49
  • Issue 1084 in lilypond: lilypond-book fails on identical snippets, lilypond, 14:44
  • Re: subdivideBeams fails, Patrick McCarty, 13:43
  • Issue 1083 in lilypond: subdivideBeams fails at the beginning of a pattern, lilypond, 13:43
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 12:44
  • Re: Issue 1060 in lilypond: Add Funk-style shape note heads, lilypond, 12:00
  • subdivideBeams fails, Bernhard Ott, 06:12
• May 09, 2010
  • Re: completion disturbed by other staff, Patrick McCarty, 22:43
  • Issue 1082 in lilypond: Completion_heads_engraver misbehaves in multi-staff case, lilypond, 22:40
  • Re: xref to @unnumbered* bug, Patrick McCarty, 22:20
  • Issue 1081 in lilypond: Problem with xrefs to @unnumbered*, lilypond, 22:19
  • Issue 1080 in lilypond: Regression: bar lines in double bar are positioned too close together, lilypond, 21:28
  • Re: Issue 1036 in lilypond: Links to accented anchors, lilypond, 20:06
  • Re: Failure to install (or find) the LILYPOND software with UBUNTU, Francisco Vila, 18:34
  • Re: Failure to install (or find) the LILYPOND software with UBUNTU, Bernard Hurley, 15:48
  • Re: Issue 75 in lilypond: Slurs cannot be nested (including acciaccatura and appoggiatura), lilypond, 11:02
  • Re: Issue 75 in lilypond: Slurs cannot be nested, lilypond, 10:41
  • Re: Issue 963 in lilypond: check dependency versions for 2.14, lilypond, 10:19
  • Issue 1079 in lilypond: upgrade python in GUB, lilypond, 09:56
  • Re: Issue 1072 in lilypond: PATCH: Doc: Clarify \relative inside \repeat issue., lilypond, 09:56
  • Re: Issue 1072 in lilypond: PATCH: Doc: Clarify \relative inside \repeat issue., lilypond, 09:38
  • Re: Issue 1066 in lilypond: postfix \cresc, lilypond, 09:34
  • Re: Issue 989 in lilypond: ensure that no information is only in the regtests, lilypond, 09:33
  • Re: Issue 355 in lilypond: \repeat bar lines get messed up, lilypond, 08:37
  • Re: Issue 1073 in lilypond: convert-ly and accented characters, lilypond, 08:09
  • Re: Issue 963 in lilypond: check dependency versions for 2.14, lilypond, 08:01
  • Re: Failure to install (or find) the LILYPOND software with UBUNTU, Boris Shingarov, 08:00
  • Re: Issue 602 in lilypond: Feature request: better support for Sacred Harp notation, lilypond, 07:57
  • Issue 1078 in lilypond: relative includes should also work in Scheme expressions, lilypond, 07:53
  • Re: Failure to install (or find) the LILYPOND software with UBUNTU, Henning Plumeyer, 07:53
  • Re: Issue 1040 in lilypond: regtest for changing file names, lilypond, 07:47
  • Failure to install (or find) the LILYPOND software with UBUNTU, Oliver Penrose, 07:15
• May 08, 2010
  • Re: Issue 602 in lilypond: Feature request: better support for Sacred Harp notation, lilypond, 19:43
  • Re: Issue 75 in lilypond: Slurs cannot be nested, lilypond, 19:43
  • Re: Issue 355 in lilypond: \repeat bar lines get messed up, lilypond, 19:43
  • Re: Issue 355 in lilypond: \repeat bar lines get messed up, lilypond, 19:24
  • Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly, lilypond, 19:18
  • Re: Issue 989 in lilypond: ensure that no information is only in the regtests, lilypond, 19:15
  • Re: Issue 963 in lilypond: check dependency versions for 2.14, lilypond, 18:07
  • Re: Issue 834 in lilypond: midi2ly broken on Windows systems, lilypond, 18:02
  • Re: Issue 805 in lilypond: Irrelevant configure message with autoconf and gettext test, lilypond, 17:58
  • Re: Issue 602 in lilypond: Feature request: better support for Sacred Harp notation, lilypond, 17:10
  • Re: Issue 602 in lilypond: Feature request: better support for Sacred Harp notation, lilypond, 16:58
  • Re: Issue 602 in lilypond: Feature request: better support for Sacred Harp notation, lilypond, 16:36
  • Re: Issue 943 in lilypond: input/regression/slur-broken-trend.ly broken, lilypond, 16:27
  • Re: Issue 1025 in lilypond: Lyrics with alignAboveContext are not taken into account in Vertical spacing, lilypond, 16:23
  • Re: Issue 1027 in lilypond: LSR: minimum-Y-extent snippets need to be updated, lilypond, 16:19
  • Re: Issue 1064 in lilypond: Feature request: binding-gutter, lilypond, 16:15
  • Re: Issue 1066 in lilypond: postfix \cresc needs to be documented, lilypond, 16:11
  • Re: Issue 1071 in lilypond: [PATCH] Parser docfix for tokenization of music function signatures, lilypond, 16:06
  • Re: Issue 1072 in lilypond: PATCH: Doc: Clarify \relative inside \repeat issue., lilypond, 16:02
  • Re: Issue 1070 in lilypond: [PATCH] Fix #915 (faulty full-bar rest positioning with clef). (issue931041), lilypond, 15:58
  • Re: Issue 1069 in lilypond: [PATCH] Fix #943 (issue956051), lilypond, 15:54
  • Re: Issue 1067 in lilypond: Postfix syntax for repeats, lilypond, 15:50
  • Re: Issue 1036 in lilypond: Links to accented anchors, lilypond, 10:03
• May 07, 2010
  • Issue 1077 in lilypond: [Patch] generalized markup-command and markup-command-list signatures (969046), lilypond, 09:34
• May 06, 2010
  • Re: Issue 1075 in lilypond: Regression: flag glyphs have changed shape, lilypond, 18:12
  • Re: Issue 1075 in lilypond: Regression: flag glyphs have changed shape, lilypond, 16:49
  • Re: Issue 815 in lilypond: Enhancement: AJAX-powered search auto-completion for the online documentation, lilypond, 12:46
  • Re: Issue 1075 in lilypond: Regression: flag glyphs have changed shape, lilypond, 10:56
  • Issue 1076 in lilypond: Connected arpeggios collide with previos chord or note, lilypond, 10:13
  • Issue 1075 in lilypond: Regression: flag glyphs have changed shape, lilypond, 10:12
  • Re: Issue 515 in lilypond: ugly slur (too flat), lilypond, 10:12
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), lilypond, 10:12
  • Re: Issue 963 in lilypond: check dependency versions for 2.14, lilypond, 10:12
  • Re: Issue 1068 in lilypond: [PATCH] Eliminate PDF deletion in Windows 1027042, lilypond, 10:11
  • Issue 1074 in lilypond: -q quiet mode for lilypond, lilypond, 10:11
  • Re: Issue 1056 in lilypond: Pure-height of stems does not accurately estimate height, lilypond, 10:10
  • Re: Issue 1072 in lilypond: PATCH: Doc: Clarify \relative inside \repeat issue., lilypond, 10:10
  • Re: Issue 684 in lilypond: Enhancement: MetronomeMark should support break-align-symbols, lilypond, 10:10
  • Re: Issue 1072 in lilypond: PATCH: Doc: Clarify \relative inside \repeat issue., lilypond, 10:10
  • Re: Issue 943 in lilypond: input/regression/slur-broken-trend.ly broken, lilypond, 10:10
  • Re: Issue 1069 in lilypond: [PATCH] Fix #943 (issue956051), lilypond, 10:10
  • Re: Issue 1066 in lilypond: postfix \cresc, lilypond, 10:10
  • Re: Issue 1062 in lilypond: Pure-height of a system only takes staves into account, but not other objects, lilypond, 10:10
  • Re: Issue 1070 in lilypond: [PATCH] Fix #915 (faulty full-bar rest positioning with clef). (issue931041), lilypond, 10:10
  • Re: Issue 1069 in lilypond: [PATCH] Fix #943 (issue956051), lilypond, 10:10
  • Re: Issue 1065 in lilypond: Lyrics syllable followed by \skip is left-aligned instead of center-aligned, lilypond, 04:43
  • Re: Connected arpeggios may collide with previos chord., Dmytro O. Redchuk, 04:04
  • Re: Issue 370 in lilypond: slur #'positions silently does not place slur at actual position, lilypond, 02:13
  • Re: Issue 356 in lilypond: collision slur/stems+notehead in polyphony, lilypond, 02:09
  • Re: Issue 304 in lilypond: Slurs and phrasing slurs should not collide at endpoints, lilypond, 02:04
  • Re: Issue 971 in lilypond: SVG backend: problem with memory usage and multi-page SVG output, lilypond, 01:43
  • Re: Issue 1028 in lilypond: Test failure when built without a controlling tty, lilypond, 01:37
• May 05, 2010
  • Issue 1073 in lilypond: convert-ly and accented characters, lilypond, 20:36
  • Re: Issue 1071 in lilypond: [PATCH] Parser docfix for tokenization of music function signatures, lilypond, 20:29
  • Re: Issue 1064 in lilypond: Feature request: binding-gutter, lilypond, 20:11
  • Re: Issue 915 in lilypond: Multi-measure rests dependent on prefatory matter in other staves, lilypond, 19:50
  • Issue 1072 in lilypond: PATCH: Doc: Clarify \relative inside \repeat issue., lilypond, 15:40
  • Issue 1071 in lilypond: [PATCH] Parser docfix for tokenization of music function signatures, lilypond, 15:36
  • Issue 1070 in lilypond: [PATCH] Fix #915 (faulty full-bar rest positioning with clef). (issue931041), lilypond, 15:32
  • Issue 1069 in lilypond: [PATCH] Fix #943 (issue956051), lilypond, 15:27
  • Re: Issue 1068 in lilypond: [PATCH] Eliminate PDF deletion in Windows 1027042, lilypond, 15:23
  • Issue 1068 in lilypond: [PATCH] Eliminate PDF deletion in Windows 1027042, lilypond, 15:19
  • Re: Unicode rendering problems, Patrick McCarty, 15:10
  • Re: Font selection problem in Lilypond, Patrick McCarty, 14:59
  • Re: xref to @unnumbered* bug, Graham Percival, 14:51
  • Unicode rendering problems, Didi Kanjahn, 06:42
  • Font selection problem in Lilypond, Didi Kanjahn, 06:03
• May 04, 2010
  • Re: png output with transparent background, Jonathan Wilkes, 14:58
  • Re: png output with transparent background, Bertalan Fodor (LilyPondTool), 07:40
• May 03, 2010
  • Re: Issue 1066 in lilypond: postfix \cresc, lilypond, 16:27
  • Re: png output with transparent background, Jonathan Wilkes, 16:25
  • Re: Issue 1056 in lilypond: Pure-height of stems doesnotaccurately estimate height, Neil Puttock, 10:31
  • Re: Issue 1056 in lilypond: Pure-height of stems doesnotaccurately estimate height, Boris Shingarov, 07:45
  • define-markup-command and define-markup-list-command have limited signatures, David Kastrup, 01:10
• May 02, 2010
  • Re: lilypond-book fails on identical snippets, Han-Wen Nienhuys, 20:52
  • Re: lilypond-book fails on identical snippets, Han-Wen Nienhuys, 20:44
  • Re: lilypond-book fails on identical snippets, Werner LEMBERG, 18:44
  • completion disturbed by other staff, PálBenkő, 17:45
  • Re: lilypond-book fails on identical snippets, Mats Bengtsson, 17:11
  • Re: ictus articulation incorrectly placed, Trevor Daniels, 09:39
  • ictus articulation incorrectly placed, Roman Stawski, 09:05
• May 01, 2010
  • lilypond-book fails on identical snippets, Werner LEMBERG, 04:57

---

[Prev Period]

[Next Period]

---

Mail converted by MHonArc