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 Jun 30 2011 22:34:43 -0400 Messages in reverse chronological order

[Next Period]

---

• June 30, 2011
  • Issue 1729 in lilypond: Set spanner length as a spanner property, lilypond, 22:34
  • Issue 1728 in lilypond: Implements multi-line non-cross staff glissandi, lilypond, 22:28
  • Issue 1727 in lilypond: Adds glissando stems to lilypond, lilypond, 22:21
  • Re: Issue 1716 in lilypond: No convert-ly rule for the fix for issue 1655, lilypond, 21:21
  • Re: Issue 1651 in lilypond: Triplet direction depends on rest length, lilypond, 18:28
  • Re: Issue 1507 in lilypond: weird linebreaks in song output, lilypond, 14:04
  • Issue 1726 in lilypond: python versions might not be updating, lilypond, 13:44
  • Re: Issue 1724 in lilypond: DynamicTextSpanner inside Dynamics context are shifted due to pedal, lilypond, 12:36
  • Re: Issue 1507 in lilypond: weird linebreaks in song output, lilypond, 12:28
  • Re: Issue 1507 in lilypond: weird linebreaks in song output, lilypond, 12:16
  • Re: Issue 1720 in lilypond: Incorrect tuplet bracket direction calculation when tuplets contain rests., lilypond, 11:26
  • Re: Issue 1651 in lilypond: Triplet direction depends on rest length, lilypond, 11:22
  • Re: Issue 1720 in lilypond: Incorrect tuplet bracket direction calculation when tuplets contain rests., lilypond, 11:18
  • Re: Issue 620 in lilypond: It should be possible to specify more specific spanner bounds., lilypond, 11:14
  • Re: Issue 1724 in lilypond: DynamicTextSpanner inside Dynamics context are shifted due to pedal, lilypond, 11:10
  • Issue 1725 in lilypond: DynamicTextSpanner collides with DynamicText, lilypond, 09:40
  • Re: DynamicTextSpanner collides with DynamicText, Dmytro O. Redchuk, 09:39
  • Issue 1724 in lilypond: DynamicTextSpanner inside Dynamics context are shifted due to pedal, lilypond, 09:36
  • Re: DynamicTextSpanner inside Dynamics context are shifted due to pedal, Dmytro O. Redchuk, 09:36
  • Re: Issue 1723 in lilypond: beam drawn over less than its full span, some OS only, lilypond, 09:13
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, Colin Campbell, 09:02
  • Re: Issue 1643 in lilypond: Part Combine problems, lilypond, 05:11
  • Re: Issue 1723 in lilypond: beam drawn over less than its full span, some OS only, lilypond, 04:16
  • Re: Issue 1721 in lilypond: Doc: translated docs should use @rlsrnamed instead of @rlsr, lilypond, 03:33
  • Re: Issue 1718 in lilypond: Slur collides with cross-staff stems, lilypond, 01:38
  • Issue 1723 in lilypond: beam drawn over less than its full span, some OS only, lilypond, 01:31
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, lilypond, 01:20
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, lilypond, 00:33
  • Re: Issue 1693 in lilypond: Attaches bound info to beam for better normalized-endpoint calculations, lilypond, 00:30
  • Re: Issue 1712 in lilypond: Braces redesigned, lilypond, 00:25
  • Issue 1722 in lilypond: Lyrics hyphen's visibility after line break should be controllable, lilypond, 00:12
  • Re: Issue 1128 in lilypond: Text pedal mark not closed at music end, lilypond, 00:05
  • Re: [translations] Doc: @snippets links are broken when translated, Dmytro O. Redchuk, 00:00
  • Issue 1721 in lilypond: Doc: @snippets links are broken when translated, lilypond, 00:00
• June 29, 2011
  • Issue 1720 in lilypond: Incorrect tuplet bracket direction calculation when tuplets contain rests., lilypond, 20:00
  • RE: [translations] Doc: @snippets links are broken when translated, James Lowe, 19:46
  • Re: [translations] Doc: @snippets links are broken when translated, Valentin Villenave, 18:45
  • Re: [translations] Doc: @snippets links are broken when translated, Jean-Charles Malahieude, 13:43
  • Issue 1719 in lilypond: list of places to send release announcements, lilypond, 09:38
  • Re: Issue 1214 in lilypond: Cue notes to music that creates a sub-voice does not work, lilypond, 07:49
  • Re: Issue 1216 in lilypond: DynamicTextSpanners should end like hairpins, lilypond, 07:40
  • DynamicTextSpanner collides with DynamicText, Xavier Scheuer, 07:21
  • DynamicText inside Dynamics context not correctly aligned, Xavier Scheuer, 07:05
  • DynamicTextSpanner inside Dynamics context are shifted due to pedal, Xavier Scheuer, 04:38
  • Re: [translations] Doc: @snippets links are broken when translated, Francisco Vila, 03:23
• June 28, 2011
  • Re: Issue 1694 in lilypond: Modifies Spanner::spanner_length to better handle line-spanners, lilypond, 23:04
  • Re: Issue 1697 in lilypond: Add ties from Completion_note_heads_engraver to a TieColumn, lilypond, 23:00
  • Re: Slurs ignore intermediary cross-staff notes, Colin Campbell, 20:47
  • Issue 1718 in lilypond: Slur collides with cross-staff stems, lilypond, 20:44
  • Re: Build error regarding mf2pt1 with latest texlive (2011) and lilypond 2.14.1, Werner LEMBERG, 17:01
  • Re: Issue 1467 in lilypond: [PATCH] Doc: Rewrite NR 3.2 Titles and headers. (issue3667041), lilypond, 15:51
  • Re: Issue 1014 in lilypond: Full/multi measure rests should be semibreve (for any but 4/2), lilypond, 15:47
  • Re: Issue 1714 in lilypond: Build error regarding mf2pt1 with latest texlive (2011) and lilypond, lilypond, 14:43
  • Re: Backporting for 2.14.2, Carl Sorensen, 14:37
  • Re: Issue 1714 in lilypond: Build error regarding mf2pt1 with latest texlive (2011) and lilypond, lilypond, 14:29
  • Re: Build error regarding mf2pt1 with latest texlive (2011) and lilypond 2.14.1, Marc Payne, 14:22
  • Doc: @snippets links are broken when translated, Valentin Villenave, 13:05
  • Slurs ignore intermediary cross-staff notes, Valentin Villenave, 13:00
  • Re: Issue 1259 in lilypond: DynamicTextSpanner #'style = #'none doesn't work over \break, lilypond, 11:30
  • Re: Issue 1706 in lilypond: Beaming causes lilypond to crash, lilypond, 07:59
  • Re: Issue 1643 in lilypond: Part Combine problems, lilypond, 07:25
  • Re: Issue 1643 in lilypond: Part Combine problems, lilypond, 07:09
  • Re: Issue 1714 in lilypond: Build error regarding mf2pt1 with latest texlive (2011) and lilypond, lilypond, 07:05
  • Re: Build error regarding mf2pt1 with latest texlive (2011) and lilypond 2.14.1, Graham Percival, 07:05
  • Re: Issue 1716 in lilypond: No convert-ly rule for the fix for issue 1655, lilypond, 06:55
  • Re: Issue 1716 in lilypond: No convert-ly rule for the fix for issue 1655, lilypond, 06:34
  • Re: Issue 1716 in lilypond: No convert-ly rule for the fix for issue 1655, lilypond, 05:44
  • Re: Build error regarding mf2pt1 with latest texlive (2011) and lilypond 2.14.1, Werner LEMBERG, 02:14
  • Re: Issue 1709 in lilypond: Add feta-flags to build system, lilypond, 01:17
  • Re: Issue 1714 in lilypond: Build error regarding mf2pt1 with latest texlive (2011) and lilypond, lilypond, 01:12
  • Re: Issue 1717 in lilypond: Possible incompatibility with Ghostscript 9 (was: Full notes and half notes are drawn filled), lilypond, 01:08
  • Re: Issue 1641 in lilypond: noBeam disables beaming of prior notes, lilypond, 01:04
  • Re: Issue 1647 in lilypond: MIDI skips note if the pitch is already sounding in the same channel, lilypond, 01:00
  • Re: Issue 1652 in lilypond: Assertion error when line-count of StaffSymbol set to 0 and one uses a note in the middle of the (non-existant) staff, lilypond, 00:56
  • Re: Issue 1668 in lilypond: staff-staff padding is inserted below the last nonstaff, lilypond, 00:52
  • Re: Issue 1715 in lilypond: Ligature and ambitus cause segfault, lilypond, 00:36
  • Re: Issue 1714 in lilypond: Build error regarding mf2pt1 with latest texlive (2011) and lilypond, lilypond, 00:29
  • Re: Issue 1433 in lilypond: \breakDynamicSpan breaks with \break ("bounds of spanner are invalid"), lilypond, 00:25
• June 27, 2011
  • Re: [informatique] Re: Full notes and half notes are drawn filled, Dmytro O. Redchuk, 23:16
  • Issue 1717 in lilypond: Possible incompatibility with Ghostscript 9 (was: Full notes and half notes are drawn filled), lilypond, 23:14
  • Re: Issue 1673 in lilypond: patch Allows glissandi to span multiple lines., lilypond, 21:25
  • Re: Issue 1673 in lilypond: patch Allows glissandi to span multiple lines., lilypond, 20:39
  • Re: Issue 1715 in lilypond: Ligature and ambitus cause segfault, lilypond, 19:17
  • Re: Issue 1673 in lilypond: patch Allows glissandi to span multiple lines., lilypond, 19:13
  • Re: Issue 1716 in lilypond: No convert-ly rule for the fix for issue1655, Trevor Daniels, 19:00
  • Re: Issue 1716 in lilypond: No convert-ly rule for the fix for issue 1655, lilypond, 18:40
  • Re: Issue 1014 in lilypond: Full/multi measure rests should be semibreve (for any but 4/2), lilypond, 18:35
  • Re: Issue 1716 in lilypond: No convert-ly rule for the fix for issue 1655, lilypond, 18:31
  • Re: Issue 1716 in lilypond: No convert-ly rule for the fix for issue 1655, lilypond, 18:18
  • Re: Issue 1542 in lilypond: [PATCH] Add springs-and-rods callback to DynamicTextSpanner, so minimum-length has an effect (issue4187054), lilypond, 18:07
  • Re: Partcombine: beaming, Reinhold Kainhofer, 18:06
  • Re: Issue 1716 in lilypond: No convert-ly rule for the fix for issue 1655, lilypond, 18:03
  • Re: Issue 1708 in lilypond: Adds ly:engraver-property to engraver-scheme, lilypond, 17:58
  • Re: Partcombine: beaming, Xavier Scheuer, 17:06
  • Re: Issue 1716 in lilypond: No convert-ly rule for the fix for issue 1655, lilypond, 16:51
  • Partcombine: beaming, Jean-Charles Malahieude, 16:48
  • Re: Issue 1666 in lilypond: Docs problem: fretted-string-harmonics-in-tablature snippet, lilypond, 16:46
  • Re: Issue 1655 in lilypond: Handles longa in MultiMeasureRest, lilypond, 16:42
  • FW: how to create baroque ornaments, Carl Sorensen, 16:41
  • Re: Issue 1682 in lilypond: Website version links need updating, lilypond, 16:10
  • Re: Issue 1682 in lilypond: Website version links need updating, lilypond, 15:42
  • Re: Issue 1508 in lilypond: Key signature wrong with cued music, lilypond, 15:38
  • Re: Issue 1666 in lilypond: Docs problem: fretted-string-harmonics-in-tablature snippet, lilypond, 15:34
  • Re: Issue 1689 in lilypond: doc: changing example for overriding positions, lilypond, 15:30
  • Re: Issue 1694 in lilypond: Modifies Spanner::spanner_length to better handle line-spanners, lilypond, 15:26
  • Re: Issue 1714 in lilypond: Build error regarding mf2pt1 with latest texlive (2011) and lilypond, lilypond, 15:22
  • Issue 1716 in lilypond: No convert-ly rule for the fix for issue 1655, lilypond, 15:18
  • Re: [informatique] Re: Full notes and half notes are drawn filled, Graham Percival, 14:45
  • Re: [informatique] Re: Full notes and half notes are drawn filled, Dmytro O. Redchuk, 14:00
  • Re: Issue 1706 in lilypond: Beaming causes lilypond to crash, Carl Sorensen, 13:58
  • Re: Issue 379 in lilypond: ugly slur with key signature and linebreak, lilypond, 13:54
  • Re: [informatique] Re: Full notes and half notes are drawn filled, Dmytro O. Redchuk, 13:36
  • Re: Issue 1697 in lilypond: Add ties from Completion_note_heads_engraver to a TieColumn, lilypond, 13:13
  • Re: Ligatures and ambits don't mix, Laura Conrad, 12:21
  • Re: Ligatures and ambits don't mix, Dmytro O. Redchuk, 12:00
  • Re: Ligatures and ambits don't mix, Phil Holmes, 11:54
  • Issue 1715 in lilypond: Ligature and ambitus cause segfault, lilypond, 11:53
  • Re: Issue 1161 in lilypond: Lyrics is not centered with CENTER affinity if there is another Lyrics with one of UP or DOWN, lilypond, 11:46
  • Re: Issue 1161 in lilypond: Lyrics is not centered with CENTER affinity if there is another Lyrics with one of UP or DOWN, lilypond, 11:18
  • Ligatures and ambits don't mix, Laura Conrad, 10:58
  • Re: Issue 1647 in lilypond: MIDI skips note if the pitch is already sounding in the same channel, lilypond, 10:44
  • Re: Issue 1655 in lilypond: Handles longa in MultiMeasureRest, lilypond, 10:40
  • Re: Issue 1666 in lilypond: Docs problem: fretted-string-harmonics-in-tablature snippet, lilypond, 10:36
  • Re: Issue 1694 in lilypond: Modifies Spanner::spanner_length to better handle line-spanners, lilypond, 10:32
  • Re: Issue 1697 in lilypond: Add ties from Completion_note_heads_engraver to a TieColumn, lilypond, 10:28
  • Re: Issue 1161 in lilypond: Lyrics is not centered with CENTER affinity if there is another Lyrics with one of UP or DOWN, lilypond, 10:05
  • Re: Issue 1161 in lilypond: Lyrics is not centered with CENTER affinity if there is another Lyrics with one of UP or DOWN, lilypond, 10:00
  • Re: Issue 1673 in lilypond: patch Allows glissandi to span multiple lines., lilypond, 09:24
  • Re: Issue 1706 in lilypond: Beaming causes lilypond to crash, lilypond, 09:20
  • Re: Issue 1706 in lilypond: Beaming causes lilypond to crash, lilypond, 09:12
  • Re: Build error regarding mf2pt1 with latest texlive (2011) and lilypond 2.14.1, Werner LEMBERG, 04:52
  • Re: Percussion Notation, Reinhold Kainhofer, 04:51
  • Issue 1714 in lilypond: Build error regarding mf2pt1 with latest texlive (2011) and lilypond, lilypond, 03:30
  • Re: Build error regarding mf2pt1 with latest texlive (2011) and lilypond 2.14.1, Dmytro O. Redchuk, 03:30
  • Re: Issue 1161 in lilypond: Lyrics is not centered with CENTER affinity if there is another Lyrics with one of UP or DOWN, lilypond, 03:25
  • Re: Issue 1713 in lilypond: Whole note/dotted note collision in polyphony, lilypond, 03:21
  • Re: Full notes and half notes are drawn filled, Dmytro O. Redchuk, 03:12
  • Build error regarding mf2pt1 with latest texlive (2011) and lilypond 2.14.1, Marc Payne, 01:35
  • Re: Whereis lilylib etc. - Build system - Python modules, Villum Sejersen, 01:24
• June 26, 2011
  • Re: Issue 1248 in lilypond: GUB produces a random "unbound open-file" in regtests, lilypond, 21:43
  • Re: Issue 1626 in lilypond: Articulate produces faulty barcheck warnings, Peter Chubb, 21:00
  • Re: Issue 1626 in lilypond: Articulate produces faulty barcheck warnings, Colin Campbell, 20:50
  • Re: Whereis lilylib etc. - Build system - Python modules, Colin Campbell, 20:46
  • Re: Issue 1626 in lilypond: Articulate produces faulty barcheck warnings, Peter Chubb, 20:28
  • Re: Issue 1015 in lilypond: doc line width, lilypond, 19:39
  • Re: Issue 1015 in lilypond: doc line width, lilypond, 19:34
  • Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 19:30
  • Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 18:47
  • Re: Issue 1015 in lilypond: doc line width, lilypond, 18:43
  • Re: Issue 1713 in lilypond: Whole note/dotted note collision in polyphony, lilypond, 16:46
  • Re: Whole-note/dotted-note collisions in polyphony, Colin Campbell, 15:17
  • Issue 1713 in lilypond: Whole note/dotted note collision in polyphony, lilypond, 15:17
  • Re: Issue 1692 in lilypond: Spanner::calc_normalized_endpoints is broken for line-spanners, lilypond, 12:32
  • Re: Issue 1706 in lilypond: Beaming causes lilypond to crash, lilypond, 12:28
  • Whole-note/dotted-note collisions in polyphony, Connor Harris, 12:16
  • Re: fingerings with fingeringOrientations = #'(up left), -Eluze, 11:14
  • Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 10:37
  • Issue 1712 in lilypond: Braces redesigned, lilypond, 08:42
  • Re: Issue 682 in lilypond: annotate-spacing should produce horizontal info as well, lilypond, 08:38
  • Re: Issue 1687 in lilypond: separating flags from noteheads in font files, lilypond, 07:43
  • Re: Collision between flags on down-stems and note-heads in single-staffpolyphony, Phil Holmes, 05:53
  • Re: Issue 39 in lilypond: collision flag notehead with polyphony, lilypond, 05:53
  • Re: Accidentals may cause odd-looking slurs, Valentin Villenave, 05:08
  • Re: fingerings with fingeringOrientations = #'(up left), -Eluze, 04:54
  • Whereis lilylib etc. - Build system - Python modules, Villum Sejersen, 03:06
  • Re: Issue 1711 in lilypond: Pitch bend tuning adjustments, lilypond, 02:50
  • Re: Issue 1647 in lilypond: MIDI skips note if the pitch is already sounding in the same channel, lilypond, 02:35
  • Collision between flags on down-stems and note-heads in single-staff polyphony, Connor Harris, 00:25
• June 25, 2011
  • Re: Issue 1607 in lilypond: patch for mandolin freboard diagrams, lilypond, 23:44
  • Re: Issue 1626 in lilypond: Articulate produces faulty barcheck warnings, lilypond, 23:40
  • Re: Issue 1652 in lilypond: Assertion error when line-count of StaffSymbol set to 0 and one uses a note in the middle of the (non-existant) staff, lilypond, 23:36
  • Re: Issue 1689 in lilypond: doc: changing example for overriding positions, lilypond, 23:32
  • Re: Issue 1704 in lilypond: Website: old version of website still active, lilypond, 23:21
  • Re: Issue 1647 in lilypond: MIDI skips note if the pitch is already sounding in the same channel, lilypond, 23:17
  • Re: Issue 1643 in lilypond: Part Combine problems, lilypond, 19:42
  • Issue 1711 in lilypond: Pitch bend tuning adjustments, lilypond, 18:48
  • Re: Issue 1259 in lilypond: DynamicTextSpanner #'style = #'none doesn't work over \break, lilypond, 18:13
  • Re: enharmonic problem with \transpose - should we modify it?, Keith OHara, 18:12
  • Re: Issue 1433 in lilypond: \breakDynamicSpan breaks with \break ("bounds of spanner are invalid"), lilypond, 18:09
  • Re: Issue 1710 in lilypond: rearrange flag definitions in feta-flags.mf, lilypond, 17:21
  • Re: Issue 1468 in lilypond: stdout vs. stderr for some messages, lilypond, 16:04
  • Issue 1710 in lilypond: rearrange flag definitions in feta-flags.mf, lilypond, 15:39
  • Re: Issue 1687 in lilypond: separating flags from noteheads in font files, lilypond, 15:33
  • Re: Issue 1709 in lilypond: Add feta-flags to build system, lilypond, 15:29
  • Re: Issue 1706 in lilypond: Beaming causes lilypond to crash, lilypond, 13:14
  • Re: Accidentals may cause odd-looking slurs, Colin Campbell, 12:58
  • Issue 1709 in lilypond: Add feta-flags to build system, lilypond, 12:51
  • Accidentals may cause odd-looking slurs, Valentin Villenave, 12:50
  • Re: Issue 1643 in lilypond: Part Combine problems, lilypond, 12:15
  • Re: Issue 1707 in lilypond: add python -tt to build system, lilypond, 12:09
  • Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 12:05
  • Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 12:01
  • Re: fingerings with fingeringOrientations = #'(up left), Phil Holmes, 11:50
  • Re: Full notes and half notes are drawn filled, Phil Holmes, 11:46
  • Re: Issue 1707 in lilypond: add python -tt to build system, lilypond, 11:39
  • Re: Issue 1692 in lilypond: Spanner::calc_normalized_endpoints is broken for line-spanners, lilypond, 11:18
  • fingerings with fingeringOrientations = #'(up left), -Eluze, 04:49
  • Full notes and half notes are drawn filled, Jérôme M . Berger, 04:31
  • Re: Issue 1643 in lilypond: Part Combine problems, lilypond, 04:11
  • Re: Issue 1643 in lilypond: Part Combine problems, lilypond, 03:28
  • Re: Issue 1697 in lilypond: Add ties from Completion_note_heads_engraver to a TieColumn, lilypond, 03:00
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 02:56
  • Re: Issue 1696 in lilypond: Breathing sign incorrectly positioned on custom staves using 'line-positions, lilypond, 02:52
  • Re: Issue 1696 in lilypond: Breathing sign incorrectly positioned on custom staves using 'line-positions, lilypond, 02:48
  • Re: Issue 1685 in lilypond: links to spanish "changes" manual, lilypond, 02:44
  • Re: Issue 1679 in lilypond: textspan can end prematurely when entering an empty bar, lilypond, 02:40
  • Re: Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly, lilypond, 02:36
  • Re: Issue 1658 in lilypond: Doc: need documentation of \cueClef and \cueDuringWithClef, lilypond, 02:32
  • Re: Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly, lilypond, 02:28
  • Re: Issue 1658 in lilypond: Doc: need documentation of \cueClef and \cueDuringWithClef, lilypond, 02:24
  • Re: Issue 1658 in lilypond: Doc: need documentation of \cueClef and \cueDuringWithClef, lilypond, 02:19
  • Re: Issue 1615 in lilypond: lily-git.tcl not working: savannah sometimes does not like git fetch --depth, lilypond, 02:12
  • Re: Issue 1643 in lilypond: Part Combine problems, David Kastrup, 01:45
• June 24, 2011
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'ex, Keith OHara, 22:25
  • Re: Issue 1643 in lilypond: Part Combine problems, lilypond, 20:54
  • Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 17:38
  • Re: Issue 1708 in lilypond: Adds ly:engraver-property to engraver-scheme, lilypond, 15:37
  • Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 15:03
  • Issue 1708 in lilypond: Adds ly:engraver-property to engraver-scheme, lilypond, 10:51
  • Re: Issue 1673 in lilypond: patch Allows glissandi to span multiple lines., lilypond, 10:47
  • Re: Issue 1706 in lilypond: Beaming causes lilypond to crash, lilypond, 10:34
  • Issue 1707 in lilypond: add python -tt to build system, lilypond, 09:59
  • Re: Windows/DOS PATH statement again, Graham Percival, 09:56
  • Re: Windows/DOS PATH statement again, Colin Campbell, 08:40
  • Re: Windows/DOS PATH statement again, Phil Holmes, 08:17
  • RE: Windows/DOS PATH statement again, James Lowe, 07:50
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, bruys ., 05:59
  • Windows/DOS PATH statement again, Phil Holmes, 05:03
• June 23, 2011
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, Keith OHara, 21:22
  • Re: Issue 1682 in lilypond: Website version links need updating, lilypond, 18:42
  • Re: 2.12 docs link redirects to current stable, Federico Bruni, 16:05
  • Re: 2.12 docs link redirects to current stable, Graham Percival, 14:43
  • Re: 2.12 docs link redirects to current stable, Federico Bruni, 13:22
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, David Kastrup, 09:21
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Graham Percival, 09:19
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Dmytro O. Redchuk, 09:09
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, Graham Percival, 09:00
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Colin Campbell, 08:48
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, David Kastrup, 08:40
  • Issue 1706 in lilypond: Beaming causes lilypond to crash, lilypond, 08:29
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Graham Percival, 07:47
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, lilypond, 07:39
  • Issue 1705 in lilypond: New breve rest with ledger lines, lilypond, 07:25
  • Re: Issue 1685 in lilypond: links to spanish "changes" manual, lilypond, 07:18
  • Re: Issue 1502 in lilypond: Document information in PDF headers requires escapes for accented characters, lilypond, 05:23
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, Keith OHara, 05:17
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Dmytro O. Redchuk, 01:54
• June 22, 2011
  • Re: Issue 1502 in lilypond: Document information in PDF headers requires escapes for accented characters, lilypond, 22:23
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Colin Campbell, 21:06
  • Re: Issue 1685 in lilypond: links to spanish "changes" manual, lilypond, 20:54
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Colin Campbell, 20:52
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, bruys ., 18:45
  • Re: Issue 1685 in lilypond: links to spanish "changes" manual, lilypond, 12:30
  • Re: Issue 1287 in lilypond: Notation 2.9 Ancient notation does not follow doc policy, lilypond, 12:26
  • Re: 2.12 docs link redirects to current stable, Francisco Vila, 12:24
  • Re: Issue 1685 in lilypond: links to spanish "changes" manual, lilypond, 12:18
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 11:05
  • Re: Issue 1219 in lilypond: Broken tie may become a too small dot, lilypond, 10:32
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 10:11
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, bruys ., 08:27
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Dmytro O. Redchuk, 07:47
  • RE: bug report on 2.15.2 Mac OS X Intel version, James Lowe, 07:35
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Graham Percival, 07:25
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), David Kastrup, 07:17
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Graham Percival, 06:53
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Dmytro O. Redchuk, 03:05
  • Re: Issue 1349 in lilypond: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used., lilypond, 01:23
• June 21, 2011
  • Re: Issue 1682 in lilypond: Website version links need updating, lilypond, 22:17
  • Re: Issue 1704 in lilypond: Website: old version of website still active, lilypond, 19:29
  • Re: Issue 1272 in lilypond: remove old /web/, lilypond, 19:25
  • Issue 1704 in lilypond: Website: old version of website still active, lilypond, 18:33
  • Re: Issue 1349 in lilypond: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used., lilypond, 16:29
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Graham Percival, 15:53
  • Re: Issue 1349 in lilypond: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used., lilypond, 15:48
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, lilypond, 15:32
  • Re: Issue 1349 in lilypond: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used., lilypond, 15:28
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, lilypond, 15:18
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, lilypond, 13:25
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, lilypond, 12:22
  • Re: Issue 1640 in lilypond: Consecutive glissandos not typeset, lilypond, 11:33
  • Re: Issue 1639 in lilypond: Glissando between chords at end of measure prevents break and is sometimes not printed, lilypond, 11:29
  • Re: Issue 1639 in lilypond: Glissando between chords at end of measure prevents break and is sometimes not printed, lilypond, 11:25
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 11:21
  • Re: Issue 1618 in lilypond: unpredictable placement of rests, lilypond, 11:17
  • Re: Issue 1617 in lilypond: chordGlissando is a hack that should be replaced with a Glissando property such as 'connect-all, lilypond, 11:13
  • Re: Issue 1614 in lilypond: DynamicTextSpanner documentation is wrong, lilypond, 11:08
  • Re: Issue 1547 in lilypond: Too many colliding rests, lilypond, 11:04
  • Re: Issue 1502 in lilypond: Document information in PDF headers requires escapes for accented characters, lilypond, 11:00
  • Re: Issue 1043 in lilypond: Cross-staff beams confuse skyline calculations, lilypond, 10:55
  • Re: bug report on 2.15.2 Mac OS X Intel version, Hans Aberg, 09:49
  • Re: Issue 682 in lilypond: annotate-spacing should produce horizontal info as well, lilypond, 08:15
  • Re: Issue 687 in lilypond: Enhancement: inequal MIDI quantization of equal durations (swing, rubato), lilypond, 08:11
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Dmytro O. Redchuk, 07:32
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), lilypond, 07:28
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Dmytro O. Redchuk, 07:28
  • Re: Issue 1508 in lilypond: Key signature wrong with cued music, lilypond, 07:24
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), lilypond, 07:15
  • FW: bug report on 2.15.2 Mac OS X Intel version, James Lowe, 06:55
  • RE: bug report on 2.15.2 Mac OS X Intel version, James Lowe, 06:43
  • FW: bug report on 2.15.2 Mac OS X Intel version, James Lowe, 06:28
  • RE: bug report on 2.15.2 Mac OS X Intel version, James Lowe, 06:13
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, lilypond, 05:59
  • bug report on 2.15.2 Mac OS X Intel version, Henk Verhaar, 05:55
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Dmytro O. Redchuk, 05:52
  • Re: Issue 1200 in lilypond: GUB does something with fontforge all the time, lilypond, 05:52
  • Re: Issue 1200 in lilypond: GUB does something with fontforge all the time, lilypond, 05:48
  • Re: Issue 1050 in lilypond: website translations should use gettext, lilypond, 05:44
  • Re: Issue 1015 in lilypond: doc line width, lilypond, 05:40
  • Re: Issue 1333 in lilypond: Enhancement: beamed acciaccaturas should be printed with a slash, lilypond, 05:36
  • Re: Issue 1287 in lilypond: Notation 2.9 Ancient notation does not follow doc policy, lilypond, 05:32
  • Re: Issue 1508 in lilypond: Key signature wrong with cued music, lilypond, 05:28
  • Re: Issue 1669 in lilypond: Empty contexts sometimes take up too much space, lilypond, 05:24
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Phil Holmes, 05:20
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Graham Percival, 05:16
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), David Kastrup, 05:11
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 04:40
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Graham Percival, 04:39
  • Re: Issue 1682 in lilypond: Website version links need updating, lilypond, 04:36
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), David Kastrup, 04:33
• June 20, 2011
  • Re: Issue 1682 in lilypond: Website version links need updating, lilypond, 23:43
  • Re: Issue 1682 in lilypond: Website version links need updating, Colin Campbell, 23:10
  • probably old link to 2.12.3, -Eluze, 18:24
  • 2.12 docs link redirects to current stable, Federico Bruni, 16:45
  • Re: Issue 1702 in lilypond: Unaesthetic beam slope, lilypond, 16:08
  • Re: Issue 1682 in lilypond: Website version links need updating, lilypond, 14:31
  • Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile, lilypond, 14:08
  • [no subject], walter freihube, 12:39
  • Re: Issue 1641 in lilypond: noBeam disables beaming of prior notes, lilypond, 10:50
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), lilypond, 09:56
  • Re: Issue 1702 in lilypond: Unaesthetic beam slope, lilypond, 08:13
  • Re: Cross-staff beam unaesthetic (defect 2.12 -> 2.14), Xavier Scheuer, 05:05
  • Re: Issue 1702 in lilypond: Unaesthetic beam slope, lilypond, 03:48
  • Issue 1703 in lilypond: slur moves on its own (in specific situations), lilypond, 02:50
  • Re: slur moves on its own (in specific situations), Dmytro O. Redchuk, 02:50
  • Re: Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly, lilypond, 02:39
  • Re: Issue 1668 in lilypond: staff-staff padding is inserted below the last nonstaff, lilypond, 02:35
  • Re: Issue 1679 in lilypond: textspan can end prematurely when entering an empty bar, lilypond, 02:31
  • Re: Issue 1680 in lilypond: Vertical spacing stretchability affects compressibility, lilypond, 02:27
  • Re: Issue 1696 in lilypond: Breathing sign incorrectly positioned on custom staves using 'line-positions, lilypond, 02:23
• June 19, 2011
  • Re: Issue 1702 in lilypond: Unaesthetic beam slope, lilypond, 19:50
  • RE: missing backslash before Program Files in http://www.lilypond.org/windows.html, James Lowe, 19:45
  • Re: Cross-staff beam unaesthetic (defect 2.12 -> 2.14), Keith OHara, 18:10
  • Re: Issue 1702 in lilypond: Unaesthetic beam slope, lilypond, 16:24
  • RE: missing backslash before Program Files in http://www.lilypond.org/windows.html, James Lowe, 15:44
  • Re: missing backslash before Program Files in http://www.lilypond.org/windows.html, Frédéric Bron, 15:32
  • Re: missing backslash before Program Files in http://www.lilypond.org/windows.html, Graham Percival, 15:06
  • RE: missing backslash before Program Files in http://www.lilypond.org/windows.html, James Lowe, 14:58
  • Re: Issue 1693 in lilypond: Attaches bound info to beam for better normalized-endpoint calculations, lilypond, 12:06
  • Re: \midi plays straight through repeat marks, Reinhold Kainhofer, 11:36
  • Re: Cross-staff beam unaesthetic (defect 2.12 -> 2.14), Phil Holmes, 11:06
  • Issue 1702 in lilypond: Unaesthetic beam slope, lilypond, 11:06
  • Re: \midi plays straight through repeat marks, Graham Percival, 10:55
  • Cross-staff beam unaesthetic (defect 2.12 -> 2.14), Xavier Scheuer, 10:31
  • Re: \midi plays straight through repeat marks, Reinhold Kainhofer, 10:22
  • Re: \midi plays straight through repeat marks, Graham Percival, 09:26
  • Re: \midi plays straight through repeat marks, Michael Hendry, 09:04
  • Re: \midi plays straight through repeat marks, Xavier Scheuer, 07:01
  • \midi plays straight through repeat marks, Michael Hendry, 06:57
  • Re: Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly, lilypond, 06:19
  • Re: Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly, lilypond, 05:40
  • Re: missing backslash before Program Files in http://www.lilypond.org/windows.html, Graham Percival, 05:32
  • Re: missing backslash before Program Files in http://www.lilypond.org/windows.html, Frédéric Bron, 05:08
• June 18, 2011
  • Re: Issue 1700 in lilypond: Chord names collide when several note-columns lay in between, lilypond, 23:16
  • Re: Issue 1700 in lilypond: Chord names collide when several note-columns lay in between, lilypond, 23:11
  • Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, lilypond, 21:37
  • Re: Issue 1697 in lilypond: Add ties from Completion_note_heads_engraver to a TieColumn, lilypond, 19:02
  • Re: Issue 1696 in lilypond: Breathing sign incorrectly positioned on custom staves using 'line-positions, lilypond, 18:56
  • Re: Issue 1700 in lilypond: Chord names collide when several note-columns lay in between, lilypond, 18:36
  • Re: missing backslash before Program Files in http://www.lilypond.org/windows.html, Graham Percival, 18:27
  • Re: missing backslash before Program Files in http://www.lilypond.org/windows.html, Graham Percival, 18:25
  • Re: missing backslash before Program Files in http://www.lilypond.org/windows.html, Frédéric Bron, 18:02
  • Issue 1700 in lilypond: Chord names collide when several note-columns lay in between, lilypond, 17:09
  • Re: missing backslash before Program Files in http://www.lilypond.org/windows.html, Graham Percival, 15:33
  • missing backslash before Program Files in http://www.lilypond.org/windows.html, Frédéric Bron, 15:21
  • Re: Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly, lilypond, 13:06
  • Re: Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly, lilypond, 12:42
  • Re: Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly, lilypond, 12:16
  • Re: Issue 1658 in lilypond: Doc: need documentation of \cueClef and \cueDuringWithClef, lilypond, 12:12
  • Re: Issue 1658 in lilypond: Doc: need documentation of \cueClef and \cueDuringWithClef, lilypond, 12:07
  • Re: Issue 1666 in lilypond: Docs problem: fretted-string-harmonics-in-tablature snippet, lilypond, 10:51
  • Re: Issue 855 in lilypond: fix the command index, lilypond, 10:31
  • Re: Issue 1245 in lilypond: festival song output is uncompletely undocumented, lilypond, 10:27
  • Re: Issue 1666 in lilypond: Docs problem: fretted-string-harmonics-in-tablature snippet, lilypond, 10:23
  • Re: Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly, lilypond, 10:19
  • Re: Issue 855 in lilypond: fix the command index, lilypond, 08:26
  • Re: Issue 1245 in lilypond: festival song output is uncompletely undocumented, lilypond, 08:16
  • Re: Issue 1666 in lilypond: Docs problem: fretted-string-harmonics-in-tablature snippet, lilypond, 08:08
  • Re: Issue 1665 in lilypond: one-character typo in predefined-guitar-fretboards.ly, lilypond, 06:26
  • Re: Issue 1680 in lilypond: Vertical spacing stretchability affects compressibility, lilypond, 02:02
• June 17, 2011
  • Re: Issue 1695 in lilypond: Clef change placed outside score, lilypond, 19:01
  • Re: Issue 1695 in lilypond: Clef change placed outside score, lilypond, 18:57
  • Re: Issue 1693 in lilypond: Attaches bound info to beam for better normalized-endpoint calculations, lilypond, 12:48
  • Issue 1698 in lilypond: Slurs and ties are not correct over repeats, lilypond, 10:26
  • Re: Issue 1693 in lilypond: Attaches bound info to beam for better normalized-endpoint calculations, lilypond, 10:15
  • Re: Erroneous "unterminated slur" message at end of first time bar, Phil Holmes, 10:11
  • Issue 1699 in lilypond: Automated numbering for footnotes, lilypond, 10:05
  • [no subject], walter freihube, 09:35
  • Re: enharmonic problem with \transpose - should we modify it?, Hans Aberg, 05:05
  • Erroneous "unterminated slur" message at end of first time bar, Michael Hendry, 04:45
  • Re: enharmonic problem with \transpose - should we modify it?, Keith OHara, 01:19
• June 16, 2011
  • Re: Issue 1359 in lilypond: GUB always rebuilds everywhere, lilypond, 21:57
  • Re: Issue 1658 in lilypond: Doc: need documentation of \cueClef and \cueDuringWithClef, lilypond, 21:53
  • Re: Issue 1695 in lilypond: Clef change placed outside score, lilypond, 16:38
  • Re: Issue 1697 in lilypond: Add ties from Completion_note_heads_engraver to a TieColumn, lilypond, 16:18
  • Re: enharmonic problem with \transpose - should we modify it?, Janek Warchoł, 15:48
  • Issue 1697 in lilypond: Add ties from Completion_note_heads_engraver to a TieColumn, lilypond, 12:27
  • Re: Issue 1694 in lilypond: Modifies Spanner::spanner_length to better handle line-spanners, lilypond, 12:23
  • Re: Issue 1693 in lilypond: Attaches bound info to beam for better normalized-endpoint calculations, lilypond, 09:19
  • enharmonic problem with \transpose - should we modify it?, Janek Warchoł, 05:53
  • [no subject], walter freihube, 00:46
• June 15, 2011
  • Re: Issue 1696 in lilypond: Breathing sign incorrectly positioned on custom staves using 'line-positions, lilypond, 17:53
  • Issue 1696 in lilypond: Breathing sign incorrectly positioned on custom staves using 'line-positions, lilypond, 16:21
  • Re: Issue 1658 in lilypond: Doc: need documentation of \cueClef and \cueDuringWithClef, lilypond, 14:40
  • Re: misaligned rest in quatuor in 2.14.1, Francisco Vila, 12:53
  • Re: Issue 1695 in lilypond: Clef change placed outside score, lilypond, 12:10
  • Re: Clef change placed outside score, Jay Anderson, 10:28
  • Re: Issue 1695 in lilypond: Clef change placed outside score, lilypond, 10:09
  • Re: Clef change placed outside score, Ralph Palmer, 09:11
  • Issue 1695 in lilypond: Clef change placed outside score, lilypond, 09:10
  • Re: misaligned rest in quatuor in 2.14.1, Ralph Palmer, 08:49
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 08:48
  • Issue 1694 in lilypond: Modifies Spanner::spanner_length to better handle line-spanners, lilypond, 04:30
  • Issue 1693 in lilypond: Attaches bound info to beam for better normalized-endpoint calculations, lilypond, 04:26
• June 14, 2011
  • Clef change placed outside score, Jay Anderson, 23:55
  • misaligned rest in quatuor in 2.14.1, Marc Mouries, 21:27
  • Re: slur moves on its own (in specific situations), Neil Puttock, 18:11
  • Re: Issue 1679 in lilypond: textspan can end prematurely when entering an empty bar, lilypond, 17:58
  • Re: Upbeat with grace and voices, Neil Puttock, 17:47
  • Re: fretted-string-harmonics-in-tablature snippet, Janek Warchoł, 17:01
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 16:36
  • Re: Issue 1655 in lilypond: Handles longa in MultiMeasureRest, lilypond, 15:11
  • Re: fretted-string-harmonics-in-tablature snippet, Federico Bruni, 13:55
  • Upbeat with grace and voices, Friedrich Fischer, 12:35
  • Upbeat with grace and voices, Friedrich Fischer, 12:33
  • Re: Issue 1687 in lilypond: separating flags from noteheads in font files, lilypond, 09:29
  • Re: Issue 1688 in lilypond: New half-closed hihat symbol for drum mode, lilypond, 09:04
  • Re: Issue 1689 in lilypond: doc: changing example for overriding positions, lilypond, 08:15
  • Re: fretted-string-harmonics-in-tablature snippet, Graham Percival, 08:04
  • Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 08:03
  • Re: Issue 1692 in lilypond: Spanner::calc_normalized_endpoints is broken for line-spanners, lilypond, 07:21
  • Issue 1692 in lilypond: Spanner::calc_normalized_endpoints is broken for line-spanners, lilypond, 07:17
  • Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 04:58
  • Re: fretted-string-harmonics-in-tablature snippet, Janek Warchoł, 03:44
  • Re: Issue 1688 in lilypond: New half-closed hihat symbol for drum mode, lilypond, 01:22
• June 13, 2011
  • Re: Issue 1688 in lilypond: New half-closed hihat symbol for drum mode, lilypond, 23:35
  • Re: fretted-string-harmonics-in-tablature snippet, Federico Bruni, 17:11
  • Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 16:55
  • Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 16:27
  • Re: fretted-string-harmonics-in-tablature snippet, Janek Warchoł, 14:11
  • Re: Extracting parts: why does Devnull take as much space as a normal staff ?, Francisco Vila, 11:52
  • Extracting parts: why does Devnull take as much space as a normal staff ?, Jean-Charles Malahieude, 11:36
  • Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 10:42
  • Re: Issue 1686 in lilypond: Compile scheme files to scm/out when using Guile V2.n. Also load and run .go files if available, lilypond, 06:35
  • Re: Issue 1688 in lilypond: New half-closed hihat symbol for drum mode, lilypond, 01:54
• June 12, 2011
  • Re: Issue 1688 in lilypond: New half-closed hihat symbol for drum mode, lilypond, 22:51
  • Re: Issue 1687 in lilypond: separating flags from noteheads in font files, lilypond, 17:18
  • Re: Issue 1568 in lilypond: ENHANCEMENT: Adds the Articulate script with documentation, lilypond, 15:38
  • Re: Issue 1684 in lilypond: CueClefs: Use middleCClefPosition in the key engraver, lilypond, 15:34
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 15:30
  • Re: Issue 1660 in lilypond: harmonicOn doesn't work in TabStaff, lilypond, 15:22
  • Issue 1690 in lilypond: old announcements+changes on website, lilypond, 12:12
  • Re: Issue 1689 in lilypond: doc: changing example for overriding positions, lilypond, 11:57
  • Re: Issue 1684 in lilypond: CueClefs: Use middleCClefPosition in the key engraver, lilypond, 10:52
  • Re: Issue 1508 in lilypond: Key signature wrong with cued music, lilypond, 10:48
  • Re: Issue 1508 in lilypond: Key signature wrong with cued music, lilypond, 10:44
  • Re: Issue 1660 in lilypond: harmonicOn doesn't work in TabStaff, lilypond, 10:05
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 10:01
  • Re: Issue 1689 in lilypond: doc: changing example for overriding positions, lilypond, 09:53
  • Issue 1689 in lilypond: doc: changing example for overriding positions, lilypond, 09:34
  • Re: Issue 1687 in lilypond: separating flags from noteheads in font files, lilypond, 03:30
  • Re: Issue 1688 in lilypond: New half-closed hihat symbol for drum mode, lilypond, 01:53
  • Re: Issue 1688 in lilypond: New half-closed hihat symbol for drum mode, lilypond, 01:06
  • Re: Issue 1688 in lilypond: New half-closed hihat symbol for drum mode, lilypond, 01:02
  • Issue 1688 in lilypond: New half-closed hihat symbol for drum mode, lilypond, 00:49
• June 11, 2011
  • Re: Issue 1687 in lilypond: separating flags from noteheads in font files, lilypond, 20:19
  • Re: Issue 1213 in lilypond: Segmentation fault : extender triggers an infinite loop in Context::now_mom (), lilypond, 19:57
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 11:44
  • Re: Issue 1615 in lilypond: lily-git.tcl not working: savannah sometimes does not like git fetch --depth, lilypond, 11:40
  • Re: Issue 1687 in lilypond: separating flags from noteheads in font files, lilypond, 09:50
  • Re: Issue 1359 in lilypond: GUB always rebuilds everywhere, lilypond, 08:52
• June 10, 2011
  • Re: Trill Spanner, Colin Campbell, 23:48
  • Re: Issue 1615 in lilypond: lily-git.tcl not working: savannah sometimes does not like git fetch --depth, lilypond, 19:30
  • Issue 1687 in lilypond: separating flags from noteheads in font files, lilypond, 17:07
  • Re: Issue 1658 in lilypond: Doc: need documentation of \cueClef and \cueDuringWithClef, lilypond, 13:57
  • Re: Issue 1615 in lilypond: lily-git.tcl not working: savannah sometimes does not like git fetch --depth, lilypond, 10:13
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 10:09
  • Re: Issue 1637 in lilypond: include newest version of Fontforge in Lilydev, lilypond, 10:05
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 10:01
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 08:32
  • Re: Error in 2.14 Learning Manual, Phil Holmes, 06:07
  • Error in 2.14 Learning Manual, Nick Baskin, 05:05
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 00:45
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 00:37
• June 09, 2011
  • Re: Trill Spanner, Colin Campbell, 23:58
  • Re: Issue 1680 in lilypond: Vertical spacing stretchability affects compressibility, lilypond, 23:54
  • Trill Spanner, Stefano Cucuzzella, 18:28
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 16:29
  • Re: Issue 1637 in lilypond: include newest version of Fontforge in Lilydev, lilypond, 16:25
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 16:21
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 16:00
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 15:37
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 15:03
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 13:54
  • Re: slur moves on its own (in specific situations), Mark Polesky, 10:37
  • Re: Correct Figured Bass signs (slashed and crossed numbers), Reinhold Kainhofer, 08:56
  • Re: Issue 1055 in lilypond: guile 2.0, lilypond, 08:08
  • Issue 1686 in lilypond: Compile scheme files to scm/out when using Guile V2.n. Also load and run .go files if available, lilypond, 08:03
  • Re: Issue 1615 in lilypond: lily-git.tcl not working: savannah sometimes does not like git fetch --depth, lilypond, 07:34
  • Issue 1685 in lilypond: links to spanish "changes" manual, lilypond, 07:10
  • Re: CHANGES -> 2.14 instead of 2.13, Graham Percival, 07:10
  • Re: CHANGES -> 2.14 instead of 2.13, Graham Percival, 07:05
  • Re: Issue 1615 in lilypond: lily-git.tcl not working: savannah sometimes does not like git fetch --depth, lilypond, 07:03
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 06:39
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 06:35
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 05:59
  • Re: Issue 1682 in lilypond: Website version links need updating, lilypond, 05:55
  • Re: Issue 1682 in lilypond: Website version links need updating, Graham Percival, 05:55
  • Re: slur moves on its own (in specific situations), Phil Holmes, 05:09
  • Re: Beams, Phil Holmes, 05:04
  • slur moves on its own (in specific situations), Mark Polesky, 02:30
  • Re: manual beams can run off edge of paper, Keith OHara, 00:36
• June 08, 2011
  • Re: Issue 1682 in lilypond: Website version links need updating, Colin Campbell, 23:48
  • Re: Issue 1669 in lilypond: Empty contexts sometimes take up too much space, lilypond, 23:00
  • manual beams can run off edge of paper, Jeremy Mates, 21:25
  • Beams, Nels Daily, 17:36
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 16:21
  • Re: Issue 1669 in lilypond: Empty contexts sometimes take up too much space, lilypond, 15:13
  • Re: Issue 1200 in lilypond: GUB does something with fontforge all the time, lilypond, 11:47
  • Re: Issue 1217 in lilypond: clean up undocumented regtests in 2.14.0., lilypond, 11:43
  • Re: Issue 1217 in lilypond: clean up undocumented regtests in 2.14.0., lilypond, 10:23
  • Re: Issue 1200 in lilypond: GUB rebuilds fontforge all the time, lilypond, 09:39
  • Re: Issue 1200 in lilypond: GUB rebuilds fontforge all the time, lilypond, 09:07
  • Re: Issue 1200 in lilypond: GUB rebuilds fontforge all the time, lilypond, 09:00
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 00:00
• June 07, 2011
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 22:11
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 18:53
  • Re: Issue 34 in lilypond: Grace synchronization, lilypond, 18:33
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 15:48
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 15:17
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 15:13
  • Re: LSR Snippet in Doc needs modifying, Graham Percival, 15:09
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 14:23
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 14:19
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 14:12
  • RE: LSR Snippet in Doc needs modifying, James Lowe, 14:05
  • Issue 1684 in lilypond: CueClefs: Use middleCClefPosition in the key engraver, lilypond, 13:47
  • Re: Issue 1217 in lilypond: clean up undocumented regtests in 2.14.0., lilypond, 13:42
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 13:32
  • Re: LSR Snippet in Doc needs modifying, Phil Holmes, 13:22
  • Re: Issue 1682 in lilypond: Website version links need updating, lilypond, 13:09
  • Re: Issue 1568 in lilypond: ENHANCEMENT: Adds the Articulate script with documentation, lilypond, 13:05
  • Re: Issue 1568 in lilypond: ENHANCEMENT: Adds the Articulate script with documentation, lilypond, 13:01
  • Re: Issue 1496 in lilypond: Update Pango to 1.28.3, lilypond, 12:57
  • Re: Issue 1171 in lilypond: docs search box always does 2.14, lilypond, 12:53
  • Re: Issue 982 in lilypond: web big-html and pdf look bad, lilypond, 12:49
  • Re: Issue 977 in lilypond: GUB build numbers, lilypond, 12:45
  • Re: Issue 1217 in lilypond: clean up undocumented regtests in 2.14.0., lilypond, 12:41
  • Re: Issue 1567 in lilypond: Add documentation for footnotes, lilypond, 12:37
  • Re: Issue 1658 in lilypond: Doc: need documentation of \cueClef and \cueDuringWithClef, lilypond, 12:32
  • Re: Issue 1682 in lilypond: Website version links need updating, lilypond, 12:28
  • Re: Bugs in Debian, Carlo Stemberger, 12:25
  • Re: Issue 1213 in lilypond: Segmentation fault : extender triggers an infinite loop in Context::now_mom (), lilypond, 12:22
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 12:18
  • Re: Bugs in Debian, Carl Sorensen, 11:34
  • Re: Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 11:25
  • Issue 1683 in lilypond: The dynamic m is broken at staff-size-14, lilypond, 11:21
  • LSR Snippet in Doc needs modifying, James Lowe, 11:05
  • Re: CHANGES -> 2.14 instead of 2.13, Francisco Vila, 10:14
  • Re: Bugs in Debian, Carlo Stemberger, 09:29
  • Issue 1682 in lilypond: Website version links need updating, lilypond, 09:17
  • Re: 2.14 linux download page error, Colin Campbell, 09:17
  • Re: Bugs in Debian, Colin Campbell, 08:51
  • Re: CHANGES -> 2.14 instead of 2.13, Graham Percival, 08:41
  • Re: CHANGES -> 2.14 instead of 2.13, Francisco Vila, 08:14
  • Bugs in Debian, Carlo Stemberger, 07:43
  • Re: CHANGES -> 2.14 instead of 2.13, Graham Percival, 07:37
  • Re: CHANGES -> 2.14 instead of 2.13, Francisco Vila, 07:33
  • Re: CHANGES -> 2.14 instead of 2.13, Graham Percival, 07:26
  • Re: CHANGES -> 2.14 instead of 2.13, Francisco Vila, 06:55
  • Re: CHANGES -> 2.14 instead of 2.13, Francisco Vila, 06:51
  • Re: Issue 1658 in lilypond: Doc: need documentation of \cueClef and \cueDuringWithClef, lilypond, 06:44
  • Re: Website doc search still using 2.12, Graham Percival, 06:42
  • Re: Issue 1672 in lilypond: patch Allows LilyPond to ignore certain note-heads in a stem, lilypond, 06:41
  • Re: Issue 1672 in lilypond: patch Allows LilyPond to ignore certain note-heads in a stem, lilypond, 06:37
  • Re: 2.14 linux download page error, Graham Percival, 06:32
  • Re: source download link broken, Graham Percival, 06:30
  • Re: Issue 1658 in lilypond: Doc: need documentation of \cueClef and \cueDuringWithClef, lilypond, 06:26
  • Re: CHANGES -> 2.14 instead of 2.13, Xavier Scheuer, 03:45
  • Website doc search still using 2.12, Xavier Scheuer, 03:42
  • CHANGES -> 2.14 instead of 2.13, Xavier Scheuer, 03:38
• June 06, 2011
  • Re: Issue 1658 in lilypond: Doc: need documentation of \cueClef and \cueDuringWithClef, lilypond, 18:28
  • source download link broken, Josiah Boothby, 17:40
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 14:18
  • Re: Issue 737 in lilypond: Enhancement: support for footnotes and/or endnotes., lilypond, 14:13
  • Re: Issue 1658 in lilypond: Doc: need documentation of \cueClef and \cueDuringWithClef, lilypond, 11:22
  • Re: Issue 1681 in lilypond: \change Staff cannot be the first element inside a musical expression, lilypond, 08:33
• June 05, 2011
  • Re: \change Staff does not work in the very beginning, Colin Campbell, 22:26
  • Issue 1681 in lilypond: \change Staff cannot be the first element inside a musical expression, lilypond, 22:18
  • Re: Issue 1633 in lilypond: pdf utf-16be breaks doc compile, lilypond, 18:51
• June 04, 2011
  • Re: Issue 1043 in lilypond: Cross-staff beams confuse skyline calculations, lilypond, 23:21
  • Re: Issue 1043 in lilypond: Cross-staff beams confuse skyline calculations, lilypond, 23:17
  • Issue 1680 in lilypond: Vertical spacing stretchability affects compressibility, lilypond, 23:01
  • Re: Issue 1649 in lilypond: ly:arpeggio::brew-chord-bracket can lead to tight horizontal spacing, lilypond, 18:07
  • Re: Issue 1648 in lilypond: MIDI: no defined order between a simultaneous note-on and note-off, lilypond, 18:03
  • Re: Issue 1649 in lilypond: ly:arpeggio::brew-chord-bracket can lead to tight horizontal spacing, lilypond, 17:59
  • Re: Issue 1442 in lilypond: staff-staff padding all appears after the last nonstaff, lilypond, 17:55
  • Re: Issue 1560 in lilypond: Lyrics can not be aligned below ossia staff, lilypond, 17:51
  • Re: Issue 1667 in lilypond: silly bug about thinking cross-staff beams, lilypond, 17:46
  • Re: Issue 487 in lilypond: stems of beamed notes too long before staff change, lilypond, 17:42
  • Re: Issue 1671 in lilypond: Vertical spacing: undesired figured bass stretching, lilypond, 17:38
  • Re: Issue 1674 in lilypond: String-match unbound function unavailable in lilypond, lilypond, 17:34
  • Re: Issue 665 in lilypond: Request: MusicXML backend, lilypond, 14:29
  • Re: Issue 1362 in lilypond: Enhancement: automatic dynamics grouping when computing vertical alignment, lilypond, 14:25
  • Re: Issue 487 in lilypond: stems of beamed notes too long before staff change, lilypond, 14:21
• June 03, 2011
  • Re: Issue 1669 in lilypond: Empty contexts sometimes take up too much space, lilypond, 21:52
  • Re: Issue 1669 in lilypond: Empty contexts sometimes take up too much space, lilypond, 02:46
• June 02, 2011
  • Re: Issue 1679 in lilypond: textspan can end prematurely when entering an empty bar, lilypond, 16:59
  • Re: Issue 1679 in lilypond: textspan can end prematurely when entering an empty bar, lilypond, 16:32
  • Re: Issue 1679 in lilypond: textspan can end prematurely when entering an empty bar, lilypond, 16:00
  • Issue 1679 in lilypond: textspan can end prematurely when entering an empty bar, lilypond, 15:56
  • Re: MIDI: false warning, Phil Holmes, 07:24
  • Issue 1678 in lilypond: Midi gives false warnings, lilypond, 07:23
  • Re: MIDI: false warning, Graham Percival, 07:13
  • Re: Issue 1660 in lilypond: harmonicOn doesn't work in TabStaff, lilypond, 06:37
  • Re: Issue 1670 in lilypond: Allow numbers in variable names: violin1mvt2 = c', David Kastrup, 04:03
  • Re: Issue 1670 in lilypond: Allow numbers in variable names: violin1mvt2 = c', Werner LEMBERG, 03:54
  • Re: Issue 1670 in lilypond: Allow numbers in variable names: violin1mvt2 = c', David Kastrup, 03:30
  • Re: Issue 665 in lilypond: Request: MusicXML backend, lilypond, 03:02
• June 01, 2011
  • Re: Issue 1664 in lilypond: Add link to LSR on web site, lilypond, 23:03
  • Re: Issue 1668 in lilypond: staff-staff padding is inserted below the last nonstaff, lilypond, 20:40
  • Re: Issue 1658 in lilypond: Doc: need documentation of \cueClef and \cueDuringWithClef, lilypond, 20:26
  • Re: Issue 1660 in lilypond: harmonicOn doesn't work in TabStaff, lilypond, 17:32
  • Re: Issue 1670 in lilypond: Allow numbers in variable names: violin1mvt2 = c', lilypond, 17:27
  • MIDI: false warning, Keith OHara, 17:08
  • Issue 1677 in lilypond: Partcombine misses notes, lilypond, 11:01
  • Re: Partcombine, Phil Holmes, 10:58
  • Re: Issue 39 in lilypond: collision flag notehead with polyphony, lilypond, 10:24
  • Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties, lilypond, 09:29
  • Re: Issue 665 in lilypond: Request: MusicXML backend, lilypond, 09:25
  • Re: Issue 1672 in lilypond: patch Allows LilyPond to ignore certain note-heads in a stem, lilypond, 09:18
  • Re: Partcombine, Reinhold Kainhofer, 07:04
  • Re: Partcombine, Xavier Scheuer, 03:02
  • \change Staff does not work in the very beginning, -Eluze, 02:21
  • \cjan, -Eluze, 00:18

---

[Prev Period]

[Next Period]

---

Mail converted by MHonArc