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: Sun Jul 31 2011 23:12:13 -0400 Messages in reverse chronological order

[Next Period]

---

• July 31, 2011
  • Re: make doc, Graham Percival, 23:12
  • Re: Issue 1789 in lilypond: \tweak does not work for changing control-points of any but the first tie in chorded notes, lilypond, 20:58
  • Re: Issue 1792 in lilypond: dot-notehead collision, lilypond, 20:42
  • Re: Issue 1403 in lilypond: Enhancement: defining postfix commands in Scheme., lilypond, 19:13
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond 2.14.x, Christian Hitz, 18:47
  • Re: Issue 1794 in lilypond: Adds longas, maximas and non-standard tweaks to MultiMeasureRest, lilypond, 18:08
  • Re: Issue 1794 in lilypond: Adds longas, maximas and non-standard tweaks to MultiMeasureRest, lilypond, 17:16
  • Re: Issue 1793 in lilypond: Doc: change how lyrics in PianoStaff is documented, lilypond, 17:12
  • RE: png output with transparency and the option to have the renderingcropped to the score, James Lowe, 16:53
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 16:24
  • RE: Lilynet down?, James Lowe, 15:42
  • Re: Issue 1063 in lilypond: Reverting nested property fails to restore default value if preceded by override in same grob, lilypond, 15:29
  • Issue 1794 in lilypond: Adds longas, maximas and non-standard tweaks to MultiMeasureRest, lilypond, 15:21
  • Re: Issue 1792 in lilypond: dot-notehead collision, lilypond, 15:00
  • Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly, lilypond, 13:43
  • Lilynet down?, Jean-Charles Malahieude, 13:41
  • Re: Issue 1063 in lilypond: Reverting nested property fails to restore default value if preceded by override in same grob, lilypond, 13:04
  • make doc, Jean-Charles Malahieude, 12:29
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 12:15
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond 2.14.x, Floris van Manen, 10:50
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond2.14.x, Phil Holmes, 10:22
  • Re: Issue 1063 in lilypond: Reverting nested property fails to restore default value if preceded by override in same grob, lilypond, 10:19
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond 2.14.x, Christian Hitz, 09:46
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond 2.14.x, Floris van Manen, 08:31
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond 2.14.x, lilypond, 07:04
  • Re: Full measure rest should take more horizontal space, Phil Holmes, 07:02
  • Re: Issue 1635 in lilypond: clean up misleading warnings in website build, lilypond, 06:54
  • Re: Full measure rest should take more horizontal space, Janek Warchoł, 06:53
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 06:49
  • Re: Issue 1742 in lilypond: print transposed guitar chords on piano sheets, lilypond, 06:39
  • Full measure rest should take more horizontal space, Xavier Scheuer, 05:49
  • Re: png output with transparency and the option to have the renderingcropped to the score, Phil Holmes, 05:45
  • Re: lyrics with musical intro?, Phil Holmes, 05:40
  • Re: Completion_rest_engraver fails with fractional rests, Phil Holmes, 05:35
  • Re: Lilypond will not launch under OSX 10.7 Lion, Phil Holmes, 05:30
  • Issue 1793 in lilypond: Doc: change how lyrics in PianoStaff is documented, lilypond, 05:27
  • Re: version 2.14.2, notation reference manual, section 5.1.7 hasincorrect diagrams, Phil Holmes, 05:26
  • Re: odd macport config, Phil Holmes, 05:21
  • Re: Issue 1771 in lilypond: Nested reverts fail for properties which aren't set as defaults in define-grobs.scm, lilypond, 05:05
  • Re: Issue 1063 in lilypond: Reverting nested property fails to restore default value if preceded by override in same grob, lilypond, 04:42
  • Re: Issue 1 in lilypond: this is a test, lilypond, 04:15
  • Re: Issue 1 in lilypond: this is a test, lilypond, 04:11
  • Re: Issue 1 in lilypond: this is a test, lilypond, 03:31
  • Re: version 2.14.2, notation reference manual, section 5.1.7 hasincorrect diagrams, Trevor Daniels, 03:15
  • Re: Issue 1789 in lilypond: \tweak does not work for changing control-points of any but the first tie in chorded notes, lilypond, 02:25
  • version 2.14.2, notation reference manual, section 5.1.7 has incorrect diagrams, ehzone, 01:48
  • Re: Issue 1789 in lilypond: \tweak does not work for changing control-points of any but the first tie in chorded notes, lilypond, 00:59
  • Issue 1792 in lilypond: dot-notehead collision, lilypond, 00:26
• July 30, 2011
  • odd macport config, Floris van Manen, 19:52
  • Re: Issue 1788 in lilypond: auto numbering footnote checkin doesn't play with \null and \musicglyph, lilypond, 19:14
  • Re: Issue 1567 in lilypond: Add documentation for footnotes, lilypond, 19:10
  • Issue 1791 in lilypond: footnote numbering is 'out of order' when using multiple staves in a system, lilypond, 18:53
  • Re: Issue 1790 in lilypond: Proper loglevels: cmd-line option --loglevel=NONE/ERROR/WARN/PROGRESS/INFO/DEBUG, lilypond, 18:49
  • Re: Issue 1775 in lilypond: doc: add broken- and unbroken slur shaping function, lilypond, 18:45
  • Re: Issue 1790 in lilypond: Proper loglevels: cmd-line option --loglevel=NONE/ERROR/WARN/PROGRESS/INFO/DEBUG, lilypond, 18:18
  • Issue 1790 in lilypond: Proper loglevels: cmd-line option --loglevel=NONE/ERROR/WARN/PROGRESS/INFO/DEBUG, lilypond, 18:14
  • Re: Issue 1786 in lilypond: New engraver for braces, lilypond, 18:05
  • Re: Issue 1786 in lilypond: New engraver for braces, lilypond, 17:54
  • Re: Issue 1742 in lilypond: print transposed guitar chords on piano sheets, lilypond, 17:50
  • Re: Issue 1787 in lilypond: Hide ends of barlines inside staff lines., lilypond, 17:42
  • Re: Issue 1789 in lilypond: \tweak does not work for changing control-points of any but the first tie in chorded notes, lilypond, 15:03
  • Re: Issue 1789 in lilypond: \tweak is 'broken' when trying to tie chorded notes (other than the first note in the chord), lilypond, 14:32
  • Re: Issue 1775 in lilypond: doc: add broken- and unbroken slur shaping function, lilypond, 14:28
  • Issue 1789 in lilypond: \tweak is 'broken' when trying to tie chorded notes (other than the first note in the chord), lilypond, 14:24
  • RE: music function semantics, James Lowe, 14:22
  • Re: Issue 1775 in lilypond: doc: add broken- and unbroken slur shaping function, lilypond, 14:20
  • Re: Issue 1775 in lilypond: doc: add broken- and unbroken slur shaping function, lilypond, 14:08
  • Re: Issue 1742 in lilypond: print transposed guitar chords on piano sheets, lilypond, 14:03
  • Re: some comments do not appear in the tracker page, Jan Warchoł, 11:59
  • Re: Issue 1775 in lilypond: doc: add broken- and unbroken slur shaping function, lilypond, 10:42
  • Re: Issue 1663 in lilypond: Images missing on web site, Carl Sorensen, 08:30
  • Re: Issue 1663 in lilypond: Images missing on web site, Phil Holmes, 05:08
• July 29, 2011
  • Re: Issue 621 in lilypond: Dynamics should avoid cross-staff BarLines (e.g. GrandStaff, PianoStaff etc), lilypond, 23:05
  • Re: Issue 1663 in lilypond: Images missing on web site, Colin Campbell, 19:40
  • Re: Codas not followed in MIDI output, Keith OHara, 15:25
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 13:52
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 13:48
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 13:24
  • Codas not followed in MIDI output, Jon Toohill, 13:15
  • Re: Issue 1786 in lilypond: New engraver for braces, lilypond, 12:32
  • Re: some comments do not appear in the tracker page, Graham Percival, 12:11
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 10:21
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 09:51
  • Re: Issue 1567 in lilypond: Add documentation for footnotes, lilypond, 07:37
  • Re: Issue 1788 in lilypond: auto numbering footnote checkin doesn't play with \null and \musicglyph, lilypond, 07:30
  • Re: Issue 1788 in lilypond: auto numbering footnote checkin doesn't play with \null and \musicglyph, lilypond, 07:17
  • Issue 1788 in lilypond: auto numbering footnote checkin doesn't play with \null and \musicglyph, lilypond, 07:13
  • Re: some comments do not appear in the tracker page, Urs Liska, 05:42
  • RE: some comments do not appear in the tracker page, James Lowe, 04:21
  • Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display, Janek Warchoł, 01:48
  • Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes, lilypond, 01:43
  • Issue 1787 in lilypond: Hide ends of barlines inside staff lines., lilypond, 01:24
  • Re: Issue 652 in lilypond: create glyphs dynamically instead of PS code, lilypond, 01:20
  • Re: some comments do not appear in the tracker page, Janek Warchoł, 00:49
  • Re: Issue 1785 in lilypond: Compressible space before the first note of a line ?, lilypond, 00:40
  • Re: Issue 1785 in lilypond: Compressible space before the first note of a line ?, Keith OHara, 00:39
• July 28, 2011
  • Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes, lilypond, 18:15
  • Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes, lilypond, 18:09
  • Re: Issue 1767 in lilypond: Feta font - change breve vertical lines, lilypond, 17:30
  • Re: Issue 1767 in lilypond: Feta font - change breve vertical lines, lilypond, 17:18
  • Re: Failing regtests because of footnotes., David Kastrup, 17:18
  • Re: Issue 1786 in lilypond: New engraver for braces, lilypond, 16:12
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 16:07
  • Issue 1786 in lilypond: New engraver for braces, lilypond, 15:42
  • Re: Issue 1567 in lilypond: Add documentation for footnotes, lilypond, 15:35
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 15:09
  • Re: Failing regtests because of footnotes., Graham Percival, 13:50
  • Failing regtests because of footnotes., David Kastrup, 13:40
  • Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display, Graham Percival, 13:37
  • Re: Issue 1765 in lilypond: Clean up regtest mozart-hrn-3, lilypond, 13:36
  • Re: Wrong link on German Home Page, Francisco Vila, 12:29
  • Re: Issue 1765 in lilypond: Clean up regtest mozart-hrn-3, lilypond, 12:19
  • Re: Wrong link on German Home Page, Till Paala, 11:35
  • Re: Issue 1765 in lilypond: Clean up regtest mozart-hrn-3, lilypond, 11:18
  • Re: Issue 732 in lilypond: Alignment problems when vertically stacking horizontally centered stencils., lilypond, 08:41
  • Re: Issue 1744 in lilypond: \once \set behavior should be documented, lilypond, 08:34
  • Re: Issue 153 in lilypond: \once \set fails to restore previous setting, lilypond, 08:29
  • Re: Collision between figures and tie, Bertrand Bordage, 08:28
  • Re: Issue 1111 in lilypond: Allow manual directions on dynamics to break alignment spanner automatically, lilypond, 08:06
  • Re: Issue 1433 in lilypond: \breakDynamicSpan breaks with \break ("bounds of spanner are invalid"), lilypond, 08:01
  • Re: Issue 1259 in lilypond: DynamicTextSpanner #'style = #'none doesn't work over \break, lilypond, 07:57
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 06:54
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 04:45
  • Re: Slurs and PhrasingSlurs with simultaneous start or end, Dmytro O. Redchuk, 04:43
  • Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display, lilypond, 04:41
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 04:37
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 04:31
  • Re: Issue 1572 in lilypond: Enhancement req: Change chord name separator and inversion separator, separately, lilypond, 04:24
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 04:03
  • Re: Issue 1572 in lilypond: Enhancement req: Change chord name separator and inversion separator, separately, lilypond, 03:51
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), lilypond, 03:22
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), lilypond, 03:13
  • Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display, lilypond, 02:58
  • Re: Issue 1785 in lilypond: Compressible space before the first note of a line ?, lilypond, 02:16
  • Re: Issue 1785 in lilypond: Compressible space before the first note of a line ?, lilypond, 02:12
  • Re: Issue 1785 in lilypond: Compressible space before the first note of a line ?, lilypond, 01:39
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 01:35
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 01:31
• July 27, 2011
  • Slurs and PhrasingSlurs with simultaneous start or end, Nick Payne, 23:49
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), lilypond, 22:33
  • Re: Issue 1768 in lilypond: Tremoli can collide with flags in tight spacing situations., lilypond, 21:55
  • Issue 1785 in lilypond: Compressible space before the first note of a line ?, lilypond, 21:49
  • Re: Issue 1779 in lilypond: accidentaled notes too far from the barline, lilypond, 20:58
  • Re: Issue 1779 in lilypond: accidentaled notes too far from the barline, lilypond, 20:44
  • Re: Issue 36 in lilypond: collision cresc and kneed beams -, lilypond, 18:24
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 17:14
  • Re: Issue 36 in lilypond: collision cresc and kneed beams -, lilypond, 16:59
  • Re: Issue 36 in lilypond: collision cresc and kneed beams, lilypond, 16:55
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), lilypond, 16:51
  • Re: Issue 1784 in lilypond: Adds epsilon to Bezier range calculations, lilypond, 16:46
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), lilypond, 16:42
  • Issue 1784 in lilypond: Adds epsilon to Bezier range calculations, lilypond, 16:04
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), lilypond, 15:48
  • Re: Issue 620 in lilypond: It should be possible to specify more specific spanner bounds., lilypond, 15:43
  • Re: Issue 620 in lilypond: It should be possible to specify more specific spanner bounds., lilypond, 15:26
  • Re: Spaces in filenames don't work with -danti-alias-factor option, Phil Holmes, 11:11
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 10:44
  • Re: Issue 36 in lilypond: collision cresc and kneed beams, address@hidden, 06:25
  • Re: Issue 36 in lilypond: collision cresc and kneed beams, lilypond, 06:22
  • RE: some comments do not appear in the tracker page, James Lowe, 06:14
  • Re: Wrong link on German Home Page, Urs Liska, 05:09
  • some comments do not appear in the tracker page, Janek Warchoł, 04:55
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 04:20
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), lilypond, 04:06
  • Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes, lilypond, 02:50
  • Re: Issue 1762 in lilypond: mutual cues fail, lilypond, 02:44
  • Re: Issue 1767 in lilypond: Feta font - change breve vertical lines, lilypond, 00:56
• July 26, 2011
  • Issue 1783 in lilypond: Spaces in filenames don't work with -danti-alias-factor option, lilypond, 22:13
  • Re: Collision between figures and tie, Colin Campbell, 22:11
  • Re: Issue 1656 in lilypond: Broken link on German manuals page, lilypond, 17:55
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 17:19
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, Graham Percival, 17:14
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 17:09
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, Neil Puttock, 16:47
  • Re: Issue 1776 in lilypond: doc: \compoundMeter isn't documented, lilypond, 16:43
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, Graham Percival, 16:34
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond 2.14.x, lilypond, 16:03
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond 2.14.x, lilypond, 15:59
  • Re: Issue 1656 in lilypond: Broken link on German manuals page, lilypond, 15:55
  • Re: Wrong link on German Home Page, Till Paala, 15:31
  • Re: New install problem, Floris van Manen, 14:12
  • Spaces in filenames don't work with -danti-alias-factor option, Chris Snyder, 12:30
  • Re: New install problem, Graham Percival, 12:13
  • Re: New install problem, Floris van Manen, 11:33
  • Re: Issue 1775 in lilypond: doc: add broken- and unbroken slur shaping function, lilypond, 11:13
  • Re: Issue 1775 in lilypond: doc: add broken- and unbroken slur shaping function, lilypond, 10:13
  • Re: Issue 1776 in lilypond: doc: \compoundMeter isn't documented, lilypond, 10:09
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond 2.14.x, lilypond, 10:05
  • Re: Issue 153 in lilypond: \once \set fails to restore previous setting, Colin Campbell, 08:56
  • Collision between figures and tie, Bertrand Bordage, 08:42
  • Re: Issue 1655 in lilypond: Handles longa in MultiMeasureRest, lilypond, 08:17
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond 2.14.x, lilypond, 07:59
  • RE: New install problem, James Lowe, 07:56
  • Re: Issue 153 in lilypond: \once \set fails to restore previous setting, lilypond, 07:51
  • Re: Issue 732 in lilypond: Alignment problems when vertically stacking horizontally centered stencils., lilypond, 06:33
  • Re: Issue 732 in lilypond: Alignment problems when vertically stacking horizontally centered stencils., lilypond, 05:52
  • Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display, lilypond, 04:54
  • Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display, lilypond, 04:50
  • Re: Issue 738 in lilypond: Support for Persian accidentals (koron, sori), lilypond, 04:41
  • Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display, lilypond, 04:37
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 03:48
  • Re: New install problem, Floris van Manen, 03:45
  • Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes, lilypond, 03:34
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 02:35
  • Re: Issue 732 in lilypond: Alignment problems when vertically stacking horizontally centered stencils., lilypond, 01:29
  • Lilypond will not launch under OSX 10.7 Lion, Floris van Manen, 00:37
• July 25, 2011
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), lilypond, 23:58
  • Re: Issue 620 in lilypond: It should be possible to specify more specific spanner bounds., lilypond, 23:51
  • Re: Issue 153 in lilypond: \once \set fails to restore previous setting, lilypond, 23:47
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 23:33
  • Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes, lilypond, 19:50
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, Trevor Daniels, 19:49
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, Carl Sorensen, 18:36
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, Carl Sorensen, 18:28
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, Graham Percival, 18:19
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 17:44
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 16:57
  • Re: Issue 631 in lilypond: Dynamics collide with cross-staff barlines when attached to skips, lilypond, 16:49
  • Re: Issue 621 in lilypond: Dynamics should avoid cross-staff BarLines (e.g. GrandStaff, PianoStaff etc), lilypond, 16:45
  • Re: Issue 1779 in lilypond: accidentaled notes too far from the barline, lilypond, 16:27
  • Re: Issue 1673 in lilypond: patch Allows glissandi to span multiple lines., lilypond, 15:21
  • Re: New install problem, Trevor Bača, 14:20
  • Re: New install problem, Floris van Manen, 11:20
  • Re: New install problem, Trevor Bača, 11:12
  • Issue 1782 in lilypond: avoid-slur should have a setting `best' to avoid huge slurs with key signatures, lilypond, 09:54
  • RE: New install problem, James Lowe, 07:03
  • Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond 2.14.x, lilypond, 07:03
  • Re: New install problem, Floris van Manen, 06:37
  • RE: New install problem, James Lowe, 06:30
  • RE: New install problem, James Lowe, 06:03
  • Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 05:19
  • New install problem, Brian Galliford, 04:55
  • Issue 1779 in lilypond: accidentaled notes too far from the barline, lilypond, 02:20
  • Re: Issue 621 in lilypond: Dynamics should avoid cross-staff BarLines (e.g. GrandStaff, PianoStaff etc), lilypond, 01:55
• July 24, 2011
  • Re: Issue 1776 in lilypond: doc: \compoundMeter isn't documented, lilypond, 19:55
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 19:43
  • Re: Renaissance lute and tab, David Kastrup, 18:37
  • Re: Renaissance lute and tab, Janek Warchoł, 18:36
  • Re: Renaissance lute and tab, Neil Puttock, 18:23
  • Re: Issue 155 in lilypond: \parenthesize does not take accidentals into account, lilypond, 17:36
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 16:19
  • Re: Issue 155 in lilypond: \parenthesize does not take accidentals into account, lilypond, 16:15
  • Re: Renaissance lute and tab, Janek Warchoł, 15:52
  • Re: Issue 1724 -> 620 : workaround?, Xavier Scheuer, 15:46
  • Re: Issue 1730 in lilypond: Documentation for lilypond-windows.exe and -dgui option, lilypond, 14:54
  • Re: Issue 1730 in lilypond: Documentation for lilypond-windows.exe and -dgui option, lilypond, 14:29
  • Re: Issue 1567 in lilypond: Add documentation for footnotes, lilypond, 14:05
  • Re: Issue 868 in lilypond: \parenthesize does not take dotted notes into account, lilypond, 13:54
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), lilypond, 13:02
  • Re: Useless test in parser.yy, Keith OHara, 12:37
  • Re: Issue 307 in lilypond: collision slur with tuplet bracket, lilypond, 12:21
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 12:16
  • Re: Issue 868 in lilypond: \parenthesize does not take dottednotesinto account, Phil Holmes, 11:27
  • Re: Issue 596 in lilypond: collision tuplet number and slur, lilypond, 10:25
  • Re: Issue 307 in lilypond: collision slur with tuplet bracket, lilypond, 10:21
  • Re: Issue 1733 in lilypond: \displayLilyMusic ignores \tweak, Carl Sorensen, 09:58
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), lilypond, 09:44
  • Re: Useless test in parser.yy, Werner LEMBERG, 09:10
  • Re: Useless test in parser.yy, David Kastrup, 08:44
  • Re: Issue 307 in lilypond: collision slur with tuplet bracket, Werner LEMBERG, 08:19
  • RE: Issue 153 in lilypond: \once \set fails to restore previous setting, James Lowe, 07:40
  • RE: Issue 307 in lilypond: collision slur with tuplet bracket, James Lowe, 07:31
  • Re: Issue 868 in lilypond: \parenthesize does not take dotted notesinto account, Trevor Daniels, 07:06
  • Re: Issue 1768 in lilypond: Tremoli can collide with flags in tight spacing situations., lilypond, 07:05
  • Re: Useless test in parser.yy, Phil Holmes, 06:57
  • Re: Issue 1776 in lilypond: doc: \compoundMeter isn't documented, lilypond, 06:53
  • Re: Issue 307 in lilypond: collision slur with tuplet bracket, David Kastrup, 06:49
  • Useless test in parser.yy, David Kastrup, 06:45
  • Re: Issue 1733 in lilypond: \displayLilyMusic ignores \tweak, lilypond, 06:36
  • Re: Issue 307 in lilypond: collision slur with tuplet bracket, address@hidden, 06:34
  • Re: Issue 1744 in lilypond: \once \set behavior should be documented, lilypond, 06:15
  • Re: Issue 1733 in lilypond: \displayLilyMusic ignores \tweak, -Eluze, 06:12
  • Re: Issue 153 in lilypond: \once \set fails to restore previous setting, lilypond, 06:11
  • Re: Issue 1777 in lilypond: adds auto-generated documentation for context modifications, lilypond, 06:07
  • Re: Issue 1214 in lilypond: Cue notes to music that creates a sub-voice does not work, lilypond, 06:03
  • Re: Issue 1733 in lilypond: \displayLilyMusic ignores \tweak, lilypond, 05:59
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), lilypond, 05:55
  • Re: Issue 868 in lilypond: \parenthesize does not take dotted notes into account, lilypond, 05:51
  • Re: Issue 1733 in lilypond: \displayLilyMusic ignores \tweak, lilypond, 05:47
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 05:43
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 05:39
  • Re: Issue 36 in lilypond: collision cresc and kneed beams, lilypond, 05:35
  • Re: Issue 1604 in lilypond: MultiMeasureRest staff position 0 is taken as staff position 2, lilypond, 05:09
  • Re: Issue 1774 in lilypond: Semi-breves unnecessarily shifted, lilypond, 04:59
  • Re: Issue 307 in lilypond: collision slur with tuplet bracket, lilypond, 01:29
• July 23, 2011
  • Re: Issue 1774 in lilypond: Semi-breves unnecessarily shifted, lilypond, 21:07
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, Trevor Daniels, 19:08
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 18:55
  • RE: Issue 1752 in lilypond: redesigning G clef in our Feta font, James Lowe, 18:45
  • Re: \midi plays straight through repeat marks, Neil Puttock, 18:43
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 18:38
  • Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes, lilypond, 18:34
  • Re: Issue 36 in lilypond: collision cresc and kneed beams, lilypond, 18:21
  • Issue 1778 in lilypond: slashedGrace function (graces with slashed stems but no slur, e.g. when grace is tied) needs documenting, lilypond, 18:17
  • Issue 1777 in lilypond: adds auto-generated documentation for context modifications, lilypond, 18:13
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), lilypond, 18:09
  • Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes, lilypond, 17:34
  • Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes, lilypond, 17:14
  • Issue 1776 in lilypond: doc: \compoundMeter isn't documented, lilypond, 17:05
  • Re: Issue 307 in lilypond: collision slur with tuplet bracket, lilypond, 17:00
  • Re: Issue 1724 -> 620 : workaround?, Neil Puttock, 16:28
  • Issue 1775 in lilypond: doc: add broken- and unbroken slur shaping function, lilypond, 16:19
  • Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes, lilypond, 15:59
  • Re: Issue 1214 in lilypond: Cue notes to music that creates a sub-voice does not work, lilypond, 11:27
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 10:42
  • Re: Issue 75 in lilypond: Slurs cannot be nested (including acciaccatura and appoggiatura), lilypond, 09:53
  • Re: Issue 1728 in lilypond: Implements multi-line non-cross staff glissandi, lilypond, 09:49
  • Re: Issue 1769 in lilypond: Doc: Usage 5.5, wrong file name in snippet, lilypond, 09:44
• July 22, 2011
  • Re: Issue 1678 in lilypond: Midi gives false warnings, lilypond, 22:39
  • Re: Issue 1259 in lilypond: DynamicTextSpanner #'style = #'none doesn't work over \break, lilypond, 22:35
  • Re: Issue 1433 in lilypond: \breakDynamicSpan breaks with \break ("bounds of spanner are invalid"), lilypond, 22:31
  • Re: Issue 620 in lilypond: It should be possible to specify more specific spanner bounds., lilypond, 22:13
  • Re: Issue 153 in lilypond: \once \set fails to restore previous setting, lilypond, 22:09
  • Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 18:57
  • Re: Issue 153 in lilypond: \once \set fails to restore previous setting, lilypond, 16:45
  • Re: Issue 1111 in lilypond: Allow manual directions on dynamics to break alignment spanner automatically, lilypond, 16:33
  • Re: Issue 732 in lilypond: Alignment problems when vertically stacking horizontally centered stencils., lilypond, 16:21
  • Re: Issue 1214 in lilypond: Cue notes to music that creates a sub-voice does not work, lilypond, 15:54
  • Re: Issue 732 in lilypond: Alignment problems when vertically stacking horizontally centered stencils., lilypond, 13:29
  • Re: Issue 650 in lilypond: Broken hairpin placed too high after a line break, lilypond, 13:25
  • Re: Mac OS X Lion killed LilyPond, Hans Aberg, 13:21
  • RE: Mac OS X Lion killed LilyPond, James Lowe, 13:18
  • RE: Mac OS X Lion killed LilyPond, James Lowe, 12:54
  • Re: Issue 620 in lilypond: It should be possible to specify more specific spanner bounds., lilypond, 12:16
  • RE: Mac OS X Lion killed LilyPond, James Lowe, 12:13
  • Re: Issue 471 in lilypond: explicitKeySignatureVisibility shouldn't be necessary here, lilypond, 11:19
  • Re: Issue 385 in lilypond: \partcombine with grace notes results in incorrectly combined stems, lilypond, 11:15
  • Re: Issue 1111 in lilypond: Allow manual directions on dynamics to break alignment spanner automatically, lilypond, 10:50
  • Re: Issue 1259 in lilypond: DynamicTextSpanner #'style = #'none doesn't work over \break, lilypond, 10:46
  • Mac OS X Lion killed LilyPond, Frank Tegtmeyer, 10:45
  • Re: Issue 1433 in lilypond: \breakDynamicSpan breaks with \break ("bounds of spanner are invalid"), lilypond, 10:43
  • Re: Issue 1111 in lilypond: Allow manual directions on dynamics to break alignment spanner automatically, lilypond, 10:39
  • Re: Issue 1770 in lilypond: \displayLilyMusic causes error with \oneVoice, lilypond, 08:51
  • Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes, lilypond, 08:32
  • Re: Can’t compile LilyPond, libz.so error, Jan Nieuwenhuizen, 08:11
  • Re: lyrics misaligned when nested in a 2nd lyric line, -Eluze, 08:06
  • Re: Issue 1563 in lilypond: strange vertical line at staff begin using StaffSymbol #'staff-space, lilypond, 08:06
  • Re: Issue 1772 in lilypond: Completion_rest_engraver fails with fractional rests, lilypond, 07:56
  • Can’t compile LilyPond, libz.so error, Ejis, 07:55
  • Re: lyrics misaligned when nested in a 2nd lyric line, Xavier Scheuer, 07:29
  • Re: Issue 1772 in lilypond: Completion_rest_engraver fails with fractional rests, lilypond, 07:24
  • Re: lyrics misaligned when nested in a 2nd lyric line, -Eluze, 07:16
  • Re: Issue 1772 in lilypond: Completion_rest_engraver fails with fractional rests, address@hidden, 06:35
  • Re: Issue 1772 in lilypond: Completion_rest_engraver fails with fractional rests, lilypond, 06:24
  • Re: lyrics misaligned when nested in a 2nd lyric line, Xavier Scheuer, 06:09
  • lyrics misaligned when nested in a 2nd lyric line, -Eluze, 05:59
  • Issue 1774 in lilypond: Semi-breves incorrectly shifted, lilypond, 05:05
  • Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 04:13
  • Re: Issue 1762 in lilypond: mutual cues fail, lilypond, 04:09
  • Re: Issue 1769 in lilypond: Doc: Usage 5.5, wrong file name in snippet, lilypond, 04:05
  • Re: Issue 1757 in lilypond: Footnotes cannot attach to \header { }, (some?) TrypeScripts and MMRs, lilypond, 04:01
  • Re: Issue 1773 in lilypond: Add Footnote_engraver to Staff context, address@hidden, 04:00
  • Issue 1773 in lilypond: Add Footnote_engraver to Staff context, lilypond, 03:57
• July 21, 2011
  • Re: Issue 1214 in lilypond: Cue notes to music that creates a sub-voice does not work, lilypond, 14:33
  • Re: [Jan Nieuwenhuizen] Cron 404 report, Graham Percival, 14:07
  • Re: Issue 1678 in lilypond: Midi gives false warnings, lilypond, 14:02
  • Re: Issue 1678 in lilypond: Midi gives false warnings, lilypond, 13:57
  • Re: Issue 1507 in lilypond: weird linebreaks in song output, lilypond, 13:44
  • Re: Completion_rest_engraver fails with fractional rests, Neil Puttock, 13:10
  • Re: Issue 665 in lilypond: Request: MusicXML backend, lilypond, 08:07
  • Re: Completion_rest_engraver fails with fractional rests, Dmytro O. Redchuk, 07:57
  • Issue 1772 in lilypond: Completion_rest_engraver fails with fractional rests, lilypond, 07:56
  • Re: Completion_rest_engraver fails with fractional rests, address@hidden, 07:43
  • Re: Completion_rest_engraver fails with fractional rests, Dmytro O. Redchuk, 07:37
  • Completion_rest_engraver fails with fractional rests, address@hidden, 07:20
  • Re: Issue 620 in lilypond: It should be possible to specify more specific spanner bounds., lilypond, 06:41
  • Re: Issue 1567 in lilypond: Add documentation for footnotes, lilypond, 06:22
  • Re: Issue 34 in lilypond: Grace synchronization, lilypond, 05:11
  • Re: Issue 34 in lilypond: Grace synchronization, lilypond, 05:05
  • Re: [Jan Nieuwenhuizen] Cron 404 report, Francisco Vila, 03:34
  • [Jan Nieuwenhuizen] Cron 404 report, Jan Nieuwenhuizen, 03:29
  • Re: Issue 1770 in lilypond: \displayLilyMusic causes error with \oneVoice, lilypond, 02:59
  • Re: Issue 34 in lilypond: Grace synchronization, lilypond, 02:05
  • Re: Issue 1770 in lilypond: \displayLilyMusic causes error with \oneVoice, lilypond, 01:54
  • Re: Issue 1744 in lilypond: \once \set behavior should be documented, lilypond, 01:53
  • Re: Issue 1491 in lilypond: git-cl hangs when uploading patches due to bad mime-type, lilypond, 01:21
• July 20, 2011
  • Re: Issue 1770 in lilypond: \displayLilyMusic causes error with \oneVoice, lilypond, 22:47
  • Re: Issue 1767 in lilypond: Feta font - change breve vertical lines, lilypond, 22:47
  • Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes, lilypond, 22:47
  • Re: Issue 1693 in lilypond: Attaches bound info to beam for better normalized-endpoint calculations, lilypond, 22:47
  • Re: Issue 1727 in lilypond: Adds glissando stems to lilypond, lilypond, 22:47
  • Re: Issue 1688 in lilypond: New half-closed hihat symbol for drum mode, lilypond, 22:47
  • Re: Issue 1673 in lilypond: patch Allows glissandi to span multiple lines., lilypond, 22:46
  • Re: Issue 1507 in lilypond: weird linebreaks in song output, lilypond, 22:46
  • Re: Issue 1567 in lilypond: Add documentation for footnotes, lilypond, 22:46
  • Re: Issue 34 in lilypond: Grace synchronization, Keith OHara, 18:11
  • Re: Issue 1259 in lilypond: DynamicTextSpanner #'style = #'none doesn't work over \break, lilypond, 17:27
  • Re: Issue 1744 in lilypond: \once \set behavior should be documented, lilypond, 17:17
  • Re: Issue 1259 in lilypond: DynamicTextSpanner #'style = #'none doesn't work over \break, lilypond, 17:13
  • Re: Issue 1433 in lilypond: \breakDynamicSpan breaks with \break ("bounds of spanner are invalid"), lilypond, 17:09
  • Re: Issue 1768 in lilypond: Tremoli can collide with flags in tight spacing situations., lilypond, 17:04
  • Re: Issue 1433 in lilypond: \breakDynamicSpan breaks with \break ("bounds of spanner are invalid"), lilypond, 16:17
  • Re: Issue 1259 in lilypond: DynamicTextSpanner #'style = #'none doesn't work over \break, lilypond, 16:13
  • Re: Issue 1705 in lilypond: New breve rest with ledger lines, lilypond, 15:54
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 15:42
  • Re: Issue 1728 in lilypond: Implements multi-line non-cross staff glissandi, lilypond, 15:36
  • Re: Issue 1390 in lilypond: Tied acciaccaturas should not be printed with a slur, lilypond, 14:19
  • Re: Issue 153 in lilypond: \once \set fails to restore previous setting, lilypond, 13:11
  • Re: Issue 1744 in lilypond: \once \set behavior should be documented, lilypond, 13:07
  • Issue 1771 in lilypond: Nested reverts fail for properties which aren't set as defaults in define-grobs.scm, lilypond, 12:52
  • Re: Issue 1695 in lilypond: Clef change placed outside score, lilypond, 12:38
  • Re: Issue 1695 in lilypond: Clef change placed outside score, lilypond, 12:34
  • Re: Issue 1770 in lilypond: \displayLilyMusic causes error with \oneVoice, lilypond, 12:30
  • Re: Issue 1762 in lilypond: mutual cues fail, lilypond, 11:37
  • Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes, lilypond, 10:55
  • Re: Issue 1695 in lilypond: Clef change placed outside score, lilypond, 10:54
  • Re: Issue 1724 -> 620 : workaround?, Neil Puttock, 10:27
  • Re: Issue 868 in lilypond: \parenthesize does not take dotted notes into account, lilypond, 09:22
  • Re: Issue 155 in lilypond: \parenthesize does not take accidentals into account, lilypond, 09:18
  • Re: Issue 34 in lilypond: Grace synchronization, lilypond, 09:14
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 09:10
  • Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly, lilypond, 08:49
  • Re: Issue 1744 in lilypond: \once \set behavior should be documented, lilypond, 08:31
  • Issue 1724 -> 620 : workaround?, Xavier Scheuer, 08:28
  • Re: Issue 896 in lilypond: When used after \tag, \partcombine may fail to print notes, lilypond, 08:27
  • Re: Issue 1770 in lilypond: \displayLilyMusic causes error with \oneVoice, lilypond, 08:22
  • Re: Issue 1725 in lilypond: DynamicTextSpanner collides with DynamicText, lilypond, 08:16
  • Re: Issue 1770 in lilypond: \displayLilyMusic causes error with \oneVoice, lilypond, 08:12
  • Re: Issue 1770 in lilypond: \displayLilyMusic causes error with \oneVoice, lilypond, 08:08
• July 19, 2011
  • Re: Issue 1767 in lilypond: Feta font - change breve vertical lines, Werner LEMBERG, 23:56
  • Re: \displayLilyMusic causes error with \oneVoice, Colin Campbell, 20:10
  • Issue 1770 in lilypond: \displayLilyMusic causes error with \oneVoice, lilypond, 20:10
  • Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes, lilypond, 17:39
  • Re: Issue 1767 in lilypond: Feta font - change breve vertical lines, lilypond, 17:35
  • Re: Wrong link on German Home Page, Francisco Vila, 17:33
  • RE: Wrong link on German Home Page, James Lowe, 17:16
  • Re: Issue 1767 in lilypond: Feta font - change breve vertical lines, lilypond, 17:08
  • Re: Issue 1768 in lilypond: Tremoli can collide with flags in tight spacing situations., lilypond, 17:03
  • Re: Issue 1767 in lilypond: Feta font - change breve vertical lines, lilypond, 16:46
  • Re: Issue 1767 in lilypond: Feta font - change breve vertical lines, lilypond, 16:37
  • Re: Issue 1767 in lilypond: Feta font - change breve vertical lines, lilypond, 16:32
  • Re: Issue 1767 in lilypond: Feta font - change breve vertical lines, lilypond, 16:17
  • Re: Issue 1767 in lilypond: Feta font - change breve vertical lines, lilypond, 16:09
  • Re: Issue 1767 in lilypond: Feta font - change breve vertical lines, lilypond, 15:48
  • lyrics with musical intro?, Jan Nieuwenhuizen, 15:10
  • Re: Issue 1767 in lilypond: Feta font - change breve vertical lines, lilypond, 14:50
  • \displayLilyMusic causes error with \oneVoice, Toine Schreurs, 13:10
  • png output with transparency and the option to have the rendering cropped to the score, Bart Deruyter, 11:45
  • Re: Issue 1769 in lilypond: Doc: Usage 5.5, wrong file name in snippet, lilypond, 10:55
  • Re: Issue 1301 in lilypond: Strange collision of note and clef, lilypond, 10:19
  • Re: Issue 1678 in lilypond: Midi gives false warnings, lilypond, 09:01
  • Re: Issue 1563 in lilypond: strange vertical line at staff begin using StaffSymbol #'staff-space, lilypond, 08:57
  • Re: Issue 1767 in lilypond: Feta font - change breve vertical lines, lilypond, 08:09
• July 18, 2011
  • Re: Issue 1720 in lilypond: Incorrect tuplet bracket direction calculation when tuplets contain rests., lilypond, 21:48
  • Re: Issue 1734 in lilypond: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } }, lilypond, 19:42
  • Re: Issue 1768 in lilypond: Tremoli can collide with flags in tight spacing situations., lilypond, 16:01
  • Re: Issue 1768 in lilypond: Tremoli can collide with flags in tight spacing situations., lilypond, 13:19
  • Re: Issue 1768 in lilypond: Tremoli can collide with flags in tight spacing situations., lilypond, 12:13
  • Re: Issue 1349 in lilypond: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used., lilypond, 08:48
  • Wrong link on German Home Page, Urs Liska, 05:55
  • Re: Ties colliding in single-staff polyphony, Dmytro O. Redchuk, 05:09
  • Re: Ties colliding in single-staff polyphony, David Kastrup, 05:09
  • Re: Ties colliding in single-staff polyphony, David Kastrup, 05:01
  • Re: Ties colliding in single-staff polyphony, Bertrand Bordage, 05:01
  • Re: Ties colliding in single-staff polyphony, Dmytro O. Redchuk, 04:39
  • Re: Ties colliding in single-staff polyphony, Dmytro O. Redchuk, 04:34
  • Re: Ties colliding in single-staff polyphony, address@hidden, 04:20
  • Re: Issue 1769 in lilypond: Doc:, lilypond, 04:14
  • Ties colliding in single-staff polyphony, Bertrand Bordage, 04:14
  • Issue 1769 in lilypond: Doc:, lilypond, 04:09
  • Re: Issue 1711 in lilypond: Pitch bend tuning adjustments, lilypond, 04:07
  • Re: Issue 621 in lilypond: Dynamics should avoidcross-staff BarLines(e.g. GrandStaff, PianoStaff etc), Trevor Daniels, 04:05
  • Re: Issue 1766 in lilypond: Checks for grobs with circular parentage in the regtests, lilypond, 04:05
  • Re: Issue 1739 in lilypond: doc: correcting note about rerunning regtests, lilypond, 04:01
  • Re: Doc: Usage 5.5, wrong file name in snippet, Dmytro O. Redchuk, 03:58
  • Re: Issue 1709 in lilypond: Add feta-flags to build system, lilypond, 03:53
  • Re: Doc: Usage 5.5, wrong file name in snippet, David Kastrup, 03:49
  • Re: Issue 1736 in lilypond: clarify description of minimal examples, lilypond, 03:49
  • Re: Issue 1761 in lilypond: cue notes clash with main voice, lilypond, 03:45
  • Re: Issue 1763 in lilypond: OttavaBracket doesn't follow fontSize, lilypond, 03:41
  • Re: Issue 1764 in lilypond: \displayLilyMusic causes error with \addFingering from LSR 768, lilypond, 03:37
  • Re: Doc: Usage 5.5, wrong file name in snippet, David Kastrup, 03:26
  • Issue 1768 in lilypond: Tremoli can collide with flags in tight spacing situations., lilypond, 02:56
  • Re: Issue 1766 in lilypond: Checks for grobs with circular parentage in the regtests, lilypond, 02:45
  • Re: Issue 621 in lilypond: Dynamics should avoid cross-staff BarLines(e.g. GrandStaff, PianoStaff etc), Keith OHara, 02:41
• July 17, 2011
  • Re: Issue 1760 in lilypond: \RemoveEmptyStaves only works inside a \layout block, lilypond, 18:02
  • Doc: Usage 5.5, wrong file name in snippet, Federico Bruni, 17:36
  • Issue 1767 in lilypond: Feta font - change breve vertical lines, lilypond, 06:22
  • Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes, lilypond, 03:26
  • Re: Issue 1764 in lilypond: \displayLilyMusic causes error with \addFingering from LSR 768, -Eluze, 02:43
• July 16, 2011
  • Re: Issue 1567 in lilypond: Add documentation for footnotes, lilypond, 16:26
  • Re: Issue 621 in lilypond: Dynamics should avoid cross-staff BarLines (e.g. GrandStaff, PianoStaff etc), lilypond, 13:01
  • Re: Issue 1766 in lilypond: Checks for grobs with circular parentage in the regtests, lilypond, 11:38
  • Re: Issue 1678 in lilypond: Midi gives false warnings, lilypond, 11:11
  • Re: Issue 1766 in lilypond: Checks for grobs with circular parentage in the regtests, lilypond, 10:23
  • Re: Partcombine: full bar rests, Jean-Charles Malahieude, 07:19
  • Re: Eighth rest position dependent on other voice., Phil Holmes, 06:14
  • Re: musicxml2ly.py conversion errors (two), Reinhold Kainhofer, 06:09
  • Re: musicxml2ly.py conversion errors (two), Phil Holmes, 05:52
  • Eighth rest position dependent on other voice., Richard Giraud, 05:25
  • Re: Issue 621 in lilypond: Dynamics should avoid cross-staff BarLines (e.g. GrandStaff, PianoStaff etc), lilypond, 04:43
  • Re: Issue 621 in lilypond: Dynamics should avoid cross-staff BarLines(e.g. GrandStaff, PianoStaff etc), Trevor Daniels, 04:21
• July 15, 2011
  • Re: Issue 621 in lilypond: Dynamics should avoid cross-staff BarLines (e.g. GrandStaff, PianoStaff etc), lilypond, 23:15
  • Re: Issue 1725 in lilypond: DynamicTextSpanner collides with DynamicText, lilypond, 23:08
  • Re: Issue 1720 in lilypond: Incorrect tuplet bracket direction calculation when tuplets contain rests., lilypond, 22:54
  • Re: Issue 1695 in lilypond: Clef change placed outside score, lilypond, 22:50
  • Re: Issue 1507 in lilypond: weird linebreaks in song output, lilypond, 22:46
  • Re: Issue 1563 in lilypond: strange vertical line at staff begin using StaffSymbol #'staff-space, lilypond, 22:42
  • Re: Issue 1728 in lilypond: Implements multi-line non-cross staff glissandi, lilypond, 22:38
  • Re: Issue 1705 in lilypond: New breve rest with ledger lines, lilypond, 22:34
  • Re: Issue 1734 in lilypond: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } }, lilypond, 22:10
  • Re: Issue 1760 in lilypond: \RemoveEmptyStaves only works inside a \layout block, lilypond, 22:06
  • Re: Issue 1390 in lilypond: Tied acciaccaturas should not be printed with a slur, lilypond, 22:02
  • Re: Partcombine: full bar rests, Colin Campbell, 21:42
  • Re: Issue 1678 in lilypond: Midi gives false warnings, lilypond, 20:23
  • musicxml2ly.py conversion errors (two), Ken Kellogg-Smith, 19:31
  • Re: Issue 1764 in lilypond: \displayLilyMusic causes error with \addFingering from LSR 768, Neil Puttock, 18:09
  • Re: Issue 1766 in lilypond: Checks for grobs with circular parentage in the regtests, lilypond, 17:42
  • Issue 1766 in lilypond: Checks for grobs with circular parentage in the regtests, lilypond, 17:39
  • Issue 1765 in lilypond: Clean up regtest mozart-hrn-3, lilypond, 13:51
  • Re: 2.14.2, Phil Holmes, 09:25
  • Re: Issue 1762 in lilypond: mutual cues fail, lilypond, 05:26
  • Re: Partcombine: full bar rests, Reinhold Kainhofer, 05:22
  • Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly, lilypond, 04:41
  • Re: Issue 1739 in lilypond: doc: correcting note about rerunning regtests, lilypond, 03:00
  • Re: Issue 1736 in lilypond: clarify description of minimal examples, lilypond, 02:56
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 02:50
• July 14, 2011
  • Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly, lilypond, 20:02
  • Re: Issue 1764 in lilypond: \displayLilyMusic causes error with \addFingering from LSR 768, -Eluze, 17:26
  • Re: Issue 1688 in lilypond: New half-closed hihat symbol for drum mode, lilypond, 16:36
  • Re: Issue 1761 in lilypond: cue notes clash with main voice, lilypond, 16:26
  • Re: Issue 1761 in lilypond: cue notes clash with main voice, lilypond, 15:56
  • Re: Issue 1763 in lilypond: OttavaBracket doesn't follow fontSize, lilypond, 15:52
  • Re: Issue 930 in lilypond: Collision: differently-sized noteheads in a polyphonic situation, lilypond, 14:35
  • Re: Issue 1761 in lilypond: cue notes clash with main voice, lilypond, 14:31
  • Re: Issue 930 in lilypond: Collision: differently-sized noteheads in a polyphonic situation, lilypond, 14:27
  • Re: Issue 1763 in lilypond: OttavaBracket doesn't follow fontSize, lilypond, 14:19
  • Partcombine: full bar rests, Jean-Charles Malahieude, 14:15
  • Re: Issue 1764 in lilypond: \displayLilyMusic causes error with \addFingering from LSR 768, lilypond, 14:09
  • Re: Issue 1721 in lilypond: Doc: translated docs should use @rlsrnamed instead of @rlsr, lilypond, 12:33
  • Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly, lilypond, 11:37
  • Re: \displayLilyMusic causes error with \addFingering from LSR 768, Dmytro O. Redchuk, 11:21
  • Issue 1764 in lilypond: \displayLilyMusic causes error with \addFingering from LSR 768, lilypond, 11:21
  • Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly, lilypond, 11:16
  • Re: 2.14.2, Dmytro O. Redchuk, 11:07
  • \displayLilyMusic causes error with \addFingering from LSR 768, -Eluze, 10:58
  • Re: 2.14.2, Graham Percival, 10:46
  • Re: Issue 1721 in lilypond: Doc: translated docs should use @rlsrnamed instead of @rlsr, lilypond, 10:39
  • Re: 2.14.2, Urs Liska, 10:30
  • Re: Issue 1757 in lilypond: Footnotes cannot attach to many layout objects/grobs, lilypond, 10:25
  • Re: Issue 1743 in lilypond: lilypond-2.15.4-1.mingw.exe does not install PATH on Windows 7 SP1, lilypond, 10:21
  • Re: 2.14.2, Graham Percival, 10:19
  • Re: Issue 1715 in lilypond: Ligature and ambitus cause segfault, lilypond, 09:17
  • Re: 2.14.2, Urs Liska, 09:15
  • Re: Issue 1750 in lilypond: Documentation suggestion: transposition resulting in triple accidentals, lilypond, 09:13
  • Re: 2.14.2, Carl Sorensen, 08:54
  • Issue 1763 in lilypond: OttavaBracket doesn't follow fontSize, lilypond, 08:45
  • Re: Issue 1761 in lilypond: cue notes clash with main voice, lilypond, 08:41
  • Re: Issue 1762 in lilypond: mutual cues fail, lilypond, 08:37
  • Issue 1762 in lilypond: mutual cues fail, lilypond, 08:33
  • 2.14.2, Urs Liska, 08:23
  • Issue 1761 in lilypond: cue notes clash with main voice, lilypond, 08:13
  • Re: Issue 1715 in lilypond: Ligature and ambitus cause segfault, lilypond, 08:08
  • Re: Issue 1750 in lilypond: Documentation suggestion: transposition resulting in triple accidentals, lilypond, 08:02
  • Re: Issue 75 in lilypond: Slurs cannot be nested (including acciaccatura and appoggiatura), Urs Liska, 07:20
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 07:09
  • Re: Issue 1710 in lilypond: rearrange flag definitions in feta-flags.mf, lilypond, 04:10
  • Re: Issue 1748 in lilypond: Defect in glissando handling, lilypond, 04:05
  • Re: Issue 75 in lilypond: Slurs cannot be nested (including acciaccatura and appoggiatura), Dmytro O. Redchuk, 04:05
  • Re: Issue 298 in lilypond: Ties do not appear when shortened because of an accidental, lilypond, 04:01
  • Re: Issue 1748 in lilypond: Defect in glissando handling, lilypond, 03:57
  • Re: Issue 840 in lilypond: broken ties too short when time signature changes, lilypond, 03:54
  • Re: Issue 1219 in lilypond: Broken tie may become a too small dot, lilypond, 03:49
  • Re: Issue 1758 in lilypond: layout-set-staff-size doesn't work properly, lilypond, 03:45
  • Re: Issue 1759 in lilypond: hairpin aligns to lyrics instead of notes, lilypond, 03:41
  • Re: Issue 1736 in lilypond: clarify description of minimal examples, lilypond, 00:12
  • Re: Issue 1739 in lilypond: doc: correcting note about rerunning regtests, lilypond, 00:08
• July 13, 2011
  • Re: Issue 1688 in lilypond: New half-closed hihat symbol for drum mode, lilypond, 21:45
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, Trevor Daniels, 18:12
  • Re: Issue 1757 in lilypond: Footnotes cannot attach to many layout objects/grobs, lilypond, 16:21
  • Re: Issue 1757 in lilypond: Footnotes cannot attach to many layout objects/grobs, lilypond, 16:17
  • Re: Issue 1757 in lilypond: Footnotes cannot attach to many layout objects/grobs, lilypond, 16:13
  • Re: Issue 1750 in lilypond: Documentation suggestion: transposition resulting in triple accidentals, lilypond, 15:19
  • Re: Issue 1715 in lilypond: Ligature and ambitus cause segfault, lilypond, 15:15
  • Re: Issue 1715 in lilypond: Ligature and ambitus cause segfault, lilypond, 15:10
  • Re: Issue 1676 in lilypond: Tremolo with change staff produces false dotted note, lilypond, 15:06
  • Re: Issue 1581 in lilypond: Pitched trill between tied notes causes `unterminated tie' warning, lilypond, 15:02
  • Re: Issue 1256 in lilypond: Extra SlurEvent modifies extents of broken slurs, lilypond, 14:59
  • Re: Issue 75 in lilypond: Slurs cannot be nested (including acciaccatura and appoggiatura), lilypond, 14:54
  • Re: Issue 1755 in lilypond: Add Baroque ornaments, lilypond, 14:50
  • Re: Issue 1256 in lilypond: Extra SlurEvent modifies extents of broken slurs, lilypond, 14:37
  • Re: Issue 1755 in lilypond: Add Baroque ornaments, lilypond, 13:49
  • Re: Issue 770 in lilypond: Lyrics behave differently when associated to a Voice-derived context, lilypond, 13:43
  • Re: Issue 750 in lilypond: Misleading warning when a Lyrics context is empty, lilypond, 13:39
  • Re: Issue 75 in lilypond: Slurs cannot be nested (including acciaccatura and appoggiatura), lilypond, 13:35
  • Re: how to change gap between beams?, Carl Sorensen, 13:08
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, Graham Percival, 13:06
  • Re: Issue 1760 in lilypond: \RemoveEmptyStaves only works inside a \layout block, Reinhold Kainhofer, 12:58
  • Re: Issue 1759 in lilypond: hairpin aligns to lyrics instead of notes, lilypond, 12:49
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, Trevor Daniels, 12:17
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 12:16
  • Re: Issue 1494 in lilypond: including alternate fonts, lilypond, 11:02
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 10:52
  • Re: how to change gap between beams?, Janek Warchoł, 08:49
  • Re: Issues regarding too-short-tie, Urs Liska, 07:22
  • Re: Manual beams confuse lyrics positioning when autoBeam is off, Urs Liska, 07:09
  • Re: Issue 1760 in lilypond: \RemoveEmptyStaves only works inside a \layout block, David Kastrup, 04:56
  • Re: Issue 298 in lilypond: Ties do not appear when shortened because of an accidental, lilypond, 01:18
  • Re: Issue 298 in lilypond: Ties do not appear when shortened because of an accidental, lilypond, 00:23
  • Re: Issue 1219 in lilypond: Broken tie may become a too small dot, lilypond, 00:22
  • Re: Issue 840 in lilypond: broken ties too short when time signature changes, lilypond, 00:19
• July 12, 2011
  • Re: Issue 1563 in lilypond: strange vertical line at staff begin using StaffSymbol #'staff-space, lilypond, 19:40
  • Re: Issue 1695 in lilypond: Clef change placed outside score, lilypond, 18:32
  • Issue 1760 in lilypond: \RemoveEmptyStaves only works inside a \layout block, lilypond, 18:27
  • Re: Issue 1507 in lilypond: weird linebreaks in song output, lilypond, 17:41
  • Re: Issue 1759 in lilypond: hairpin aligns to lyrics instead of notes, lilypond, 17:28
  • Re: Issue 1759 in lilypond: hairpin aligns to lyrics instead of notes, lilypond, 17:21
  • Re: Manual beams confuse lyrics positioning when autoBeam is off, Neil Puttock, 17:21
  • Re: Issue 620 in lilypond: It should be possible to specify more specific spanner bounds., lilypond, 17:17
  • Re: startpoint of decrescendo hairpins, Neil Puttock, 17:16
  • Manual beams confuse lyrics positioning when autoBeam is off, BognárBálint, 17:00
  • Re: startpoint of decrescendo hairpins, Janek Warchoł, 16:52
  • Issue 1759 in lilypond: hairpin aligns to lyrics instead of notes, lilypond, 16:51
  • Re: Issue 1758 in lilypond: layout-set-staff-size doesn't work properly, lilypond, 15:08
  • Re: Issue 1758 in lilypond: layout-set-staff-size doesn't work properly, lilypond, 14:38
  • Re: Issue 216 in lilypond: Enhancement: the ability to change staff line spacing inside a \layout{} block, lilypond, 14:34
  • Re: Issue 1581 in lilypond: Pitched trill between tied notes causes `unterminated tie' warning, lilypond, 13:48
  • Re: Issue 1581 in lilypond: Pitched trill between tied notes causes `unterminated tie' warning, lilypond, 13:44
  • Re: Issue 75 in lilypond: Slurs cannot be nested (including acciaccatura and appoggiatura), lilypond, 13:40
  • Re: Issue 1256 in lilypond: Extra SlurEvent modifies extents of broken slurs, lilypond, 13:36
  • Re: Issue 1676 in lilypond: Tremolo with change staff produces false dotted note, lilypond, 13:25
  • Re: Issue 750 in lilypond: Misleading warning when a Lyrics context is empty, lilypond, 13:21
  • Re: Issues regarding too-short-tie, Derek Klinge, 13:14
  • Issue 1758 in lilypond: layout-set-staff-size doesn't work properly, lilypond, 11:50
  • Re: Issue 1234 in lilypond: Fill-line should not use word space, but should use springs-and-rods, lilypond, 11:03
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 10:28
  • Issues regarding too-short-tie, Dmytro O. Redchuk, 10:17
  • Re: Issue 409 in lilypond: collision tie and time signature, lilypond, 10:06
  • Re: Issue 592 in lilypond: Regression: Tie direction reverse incorrectly on a middle-staff note, lilypond, 09:54
  • Re: Issue 1705 in lilypond: New breve rest with ledger lines, lilypond, 08:40
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 05:06
  • Re: Issue 1234 in lilypond: Fill-line should not use word space, but should use springs-and-rods, lilypond, 03:03
  • Re: Issue 1234 in lilypond: Fill-line should not use word space, but should use springs-and-rods, lilypond, 02:47
• July 11, 2011
  • Re: Issue 1705 in lilypond: New breve rest with ledger lines, lilypond, 22:42
  • Re: Issue 737 in lilypond: Enhancement: support for footnotes and/or endnotes., lilypond, 22:30
  • Re: Issue 814 in lilypond: warning-as-error should be enabled when compiling the regtests, lilypond, 22:22
  • Re: Issue 814 in lilypond: warning-as-error should be enabled when compiling the regtests, lilypond, 22:04
  • Re: Issue 1398 in lilypond: Hairpin following a text crescendo starts too late, lilypond, 21:55
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 20:57
  • Re: Issue 1581 in lilypond: Pitched trill between tied notes causes `unterminated tie' warning, lilypond, 17:33
  • Re: Issue 1390 in lilypond: Tied acciaccaturas should not be printed with a slur, lilypond, 17:17
  • Re: Issue 1676 in lilypond: Tremolo with change staff produces false dotted note, lilypond, 17:10
  • Re: Issue 1750 in lilypond: Documentation suggestion: transposition resulting in triple accidentals, lilypond, 16:43
  • Re: Issue 1711 in lilypond: Pitch bend tuning adjustments, lilypond, 16:39
  • Re: Issue 1234 in lilypond: Fill-line should not use word space, but should use springs-and-rods, lilypond, 15:12
  • Re: Issue 1234 in lilypond: Fill-line should not use word space, but should use springs-and-rods, lilypond, 15:08
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 14:35
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 12:38
  • Re: Issue 1216 in lilypond: DynamicTextSpanners should end like hairpins, lilypond, 12:31
  • Re: Issue 1398 in lilypond: Hairpin following a text crescendo starts too late, lilypond, 12:27
  • Re: Issue 1216 in lilypond: DynamicTextSpanners should end like hairpins, lilypond, 12:23
  • Re: Issue 333 in lilypond: lyrics delayed by one note with \partial and \override VerticalAxisGroup, lilypond, 12:19
  • Re: Issue 1563 in lilypond: strange vertical line at staff begin using StaffSymbol #'staff-space, lilypond, 12:10
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 11:31
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 10:58
  • Re: Issue 1563 in lilypond: strange vertical line at staff begin using StaffSymbol #'staff-space, lilypond, 10:54
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 10:50
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 10:45
  • Re: Issue 1750 in lilypond: Documentation suggestion: transposition resulting in triple accidentals, lilypond, 10:01
  • Re: Issue 1750 in lilypond: Documentation suggestion: transposition resulting in triple accidentals, lilypond, 09:57
  • Re: Issue 1234 in lilypond: Fill-line should not use word space, but should use springs-and-rods, lilypond, 09:22
  • Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes, lilypond, 09:18
  • Re: Issue 1234 in lilypond: Fill-line should not use word space, but should use springs-and-rods, lilypond, 09:14
  • Re: Issue 734 in lilypond: tremolos beams placement on a (single) whole note, lilypond, 09:10
  • Re: Issue 1234 in lilypond: Fill-line should not use word space, but should use springs-and-rods, lilypond, 08:58
  • Re: Issue 1234 in lilypond: Fill-line should not use word space, but should use springs-and-rods, lilypond, 08:54
  • Re: Issue 1234 in lilypond: Fill-line should not use word space, but should use springs-and-rods, lilypond, 08:50
  • Re: Issue 1256 in lilypond: Extra SlurEvent modifies extents of broken slurs, lilypond, 08:36
  • Re: Issue 1750 in lilypond: Documentation suggestion: transposition resulting in triple accidentals, lilypond, 08:32
  • Re: Issue 1756 in lilypond: architecture diagram image is missing, lilypond, 08:28
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 08:23
  • Issue 1757 in lilypond: Footnotes cannot attach to many layout objects/grobs, lilypond, 07:44
  • Re: Issue 1734 in lilypond: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } }, lilypond, 07:38
  • Re: Issue 1710 in lilypond: rearrange flag definitions in feta-flags.mf, lilypond, 04:39
  • Re: Issue 1710 in lilypond: rearrange flag definitions in feta-flags.mf, lilypond, 04:34
  • Re: Issue 1710 in lilypond: rearrange flag definitions in feta-flags.mf, lilypond, 04:29
  • Re: Issue 1710 in lilypond: rearrange flag definitions in feta-flags.mf, lilypond, 04:25
  • Re: Issue 1714 in lilypond: Build error regarding mf2pt1 with latest texlive (2011) and lilypond, lilypond, 04:21
  • Re: Issue 1756 in lilypond: architecture diagram image is missing, lilypond, 02:44
  • Re: Issue 1014 in lilypond: Full/multi measure rests should be semibreve (for any but 4/2), lilypond, 02:40
• July 10, 2011
  • Re: Issue 1751 in lilypond: Most analysis brackets get incorrect event-cause info, breaking point-and-click & \tweak, lilypond, 19:02
  • Re: Issue 1014 in lilypond: Full/multi measure rests should be semibreve (for any but 4/2), lilypond, 18:57
  • Re: Issue 1482 in lilypond: \caps and \smallCaps don't work with \fromproperty, lilypond, 18:47
  • Re: Issue 1482 in lilypond: \caps and \smallCaps don't work with \fromproperty, lilypond, 18:32
  • Re: Issue 1751 in lilypond: Most analysis brackets get incorrect event-cause info, breaking point-and-click & \tweak, lilypond, 18:02
  • Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes, lilypond, 17:54
  • Issue 1756 in lilypond: architecture diagram image is missing, lilypond, 17:39
  • Re: Issue 1482 in lilypond: \caps and \smallCaps don't work with \fromproperty, lilypond, 17:28
  • Re: Issue 1676 in lilypond: Tremolo with change staff produces false dotted note, lilypond, 17:15
  • Re: Issue 770 in lilypond: Lyrics behave differently when associated to a Voice-derived context, lilypond, 16:52
  • Re: Issue 1390 in lilypond: Tied acciaccaturas should not be printed with a slur, lilypond, 16:43
  • Re: Issue 1581 in lilypond: Pitched trill between tied notes causes `unterminated tie' warning, lilypond, 16:37
  • Re: Issue 1581 in lilypond: Pitched trill between tied notes causes `unterminated tie' warning, lilypond, 16:33
  • Re: Issue 1482 in lilypond: \caps and \smallCaps don't work with \fromproperty, Colin Campbell, 14:41
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 06:50
  • Re: how to create baroque ornaments, Phil Holmes, 06:33
  • Issue 1755 in lilypond: Add Baroque ornaments, lilypond, 06:33
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 06:27
  • Re: Issue 1754 in lilypond: bug when slur incorporate acciaccatura, lilypond, 06:21
  • Re: midi2ly fails on OSX 10.6.8, Hans Aberg, 04:58
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 04:39
• July 09, 2011
  • Re: Issue 1739 in lilypond: doc: correcting note about rerunning regtests, lilypond, 22:23
  • Re: Issue 1715 in lilypond: Ligature and ambitus cause segfault, lilypond, 22:19
  • Re: Issue 1715 in lilypond: Ligature and ambitus cause segfault, lilypond, 22:15
  • Re: Issue 1664 in lilypond: Add link to LSR on web site, lilypond, 22:11
  • Re: Issue 1693 in lilypond: Attaches bound info to beam for better normalized-endpoint calculations, lilypond, 22:01
  • Re: Issue 1482 in lilypond: \caps and \smallCaps don't work with \fromproperty, lilypond, 19:31
  • Re: Issue 1482 in lilypond: \caps and \smallCaps don't work with \fromproperty, lilypond, 19:27
  • Re: Issue 1754 in lilypond: bug when slur incorporate acciaccatura, lilypond, 18:34
  • Re: Issue 75 in lilypond: Slurs cannot be nested (including acciaccatura and appoggiatura), lilypond, 18:30
  • Re: midi2ly fails on OSX 10.6.8, Hans Aberg, 18:20
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 17:53
  • Re: Issue 1709 in lilypond: Add feta-flags to build system, lilypond, 17:06
  • Re: bug when slur incorporates acciaccatura, Derek Klinge, 16:34
  • midi2ly fails on OSX 10.6.8, Floris van Manen, 16:25
  • Re: Issue 1754 in lilypond: bug when slur incorporate acciaccatura, lilypond, 16:12
  • Re: Issue 1754 in lilypond: bug when slur incorporate acciaccatura, lilypond, 16:08
  • Issue 1754 in lilypond: bug when slur incorporate acciaccatura, lilypond, 16:04
  • bug when slur incorporates acciaccatura, Ruud van Silfhout, 15:50
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 12:50
  • Re: Issue 1750 in lilypond: Documentation suggestion: transposition resulting in triple accidentals, lilypond, 05:49
  • Re: Documentation suggestion: transposition resulting in triple accidentals, Graham Percival, 03:54
• July 08, 2011
  • Re: Issue 1753 in lilypond: Ehancement: tab for diatonic instruments, lilypond, 22:43
  • Re: Issue 1508 in lilypond: Key signature wrong with cued music, lilypond, 21:47
  • Re: Issue 1508 in lilypond: Key signature wrong with cued music, lilypond, 21:43
  • Re: Issue 1666 in lilypond: Docs problem: fretted-string-harmonics-in-tablature snippet, lilypond, 21:39
  • Re: Diatonic Instruments (Mountain Dulcimer), Colin Campbell, 21:28
  • Issue 1753 in lilypond: Ehancement: tab for diatonic instruments, lilypond, 21:28
  • Re: Issue 1748 in lilypond: Defect in glissando handling, lilypond, 20:30
  • Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 20:03
  • Re: Issue 1712 in lilypond: Braces redesigned, lilypond, 19:13
  • Re: Issue 1748 in lilypond: Defect in glissando handling, lilypond, 19:09
  • Re: Issue 1733 in lilypond: \displayLilyMusic ignores \tweak, lilypond, 18:59
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, lilypond, 18:55
  • Re: Diatonic Instruments (Mountain Dulcimer), Janek Warchoł, 18:51
  • Re: accidentaled notes too far from the barline, Janek Warchoł, 18:45
  • Issue 1751 in lilypond: Most analysis brackets get incorrect event-cause info, breaking point-and-click & \tweak, lilypond, 17:56
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 16:48
  • RE: Documentation suggestion: transposition resulting in triple accidentals, James Lowe, 12:03
  • Re: Issue 1750 in lilypond: Documentation suggestion: transposition resulting in triple accidentals, lilypond, 12:00
  • Re: Documentation suggestion: transposition resulting in triple accidentals, David Kastrup, 11:42
  • RE: Documentation suggestion: transposition resulting in triple accidentals, James Lowe, 11:12
  • Re: Documentation suggestion: transposition resulting in triple accidentals, Graham Percival, 11:10
  • RE: Documentation suggestion: transposition resulting in triple accidentals, James Lowe, 11:06
  • Re: Documentation suggestion: transposition resulting in triple accidentals, Graham Percival, 10:55
  • Re: Issue 1750 in lilypond: Documentation suggestion: transposition resulting in triple accidentals, lilypond, 10:55
  • Re: Issue 1750 in lilypond: Documentation suggestion: transposition resulting in triple accidentals, lilypond, 10:51
  • RE: Documentation suggestion: transposition resulting in triple accidentals, James Lowe, 10:33
  • Issue 1750 in lilypond: Documentation suggestion: transposition resulting in triple accidentals, lilypond, 10:32
  • Documentation suggestion: transposition resulting in triple accidentals, Urs Liska, 09:11
  • Re: Diatonic Instruments (Mountain Dulcimer), Carl Sorensen, 08:40
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 05:12
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 04:37
  • Re: Issue 1747 in lilypond: parallelmusic problem: q-notation does not work in \relative, lilypond, 04:33
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 04:29
  • Re: Issue 1747 in lilypond: parallelmusic problem: q-notation does not work in \relative, lilypond, 04:25
  • Re: Diatonic Instruments (Mountain Dulcimer), Janek Warchoł, 03:51
  • Re: problem with articulate and ties in chords, Janek Warchoł, 03:33
  • Re: Issue 1747 in lilypond: parallelmusic problem: q-notation does not work in \relative, Dmytro O. Redchuk, 03:32
  • Re: Switcing accidental style doesn't always work, Dmytro O. Redchuk, 03:19
  • Re: Possible regression in 2.13 series? "no viable configuration" warning, Valentin Villenave, 03:15
  • Re: problem with articulate and ties in chords, Janek Warchoł, 02:02
  • Issue 1749 in lilypond: articulate script doesn't support partial ties, lilypond, 01:59
• July 07, 2011
  • Re: Issue 1747 in lilypond: parallelmusic problem: q-notation does not work in \relative, Nicolas Sceaux, 18:14
  • Re: Issue 1664 in lilypond: Add link to LSR on web site, lilypond, 17:57
  • Re: Issue 1733 in lilypond: \displayLilyMusic ignores \tweak, lilypond, 15:16
  • Re: Issue 1748 in lilypond: Defect in glissando handling, lilypond, 14:56
  • Re: Issue 1747 in lilypond: parallelmusic problem: q-notation does not work in \relative, lilypond, 14:52
  • Re: Switcing accidental style doesn't always work, Ole Vedel Villumsen, 13:25
  • Re: Switcing accidental style doesn't always work, Neil Puttock, 12:25
  • Re: Issue 153 in lilypond: \once \set fails to restore previous setting, lilypond, 12:19
  • Re: Issue 1748 in lilypond: Defect in glissando handling, lilypond, 11:23
  • Re: Many single-system scores produces bad output and overflow, Xavier Scheuer, 11:13
  • Re: Issue 153 in lilypond: \once \set fails to restore previous setting, lilypond, 10:35
  • Issue 1748 in lilypond: Defect in glissando handling, lilypond, 10:06
  • Re: Possible regression in 2.13 series? "no viable configuration" warning, Dmytro O. Redchuk, 09:19
  • Re: Many single-system scores produces bad output and overflow, Dmytro O. Redchuk, 09:13
  • Re: accidentaled notes too far from the barline, Dmytro O. Redchuk, 09:02
  • Re: Issue 153 in lilypond: \once \set fails to restore previous setting, lilypond, 08:06
  • Re: Issue 1747 in lilypond: parallelmusic problem: q-notation does not work in \relative, lilypond, 06:13
  • Re: Issue 1747 in lilypond: parallelmusic problem: q-notation does not work in \relative, lilypond, 06:01
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, lilypond, 05:57
  • Re: Issue 1747 in lilypond: parallelmusic problem: q-notation does not work in \relative, lilypond, 05:42
  • Re: Issue 1615 in lilypond: lily-git.tcl not working: savannah sometimes does not like git fetch --depth, lilypond, 05:16
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, lilypond, 05:12
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, lilypond, 05:08
  • Re: parallelmusic problem: q-notation does not work in \relative, Dmytro O. Redchuk, 04:46
  • Issue 1747 in lilypond: parallelmusic problem: q-notation does not work in \relative, lilypond, 04:46
  • Issue 1746 in lilypond: v2.13.48 docball adds offline-root/ directory, lilypond, 04:12
  • Re: v2.13.48 docball adds offline-root/ directory..., Dmytro O. Redchuk, 04:11
  • Re: Issue 1699 in lilypond: Automated numbering for footnotes, lilypond, 04:08
  • Re: Issue 1745 in lilypond: Strange vertical space above TupletBracket when moving it for the sake of cross-staff beamed tuplets, lilypond, 03:43
  • Re: tuplet number on cross-staff kneed-beam, Dmytro O. Redchuk, 03:42
  • Issue 1745 in lilypond: Strange vertical space above TupletBracket when moving it for the sake of cross-staff beamed tuplets, lilypond, 03:34
  • Re: tuplet number on cross-staff kneed-beam, Dmytro O. Redchuk, 03:34
  • Re: Issue 1716 in lilypond: No convert-ly rule for the fix for issue 1655, lilypond, 02:41
  • Re: Issue 1651 in lilypond: Triplet direction depends on rest length, lilypond, 02:37
  • Re: Issue 1737 in lilypond: Add table of predefined fretboards for ukulele and mandolin to NR Appendices, lilypond, 02:33
  • Re: Issue 1738 in lilypond: Hairpin in dynamics aligns to lyric, lilypond, 02:29
  • Re: Issue 502 in lilypond: hairpins bound to spacer notes are aligned on lyrics, lilypond, 02:25
  • Re: Issue 153 in lilypond: \once \set fails to restore previous setting, Dmytro O. Redchuk, 02:07
  • Issue 1744 in lilypond: \once \set behavior should be documented, lilypond, 02:04
  • Re: Switcing accidental style doesn't always work, Dmytro O. Redchuk, 01:54
• July 06, 2011
  • Re: Issue 1705 in lilypond: New breve rest with ledger lines, lilypond, 22:36
  • Re: Issue 1710 in lilypond: rearrange flag definitions in feta-flags.mf, lilypond, 22:07
  • Re: Issue 1711 in lilypond: Pitch bend tuning adjustments, lilypond, 22:03
  • Re: Issue 153 in lilypond: \once \set fails to restore previous setting, -Eluze, 17:00
  • Re: Issue 1664 in lilypond: Add link to LSR on web site, lilypond, 16:09
  • Re: Issue 1737 in lilypond: Add table of predefined fretboards for ukulele and mandolin to NR Appendices, lilypond, 13:20
  • Re: Issue 1743 in lilypond: lilypond-2.15.4-1.mingw.exe does not install PATH on Windows 7 SP1, lilypond, 12:51
  • Issue 1743 in lilypond: lilypond-2.15.4-1.mingw.exe does not install PATH on Windows 7 SP1, lilypond, 12:15
  • Re: tuplet number on cross-staff kneed-beam, David Nalesnik, 10:49
  • Re: tuplet number on cross-staff kneed-beam, David Nalesnik, 10:49
  • parallelmusic problem: q-notation does not work in \relative, Arno Waschk, 09:05
  • Re: Issue 1742 in lilypond: print transposed guitar chords on piano sheets, lilypond, 05:06
  • Re: Issue 1742 in lilypond: print transposed guitar chords on piano sheets, lilypond, 05:02
  • Re: Issue 153 in lilypond: \once \set fails to restore previous setting, lilypond, 03:32
  • Re: quarter-tone tablature bug, Dmytro O. Redchuk, 03:06
  • Re: Issue 1741 in lilypond: Tablature Bug when string is tuned to beh, lilypond, 03:04
  • Re: Issue 1014 in lilypond: Full/multi measure rests should be semibreve (for any but 4/2), lilypond, 02:59
  • Re: Issue 1742 in lilypond: print transposed guitar chords on piano sheets, lilypond, 02:44
  • Re: Issue 1737 in lilypond: Add table of predefined fretboards for ukulele and mandolin to NR Appendices, lilypond, 02:37
  • Re: Issue 153 in lilypond: \once \set fails to restore previous setting, lilypond, 01:53
  • Re: Issue 1740 in lilypond: \set should store "original" settings so \once \set would restore them, lilypond, 01:48
• July 05, 2011
  • Re: tuplet number on cross-staff kneed-beam, Colin Campbell, 22:40
  • Re: Issue 1741 in lilypond: Tablature Bug when string is tuned to beh, lilypond, 19:53
  • Re: Issue 1741 in lilypond: Tablature Bug when string is tuned to beh, lilypond, 19:49
  • Re: Issue 1741 in lilypond: Tablature Bug when string is tuned to beh, lilypond, 19:45
  • Re: Issue 1741 in lilypond: Tablature Bug when string is tuned to beh, lilypond, 19:34
  • Re: Issue 1741 in lilypond: Tablature Bug when string is tuned to beh, lilypond, 19:30
  • Re: Issue 1741 in lilypond: Tablature Bug when string is tuned to beh, lilypond, 19:26
  • quarter-tone tablature bug, Bernardo Barros, 19:15
  • Re: Issue 1741 in lilypond: Tablature Bug when string is tuned to beh, lilypond, 18:14
  • Issue 1742 in lilypond: print transposed guitar chords on piano sheets, lilypond, 18:05
  • Issue 1741 in lilypond: Tablature Bug when string is tuned to beh, lilypond, 17:48
  • Re: v2.13.48 docball adds offline-root/ directory..., Graham Percival, 17:22
  • Re: Issue 1014 in lilypond: Full/multi measure rests should be semibreve (for any but 4/2), lilypond, 17:01
  • Re: Issue 502 in lilypond: hairpins bound to spacer notes are aligned on lyrics, lilypond, 15:32
  • Re: Issue 620 in lilypond: It should be possible to specify more specific spanner bounds., lilypond, 15:28
  • Re: Issue 153 in lilypond: \once \set fails to restore previous setting, lilypond, 15:24
  • Re: Issue 1740 in lilypond: \set should store "original" settings so \once \set would restore them, lilypond, 15:19
  • Re: Issue 153 in lilypond: \once \set fails to restore previous setting, lilypond, 15:15
  • Re: Issue 1738 in lilypond: Hairpin in dynamics aligns to lyric, lilypond, 09:22
  • Re: Issue 502 in lilypond: hairpins bound to spacer notes are aligned on lyrics, lilypond, 09:18
  • v2.13.48 docball adds offline-root/ directory..., Jan Nieuwenhuizen, 07:01
  • Issue 1740 in lilypond: \set should store "original" settings so \once \set would restore them, lilypond, 06:27
  • Re: after \once \set fingeringOr ientations… Lilypond falls back to #up, Dmytro O. Redchuk, 06:23
  • Issue 1739 in lilypond: doc: correcting note about rerunning regtests, lilypond, 03:49
  • Re: tuplet number on cross-staff kneed-beam, Valentin Villenave, 03:45
  • Issue 1738 in lilypond: Hairpin in dynamics aligns to lyric, lilypond, 03:42
  • Re: Issue 1014 in lilypond: Full/multi measure rests should be semibreve (for any but 4/2), lilypond, 02:39
• July 04, 2011
  • Switcing accidental style doesn't always work, Ole Vedel Villumsen, 22:30
  • Issue 1737 in lilypond: Add table of predefined fretboards for ukulele and mandolin to NR Appendices, lilypond, 19:43
  • Re: Issue 1734 in lilypond: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } }, lilypond, 18:42
  • Re: Issue 75 in lilypond: Slurs cannot be nested (including acciaccatura and appoggiatura), lilypond, 18:31
  • Re: Issue 1014 in lilypond: Full/multi measure rests should be semibreve (for any but 4/2), lilypond, 17:33
  • Research on ties (was: Odd-looking tie on a chord), Janek Warchoł, 17:21
  • Re: after \once \set fingeringOrien tations… Lilypond falls back to #up, -Eluze, 17:17
  • Re: Issue 1709 in lilypond: Add feta-flags to build system, lilypond, 17:10
  • Re: Issue 1014 in lilypond: Full/multi measure rests should be semibreve (for any but 4/2), lilypond, 16:27
  • Issue 1736 in lilypond: clarify description of minimal examples, lilypond, 16:23
  • Issue 1735 in lilypond: modifying default behaviour of tremolo slashes, lilypond, 15:54
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, lilypond, 15:50
  • Re: Issue 1643 in lilypond: Part Combine problems, lilypond, 15:46
  • Re: Issue 1714 in lilypond: Build error regarding mf2pt1 with latest texlive (2011) and lilypond, lilypond, 15:42
  • Re: Issue 1714 in lilypond: Build error regarding mf2pt1 with latest texlive (2011) and lilypond, lilypond, 15:38
  • Re: Issue 1716 in lilypond: No convert-ly rule for the fix for issue 1655, lilypond, 15:34
  • Re: Issue 1682 in lilypond: Website version links need updating, lilypond, 15:30
  • Re: Issue 1692 in lilypond: Spanner::calc_normalized_endpoints is broken for line-spanners, lilypond, 15:26
  • Re: Issue 1706 in lilypond: Beaming causes lilypond to crash, lilypond, 15:22
  • Re: Issue 1706 in lilypond: Beaming causes lilypond to crash, lilypond, 15:18
  • Re: Issue 1014 in lilypond: Full/multi measure rests should be semibreve (for any but 4/2), lilypond, 15:14
  • Re: Issue 1617 in lilypond: chordGlissando is a hack that should be replaced with a Glissando property such as 'connect-all, lilypond, 15:10
  • Re: Issue 487 in lilypond: stems of beamed notes too long before staff change, lilypond, 15:06
  • Re: Issue 1043 in lilypond: Cross-staff beams confuse skyline calculations, lilypond, 15:02
  • Re: Issue 1467 in lilypond: [PATCH] Doc: Rewrite NR 3.2 Titles and headers. (issue3667041), lilypond, 14:58
  • Re: Issue 1502 in lilypond: Document information in PDF headers requires escapes for accented characters, lilypond, 14:54
  • Re: Issue 1502 in lilypond: Document information in PDF headers requires escapes for accented characters, lilypond, 14:50
  • Re: Issue 1547 in lilypond: Too many colliding rests, lilypond, 14:46
  • Re: Issue 1607 in lilypond: patch for mandolin freboard diagrams, lilypond, 14:35
  • Re: Issue 1607 in lilypond: patch for mandolin freboard diagrams, lilypond, 14:31
  • Re: Issue 1614 in lilypond: DynamicTextSpanner documentation is wrong, lilypond, 14:24
  • Re: Issue 816 in lilypond: Accidentals should use the normal fontsize in figured bass, lilypond, 14:13
  • Re: Issue 1618 in lilypond: unpredictable placement of rests, lilypond, 14:08
  • Re: Issue 1626 in lilypond: Articulate produces faulty barcheck warnings, lilypond, 13:10
  • Re: Issue 1639 in lilypond: Glissando between chords at end of measure prevents break and is sometimes not printed, lilypond, 13:06
  • Re: Issue 1640 in lilypond: Consecutive glissandos not typeset, lilypond, 13:02
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Dmytro O. Redchuk, 10:46
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Dmytro O. Redchuk, 10:25
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Neil Puttock, 10:19
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Neil Puttock, 10:16
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Dmytro O. Redchuk, 10:15
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Dmytro O. Redchuk, 09:58
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Neil Puttock, 09:48
  • Re: Issue 1734 in lilypond: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } }, lilypond, 09:43
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Dmytro O. Redchuk, 09:17
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Colin Campbell, 09:06
  • Re: Issue 1734 in lilypond: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } }, lilypond, 08:56
  • Re: Issue 1734 in lilypond: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } }, lilypond, 08:52
  • Re: Issue 1712 in lilypond: Braces redesigned, lilypond, 08:48
  • Re: Issue 1734 in lilypond: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } }, lilypond, 08:40
  • Re: after \once \set fingeringOr ientations… Lilypond falls back to #up, Dmytro O. Redchuk, 08:34
  • Re: Issue 1734 in lilypond: Lilypond crashes on "fingeringOrientations = #'right" if set in \layout { \ context { \Score ... } }, lilypond, 08:29
  • Issue 1734 in lilypond: Lilypond crashes on "fingeringOrientations = #'right" with simple fingerings, lilypond, 08:24
  • Re: Issue 75 in lilypond: Slurs cannot be nested (including acciaccatura and appoggiatura), lilypond, 08:20
  • Re: after \once \set fingeringOrien tations… Lilypond falls back to #up, -Eluze, 08:15
  • Re: after \once \set fingeringOr ientations… Lilypond falls back to #up, Dmytro O. Redchuk, 07:44
  • Re: after \once \set fingeringOrien tations… Lilypond falls back to #up, -Eluze, 07:22
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), Dmytro O. Redchuk, 06:39
  • Re: Odd-looking tie on a chord, address@hidden, 06:15
  • Re: Odd-looking tie on a chord, Dmytro O. Redchuk, 05:46
  • Re: Issue 1126 in lilypond: Tie positioning not as expected, lilypond, 05:44
  • Re: after \once \set fingeringOr ientations… Lilypond falls back to #up, Dmytro O. Redchuk, 04:51
  • Re: Issue 1728 in lilypond: Implements multi-line non-cross staff glissandi, lilypond, 04:45
  • after \once \set fingeringOrienta tions… Lilypond falls back to #up, -Eluze, 04:43
  • Re: Issue 1728 in lilypond: Implements multi-line non-cross staff glissandi, lilypond, 04:32
  • Re: Issue 1542 in lilypond: [PATCH] Add springs-and-rods callback to DynamicTextSpanner, so minimum-length has an effect (issue4187054), lilypond, 04:28
  • Re: Issue 1655 in lilypond: Handles longa in MultiMeasureRest, lilypond, 04:24
  • Re: Issue 1728 in lilypond: Implements multi-line non-cross staff glissandi, lilypond, 04:20
  • Re: Issue 1692 in lilypond: Spanner::calc_normalized_endpoints is broken for line-spanners, lilypond, 04:16
  • Re: Issue 1708 in lilypond: Adds ly:engraver-property to engraver-scheme, lilypond, 04:12
  • Re: Issue 1728 in lilypond: Implements multi-line non-cross staff glissandi, lilypond, 04:08
  • Re: Issue 1728 in lilypond: Implements multi-line non-cross staff glissandi, lilypond, 04:04
• July 03, 2011
  • Re: Issue 1709 in lilypond: Add feta-flags to build system, lilypond, 22:41
  • Re: Issue 75 in lilypond: Slurs cannot be nested (including acciaccatura and appoggiatura), lilypond, 20:18
  • Re: Issue 1715 in lilypond: Ligature and ambitus cause segfault, lilypond, 20:14
  • Re: Issue 1733 in lilypond: \displayLilyMusic ignores \tweak, lilypond, 20:04
  • Re: Issue 1507 in lilypond: weird linebreaks in song output, lilypond, 18:10
  • Re: Issue 1733 in lilypond: \displayLilyMusic ignores \tweak, lilypond, 18:01
  • Re: Issue 1715 in lilypond: Ligature and ambitus cause segfault, lilypond, 17:12
  • Re: Issue 75 in lilypond: Slurs cannot be nested (including acciaccatura and appoggiatura), lilypond, 15:44
  • Re: Issue 75 in lilypond: Slurs cannot be nested (including acciaccatura and appoggiatura), lilypond, 10:46
  • Re: occasional segfault when compiling input/regression/midi/key-initial.ly, Dmytro O. Redchuk, 10:23
  • Re: Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly, lilypond, 10:23
  • Re: Issue 75 in lilypond: Slurs cannot be nested (including acciaccatura and appoggiatura), lilypond, 09:53
  • Issue 1733 in lilypond: \displayLilyMusic ignores \tweak, lilypond, 09:44
  • Issue 1732 in lilypond: occasional segfault when compiling input/regression/midi/key-initial.ly, lilypond, 07:56
  • occasional segfault when compiling input/regression/midi/key-initial.ly, Federico Bruni, 07:36
  • Issue 1731 in lilypond: LilyPond fails to install on Puppy Linux, lilypond, 07:03
  • Issue 1730 in lilypond: Documentation for lilypond-windows.exe and -dgui option, lilypond, 06:36
  • Re: Issue 1712 in lilypond: Braces redesigned, lilypond, 02:33
• July 02, 2011
  • Re: Issue 1433 in lilypond: \breakDynamicSpan breaks with \break ("bounds of spanner are invalid"), lilypond, 20:07
  • Re: Issue 1259 in lilypond: DynamicTextSpanner #'style = #'none doesn't work over \break, lilypond, 20:03
  • Re: Issue 770 in lilypond: Lyrics behave differently when associated to a Voice-derived context, lilypond, 19:37
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, lilypond, 17:37
  • Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals, Keith OHara, 17:12
  • Re: Issue 1716 in lilypond: No convert-ly rule for the fix for issue 1655, lilypond, 10:44
  • Re: Issue 896 in lilypond: When used after \tag, \partcombine may fail to print notes, lilypond, 10:38
  • Re: Issue 675 in lilypond: \partcombine: consecutives crescendos make voices disappear!, lilypond, 10:34
  • Re: Issue 645 in lilypond: midiInstrument + \transposition + \partcombine = wrong MIDI output, lilypond, 10:30
  • Re: Issue 385 in lilypond: \partcombine with grace notes results in incorrectly combined stems, lilypond, 10:26
  • Re: Issue 245 in lilypond: partcombine multiple tuplet brackets false warning, lilypond, 10:22
  • Re: Issue 1677 in lilypond: Partcombine misses notes, lilypond, 10:18
  • Re: Issue 100 in lilypond: Partcombine must use note durations, lilypond, 10:14
  • Re: Issue 1435 in lilypond: [PATCH] PartCombine: Keep track of the state in the Part_combine_engraver (issue3334043), lilypond, 10:10
  • Re: Issue 806 in lilypond: Musicxml2ly problem with tempo indications when a piece starts with MM rests., lilypond, 10:06
  • Re: Steams in second voice with auto beaming are broken, Francisco Vila, 09:52
  • Re: Steams in second voice with auto beaming are broken, Phil Holmes, 09:38
  • Re: Issue 770 in lilypond: Lyrics behave differently when associated to a Voice-derived context, lilypond, 07:31
• July 01, 2011
  • Re: Issue 1726 in lilypond: python versions might not be updating, lilypond, 19:51
  • Re: Issue 1726 in lilypond: python versions might not be updating, lilypond, 19:20
  • Re: Issue 1706 in lilypond: Beaming causes lilypond to crash, lilypond, 13:50
  • Re: Issue 1729 in lilypond: Set spanner length as a spanner property, lilypond, 05:49
  • Re: Issue 1728 in lilypond: Implements multi-line non-cross staff glissandi, lilypond, 05:40
  • Re: Issue 1716 in lilypond: No convert-ly rule for the fix for issue 1655, lilypond, 05:28

---

[Prev Period]

[Next Period]

---

Mail converted by MHonArc