Archives are refreshed every 30 minutes - for details, please visit the main index.
You can also download the archives in mbox format.

lilypond-auto (date)

[Thread Index][Top][All Lists]

Advanced

[Prev Period]

Last Modified: Tue Jul 31 2012 23:12:49 -0400 Messages in reverse chronological order

[Next Period]

---

• July 31, 2012
  • Re: [Lilypond-auto] Issue 1650 in lilypond: using multiple \header in a block prints only the latest items, lilypond, 23:12
  • Re: [Lilypond-auto] Issue 2700 in lilypond: Patch: Change $ to # in docs where appropriate, lilypond, 22:36
  • Re: [Lilypond-auto] Issue 2702 in lilypond: Patch: Unify the lexer's idea of words and commands across all modes., lilypond, 21:53
  • Re: [Lilypond-auto] Issue 2704 in lilypond: Add missing "#include <unistd.h>" for use with g++ 4.7, lilypond, 21:47
  • Re: [Lilypond-auto] Issue 2700 in lilypond: Patch: Change $ to # in docs where appropriate, lilypond, 21:45
  • Re: [Lilypond-auto] Issue 1661 in lilypond: MIDI dynamics take effect one note too late, lilypond, 21:44
  • Re: [Lilypond-auto] Issue 1650 in lilypond: using multiple \header in a block prints only the latest items, lilypond, 21:43
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 21:42
  • Re: [Lilypond-auto] Issue 673 in lilypond: problem with order of \consists, lilypond, 21:41
  • Re: [Lilypond-auto] Issue 2701 in lilypond: Setting automatic beams is not explained well, lilypond, 18:31
  • [Lilypond-auto] Patchy email, lilypond-auto, 18:29
  • Re: [Lilypond-auto] Issue 2701 in lilypond: Setting automatic beams is not explained well, lilypond, 18:19
  • Re: [Lilypond-auto] Issue 1834 in lilypond: Website: provide link to .ly for examples, lilypond, 17:34
  • Re: [Lilypond-auto] Issue 2709 in lilypond: Patch: Changes make test to allow output to be reviewed in a browser, lilypond, 17:32
  • [Lilypond-auto] Issue 2710 in lilypond: superfluous commands in titling-init.ly, lilypond, 17:21
  • [Lilypond-auto] Issue 2709 in lilypond: Patch: Changes make test to allow output to be reviewed in a browser, lilypond, 16:52
  • Re: [Lilypond-auto] Issue 2708 in lilypond: Patch: Let \lyricmode et al apply an optional markup head to text music properties, lilypond, 13:20
  • [Lilypond-auto] Issue 2708 in lilypond: Patch: Let \lyricmode et al apply an optional markup head to text music properties, lilypond, 13:19
  • Re: [Lilypond-auto] Issue 2699 in lilypond: Patch: Properly implement fromproperty markup handing in the pdftitle header field, lilypond, 10:04
  • [Lilypond-auto] Patchy email, lilypond-auto, 10:02
  • Re: [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 04:53
  • [Lilypond-auto] Patchy email, lilypond-auto, 02:55
  • Re: [Lilypond-auto] Issue 2647 in lilypond: Doc: Clicking on lilypond example images to obtain source file, lilypond, 02:25
  • Re: [Lilypond-auto] Issue 2640 in lilypond: doc enhancement for \headers, lilypond, 02:24
  • Re: [Lilypond-auto] Issue 1834 in lilypond: Website: provide link to .ly for examples, lilypond, 02:14
• July 30, 2012
  • Re: [Lilypond-auto] Issue 2672 in lilypond: Patch: Midi fixes, lilypond, 21:02
  • [Lilypond-auto] Issue 2707 in lilypond: Patch: Midi volume fixes, lilypond, 21:01
  • Re: [Lilypond-auto] Issue 2640 in lilypond: doc enhancement for \headers, lilypond, 18:55
  • Re: [Lilypond-auto] Issue 1650 in lilypond: using multiple \header in a block prints only the latest items, lilypond, 18:47
  • [Lilypond-auto] Patchy email, lilypond-auto, 18:30
  • [Lilypond-auto] Patchy email, lilypond-auto, 18:30
  • [Lilypond-auto] Patchy email, lilypond-auto, 18:17
  • [Lilypond-auto] Patchy email, lilypond-auto, 18:13
  • Re: [Lilypond-auto] Issue 2705 in lilypond: Patch: Parse music inside of output definitions in "notes" mode., lilypond, 16:32
  • Re: [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 16:21
  • Re: [Lilypond-auto] Issue 1650 in lilypond: using multiple \header in a block prints only the latest items, lilypond, 16:00
  • Re: [Lilypond-auto] Issue 2703 in lilypond: Patch: Set indent based on instrument name, lilypond, 15:46
  • Re: [Lilypond-auto] Issue 2704 in lilypond: Add missing "#include <unistd.h>" for use with g++ 4.7, lilypond, 15:45
  • Re: [Lilypond-auto] Issue 2705 in lilypond: Patch: Parse music inside of output definitions in "notes" mode., lilypond, 15:42
  • Re: [Lilypond-auto] Issue 2705 in lilypond: Patch: Parse music inside of output definitions in "notes" mode., lilypond, 15:31
  • Re: [Lilypond-auto] Issue 2705 in lilypond: Patch: Parse music inside of output definitions in "notes" mode., lilypond, 15:29
  • [Lilypond-auto] Issue 2706 in lilypond: add link to enc2ly, lilypond, 14:15
  • Re: [Lilypond-auto] Issue 1650 in lilypond: using multiple \header in a block prints only the latest items, lilypond, 13:42
  • Re: [Lilypond-auto] Issue 2703 in lilypond: Patch: Set indent based on instrument name, lilypond, 13:41
  • Re: [Lilypond-auto] Issue 2703 in lilypond: Patch: Set indent based on instrument name, lilypond, 13:37
  • Re: [Lilypond-auto] Issue 2705 in lilypond: Patch: Parse music inside of output definitions in "notes" mode., lilypond, 12:17
  • [Lilypond-auto] Issue 2705 in lilypond: Patch: Parse music inside of output definitions in "notes" mode., lilypond, 12:15
  • [Lilypond-auto] Patchy email, lilypond-auto, 09:56
  • Re: [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 09:51
  • Re: [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 09:50
  • Re: [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 09:34
  • Re: [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 09:20
  • Re: [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 08:53
  • [Lilypond-auto] Issue 2704 in lilypond: Add missing "#include <unistd.h>" for use with g++ 4.7, lilypond, 08:15
  • Re: [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 06:45
  • [Lilypond-auto] Email from Phil's patchy, phileholmes, 05:58
  • Re: [Lilypond-auto] Issue 2672 in lilypond: Patch: Midi fixes, lilypond, 04:20
  • Re: [Lilypond-auto] Issue 2672 in lilypond: Patch: Midi fixes, lilypond, 04:18
  • Re: [Lilypond-auto] Issue 2703 in lilypond: Patch: Set indent based on instrument name, lilypond, 03:17
  • Re: [Lilypond-auto] Issue 2703 in lilypond: Patch: Set indent based on instrument name, lilypond, 03:16
  • Re: [Lilypond-auto] Issue 2698 in lilypond: Patch: Syntax change: don't allow degenerate REAL -., lilypond, 01:56
  • Re: [Lilypond-auto] Issue 2696 in lilypond: Patch: 4 issues related to rational duration factors., lilypond, 01:52
  • Re: [Lilypond-auto] Issue 2699 in lilypond: Patch: Properly implement fromproperty markup handing in the pdftitle header field, lilypond, 01:39
  • Re: [Lilypond-auto] Issue 2698 in lilypond: Patch: Syntax change: don't allow degenerate REAL -., lilypond, 01:36
  • Re: [Lilypond-auto] Issue 2696 in lilypond: Patch: 4 issues related to rational duration factors., lilypond, 01:35
  • Re: [Lilypond-auto] Issue 2673 in lilypond: Volta improvements, lilypond, 01:32
  • Re: [Lilypond-auto] Issue 2401 in lilypond: NR 1.2.4 - Not working snippet in German translation, lilypond, 01:31
  • Re: [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 00:59
• July 29, 2012
  • Re: [Lilypond-auto] Issue 2702 in lilypond: Patch: Unify the lexer's idea of words and commands across all modes., lilypond, 16:07
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 15:58
  • [Lilypond-auto] Issue 2703 in lilypond: Patch: Set indent based on instrument name, lilypond, 14:16
  • Re: [Lilypond-auto] Issue 2702 in lilypond: Patch: Unify the lexer's idea of words and commands across all modes., lilypond, 12:09
  • Re: [Lilypond-auto] Issue 2647 in lilypond: Doc: Clicking on lilypond example images to obtain source file, lilypond, 11:03
  • Re: [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 10:49
  • Re: [Lilypond-auto] Issue 2702 in lilypond: Patch: Unify the lexer's idea of words and commands across all modes., lilypond, 10:17
  • [Lilypond-auto] Issue 2702 in lilypond: Patch: Unify the lexer's idea of words and commands across all modes., lilypond, 10:14
  • Re: [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 07:07
  • Re: [Lilypond-auto] Issue 1650 in lilypond: using multiple \header in a block prints only the latest items, lilypond, 06:50
  • Re: [Lilypond-auto] Issue 1650 in lilypond: using multiple \header in a block prints only the latest items, lilypond, 06:27
  • Re: [Lilypond-auto] Issue 1650 in lilypond: using multiple \header in a block prints only the latest items, lilypond, 06:20
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 05:19
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 05:00
  • Re: [Lilypond-auto] Issue 2700 in lilypond: Patch: Change $ to # in docs where appropriate, lilypond, 04:22
  • Re: [Lilypond-auto] Issue 1999 in lilypond: Nonsensical example in programming-interface.itely, lilypond, 02:32
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 02:27
• July 28, 2012
  • Re: [Lilypond-auto] Issue 2640 in lilypond: doc enhancement for \headers, lilypond, 18:39
  • Re: [Lilypond-auto] Issue 1999 in lilypond: Nonsensical example in programming-interface.itely, lilypond, 17:28
  • [Lilypond-auto] Issue 2701 in lilypond: Setting automatic beams is not explained well, lilypond, 16:50
  • [Lilypond-auto] Patchy email, lilypond-auto, 15:55
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 14:33
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 14:05
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 13:48
  • Re: [Lilypond-auto] Issue 2700 in lilypond: Patch: Change $ to # in docs where appropriate, lilypond, 13:45
  • [Lilypond-auto] Issue 2700 in lilypond: Patch: Change $ to # in docs where appropriate, lilypond, 11:41
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 09:29
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 09:26
  • Re: [Lilypond-auto] Issue 2691 in lilypond: Chord names collide with beams (vertical space missing on second line staff), lilypond, 08:50
  • [Lilypond-auto] Email from Phil's patchy, phileholmes, 08:37
  • Re: [Lilypond-auto] Issue 2691 in lilypond: Chord names collide with beams (vertical space missing on second line staff), lilypond, 08:37
  • [Lilypond-auto] Patchy email, lilypond-auto, 07:53
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 03:50
  • Re: [Lilypond-auto] Issue 1132 in lilypond: Header oddity, lilypond, 03:46
  • Re: [Lilypond-auto] Issue 1650 in lilypond: using multiple \header in a block prints only the latest items, lilypond, 03:45
  • Re: [Lilypond-auto] Issue 1650 in lilypond: using multiple \header in a block prints only the latest items, lilypond, 01:41
  • Re: [Lilypond-auto] Issue 673 in lilypond: problem with order of \consists, lilypond, 01:40
  • Re: [Lilypond-auto] Issue 673 in lilypond: problem with order of \consists, lilypond, 00:09
• July 27, 2012
  • [Lilypond-auto] Patchy email, lilypond-auto, 21:55
  • Re: [Lilypond-auto] Issue 1661 in lilypond: MIDI dynamics take effect one note too late, lilypond, 19:10
  • Re: [Lilypond-auto] Issue 2691 in lilypond: Chord names collide with beams (vertical space missing on second line staff), lilypond, 18:59
  • Re: [Lilypond-auto] Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 18:19
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 16:36
  • Re: [Lilypond-auto] Issue 1650 in lilypond: using multiple \header in a block prints only the latest items, lilypond, 14:40
  • Re: [Lilypond-auto] Issue 1650 in lilypond: using multiple \header in a block prints only the latest items, lilypond, 14:39
  • [Lilypond-auto] Patchy email, lilypond-auto, 10:06
  • Re: [Lilypond-auto] Issue 1661 in lilypond: MIDI dynamics take effect one note too late, lilypond, 09:05
  • Re: [Lilypond-auto] Issue 1661 in lilypond: MIDI dynamics take effect one note too late, lilypond, 08:51
  • Re: [Lilypond-auto] Issue 1132 in lilypond: Header oddity, lilypond, 08:25
  • Re: [Lilypond-auto] Issue 1650 in lilypond: using multiple \header in a block prints only the latest items, lilypond, 08:24
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 08:21
  • Re: [Lilypond-auto] Issue 1661 in lilypond: MIDI dynamics take effect one note too late, lilypond, 07:44
  • [Lilypond-auto] Email from Phil's patchy, phileholmes, 05:42
  • Re: [Lilypond-auto] Issue 673 in lilypond: problem with order of \consists, lilypond, 04:00
  • Re: [Lilypond-auto] Issue 2690 in lilypond: \tweak warning re tied chord no longer applies, lilypond, 03:29
  • Re: [Lilypond-auto] Issue 1132 in lilypond: Header oddity, lilypond, 01:50
  • Re: [Lilypond-auto] Issue 2664 in lilypond: stringTunings snippet in NR 2.4.1, lilypond, 01:33
  • Re: [Lilypond-auto] Issue 2692 in lilypond: Patch: Let ly:make-moment accept rationals for main and grace timing, lilypond, 01:31
  • Re: [Lilypond-auto] Issue 1650 in lilypond: using multiple \header in a block prints only the latest items, lilypond, 01:23
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 01:21
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 01:20
  • Re: [Lilypond-auto] Issue 2640 in lilypond: doc enhancement for \headers, lilypond, 01:12
  • Re: [Lilypond-auto] Issue 2699 in lilypond: Patch: Properly implement fromproperty markup handing in the pdftitle header field, lilypond, 01:11
  • Re: [Lilypond-auto] Issue 2640 in lilypond: doc enhancement for \headers, lilypond, 01:10
  • Re: [Lilypond-auto] Issue 2699 in lilypond: Patch: Properly implement fromproperty markup handing in the pdftitle header field, lilypond, 01:07
  • Re: [Lilypond-auto] Issue 1661 in lilypond: MIDI dynamics take effect one note too late, lilypond, 00:01
• July 26, 2012
  • Re: [Lilypond-auto] Issue 2692 in lilypond: Patch: Let ly:make-moment accept rationals for main and grace timing, lilypond, 23:57
  • Re: [Lilypond-auto] Issue 2691 in lilypond: Chord names collide with beams (vertical space missing on second line staff), lilypond, 23:56
  • Re: [Lilypond-auto] Issue 2690 in lilypond: \tweak warning re tied chord no longer applies, lilypond, 23:55
  • Re: [Lilypond-auto] Issue 2672 in lilypond: Patch: Midi fixes, lilypond, 23:54
  • Re: [Lilypond-auto] Issue 2664 in lilypond: stringTunings snippet in NR 2.4.1, lilypond, 23:53
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 23:52
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 23:26
  • [Lilypond-auto] Issue 2699 in lilypond: Patch: Properly implement fromproperty markup handing in the pdftitle header field, lilypond, 20:49
  • Re: [Lilypond-auto] Issue 1650 in lilypond: using multiple \header in a block prints only the latest items, lilypond, 18:50
  • Re: [Lilypond-auto] Issue 1650 in lilypond: using multiple \header in a block prints only the latest items, lilypond, 18:49
  • Re: [Lilypond-auto] Issue 1132 in lilypond: Header oddity, lilypond, 18:48
  • Re: [Lilypond-auto] Issue 1132 in lilypond: Header oddity, lilypond, 18:44
  • Re: [Lilypond-auto] Issue 1650 in lilypond: using multiple \header in a block prints only the latest items, lilypond, 18:38
  • Re: [Lilypond-auto] Issue 2640 in lilypond: doc enhancement for \headers, lilypond, 17:41
  • Re: [Lilypond-auto] Issue 2640 in lilypond: doc enhancement for \headers, lilypond, 17:25
  • Re: [Lilypond-auto] Issue 2640 in lilypond: doc enhancement for \headers, lilypond, 16:41
  • Re: [Lilypond-auto] Issue 2640 in lilypond: doc enhancement for \headers, lilypond, 16:06
  • Re: [Lilypond-auto] Issue 2640 in lilypond: doc enhancement for \headers, lilypond, 15:37
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 15:35
  • Re: [Lilypond-auto] Issue 2664 in lilypond: stringTunings snippet in NR 2.4.1, lilypond, 12:34
  • Re: [Lilypond-auto] Issue 2691 in lilypond: Chord names collide with beams (vertical space missing on second line staff), lilypond, 12:33
  • Re: [Lilypond-auto] Issue 2698 in lilypond: Patch: Syntax change: don't allow degenerate REAL -., lilypond, 12:24
  • [Lilypond-auto] Patchy email, lilypond-auto, 09:57
  • Re: [Lilypond-auto] Issue 2698 in lilypond: Patch: Syntax change: don't allow degenerate REAL -., lilypond, 03:42
  • Re: [Lilypond-auto] Issue 2698 in lilypond: Patch: Syntax change: don't allow degenerate REAL -., lilypond, 03:41
• July 25, 2012
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 22:34
  • [Lilypond-auto] Patchy email, lilypond-auto, 21:58
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 20:35
  • Re: [Lilypond-auto] Issue 2698 in lilypond: Patch: Syntax change: REAL requires at least one digit before decimal point, lilypond, 18:50
  • Re: [Lilypond-auto] Issue 1999 in lilypond: Nonsensical example in programming-interface.itely, lilypond, 18:07
  • Re: [Lilypond-auto] Issue 1999 in lilypond: Nonsensical example in programming-interface.itely, lilypond, 18:06
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 17:11
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 16:54
  • [Lilypond-auto] Patchy email, lilypond-auto, 15:57
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 15:38
  • [Lilypond-auto] Issue 2698 in lilypond: Patch: Syntax change: REAL requires at least one digit before decimal point, lilypond, 15:27
  • Re: [Lilypond-auto] Issue 2401 in lilypond: NR 1.2.4 - Not working snippet in German translation, lilypond, 14:35
  • Re: [Lilypond-auto] Issue 2695 in lilypond: Bad output in display-lily-tests.ly, lilypond, 14:26
  • Re: [Lilypond-auto] Issue 2695 in lilypond: Bad output in display-lily-tests.ly, lilypond, 14:22
  • Re: [Lilypond-auto] Issue 2696 in lilypond: Patch: 4 issues related to rational duration factors., lilypond, 14:06
  • Re: [Lilypond-auto] Issue 2696 in lilypond: Patch: 4 issues related to rational duration factors., lilypond, 13:03
  • Re: [Lilypond-auto] Issue 2697 in lilypond: Patch: 4 issues related to rational duration factors., lilypond, 13:02
  • [Lilypond-auto] Issue 2697 in lilypond: Patch: 4 issues related to rational duration factors., lilypond, 12:50
  • Re: [Lilypond-auto] Issue 2696 in lilypond: Patch: 4 issues related to rational duration factors., lilypond, 12:05
  • [Lilypond-auto] Issue 2696 in lilypond: Patch: 4 issues related to rational duration factors., lilypond, 12:03
  • Re: [Lilypond-auto] Issue 2522 in lilypond: duration*0 considered harmful, lilypond, 10:55
  • Re: [Lilypond-auto] Issue 2695 in lilypond: Bad output in display-lily-tests.ly, lilypond, 10:53
  • Re: [Lilypond-auto] Issue 2695 in lilypond: Bad output in display-lily-tests.ly, lilypond, 10:36
  • Re: [Lilypond-auto] Issue 2695 in lilypond: Bad output in display-lily-tests.ly, lilypond, 09:48
  • [Lilypond-auto] Issue 2695 in lilypond: Bad output in display-lily-tests.ly, lilypond, 09:47
  • [Lilypond-auto] Patchy email, lilypond-auto, 08:05
  • Re: [Lilypond-auto] Issue 2679 in lilypond: Add function for overriding broken spanners to LilyPond, lilypond, 07:46
  • [Lilypond-auto] Email from Phil's patchy, phileholmes, 05:54
  • Re: [Lilypond-auto] Issue 2401 in lilypond: NR 1.2.4 - Not working snippet in German translation, lilypond, 05:15
  • Re: [Lilypond-auto] Issue 2688 in lilypond: Patch: Add ly:context-mod-apply! function., lilypond, 01:22
  • Re: [Lilypond-auto] Issue 2584 in lilypond: please make partcombine merge slurs, lilypond, 01:21
  • Re: [Lilypond-auto] Issue 2688 in lilypond: Patch: Add ly:context-mod-apply! function., lilypond, 01:18
  • Re: [Lilypond-auto] Issue 2401 in lilypond: NR 1.2.4 - Not working snippet in German translation, lilypond, 00:48
• July 24, 2012
  • Re: [Lilypond-auto] Issue 2693 in lilypond: Patch: Documentation for cross staff stems, lilypond, 22:19
  • Re: [Lilypond-auto] Issue 2688 in lilypond: Patch: Add ly:context-mod-apply! function., lilypond, 22:02
  • Re: [Lilypond-auto] Issue 2584 in lilypond: please make partcombine merge slurs, lilypond, 22:01
  • Re: [Lilypond-auto] Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 22:00
  • [Lilypond-auto] Patchy email, lilypond-auto, 21:57
  • Re: [Lilypond-auto] Issue 2651 in lilypond: Patch: web: Linux => GNU/Linux. English only., lilypond, 18:02
  • Re: [Lilypond-auto] Issue 673 in lilypond: problem with order of \consists, lilypond, 17:59
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 16:38
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 16:29
  • Re: [Lilypond-auto] Issue 2673 in lilypond: Volta improvements, lilypond, 16:22
  • [Lilypond-auto] Patchy email, lilypond-auto, 15:56
  • Re: [Lilypond-auto] Issue 2673 in lilypond: Volta improvements, lilypond, 15:45
  • Re: [Lilypond-auto] Issue 2673 in lilypond: Volta improvements, lilypond, 15:44
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 15:43
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 15:39
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 14:40
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 14:36
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 14:29
  • [Lilypond-auto] Email from Phil's patchy, phileholmes, 14:07
  • Re: [Lilypond-auto] Issue 2428 in lilypond: symbol is shifted to the left and only partly visible in the snippet output, lilypond, 12:41
  • [Lilypond-auto] Patchy email, phileholmes, 12:37
  • Re: [Lilypond-auto] Issue 2651 in lilypond: Patch: web: Linux => GNU/Linux. English only., lilypond, 12:28
  • Re: [Lilypond-auto] Issue 2651 in lilypond: Patch: web: Linux => GNU/Linux. English only., lilypond, 11:53
  • Re: [Lilypond-auto] Issue 2662 in lilypond: lsr #3 output does not correspond to the description, lilypond, 11:45
  • Re: [Lilypond-auto] Issue 2673 in lilypond: Volta improvements, lilypond, 10:01
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 07:54
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 05:37
  • Re: [Lilypond-auto] Issue 2664 in lilypond: stringTunings snippet in NR 2.4.1, lilypond, 04:32
  • Re: [Lilypond-auto] Issue 1661 in lilypond: MIDI dynamics take effect one note too late, lilypond, 04:04
  • Re: [Lilypond-auto] Issue 2664 in lilypond: stringTunings snippet in NR 2.4.1, lilypond, 03:44
  • Re: [Lilypond-auto] Issue 2672 in lilypond: Patch: Midi fixes, lilypond, 03:34
  • Re: [Lilypond-auto] Issue 2693 in lilypond: Patch: Documentation for cross staff stems, lilypond, 03:31
  • Re: [Lilypond-auto] Issue 2664 in lilypond: stringTunings snippet in NR 2.4.1, lilypond, 02:43
  • Re: [Lilypond-auto] Issue 2672 in lilypond: Patch: Midi fixes, lilypond, 02:08
  • Re: [Lilypond-auto] Issue 1661 in lilypond: MIDI dynamics take effect one note too late, lilypond, 01:38
  • Re: [Lilypond-auto] Issue 34 in lilypond: Grace synchronization, lilypond, 01:20
  • Re: [Lilypond-auto] Issue 1661 in lilypond: MIDI dynamics take effect one note too late, lilypond, 01:13
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 00:38
  • Re: [Lilypond-auto] Issue 2672 in lilypond: Patch: Midi fixes, lilypond, 00:22
• July 23, 2012
  • Re: [Lilypond-auto] Issue 1316 in lilypond: Enhancement: improved << \\ >> polyphonic shortcut notation, lilypond, 22:27
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 19:59
  • [Lilypond-auto] Issue 2694 in lilypond: Bar engraver bug or wrong description, lilypond, 18:43
  • Re: [Lilypond-auto] Issue 2664 in lilypond: stringTunings snippet in NR 2.4.1, lilypond, 17:53
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 17:42
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 17:08
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 16:45
  • [Lilypond-auto] Patchy email, lilypond-auto, 15:57
  • Re: [Lilypond-auto] Issue 2664 in lilypond: stringTunings snippet in NR 2.4.1, lilypond, 12:53
  • [Lilypond-auto] Patchy email, lilypond-auto, 12:45
  • Re: [Lilypond-auto] Issue 2664 in lilypond: stringTunings snippet in NR 2.4.1, lilypond, 12:23
  • [Lilypond-auto] Issue 2693 in lilypond: Patch: Documentation for cross staff stems, lilypond, 11:59
  • Re: [Lilypond-auto] Issue 2673 in lilypond: Volta improvements, lilypond, 10:08
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 09:09
  • Re: [Lilypond-auto] Issue 2690 in lilypond: \tweak warning re tied chord no longer applies, lilypond, 08:44
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 07:54
  • Re: [Lilypond-auto] Issue 2691 in lilypond: Chord names collide with beams (vertical space missing on second line staff), lilypond, 07:25
  • Re: [Lilypond-auto] Issue 2692 in lilypond: Patch: Let ly:make-moment accept rationals for main and grace timing, lilypond, 07:14
  • Re: [Lilypond-auto] Issue 2692 in lilypond: Patch: Let ly:make-moment accept rationals for main and grace timing, lilypond, 07:13
  • [Lilypond-auto] Issue 2692 in lilypond: Patch: Let ly:make-moment accept rationals for main and grace timing, lilypond, 06:29
  • Re: [Lilypond-auto] Issue 1999 in lilypond: Nonsensical example in programming-interface.itely, lilypond, 06:22
  • Re: [Lilypond-auto] Issue 1999 in lilypond: Nonsensical example in programming-interface.itely, lilypond, 06:04
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 05:32
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 05:22
  • [Lilypond-auto] Patchy email, lilypond-auto, 04:45
  • Re: [Lilypond-auto] Issue 2690 in lilypond: \tweak warning re tied chord no longer applies, lilypond, 03:16
  • Re: [Lilypond-auto] Issue 2690 in lilypond: \tweak warning re tied chord no longer applies, lilypond, 03:15
  • [Lilypond-auto] Patchy email, lilypond-auto, 02:43
  • Re: [Lilypond-auto] Issue 2671 in lilypond: Patch: Provide functions ly:moment-main and ly:moment-grace, lilypond, 02:25
  • Re: [Lilypond-auto] Issue 2691 in lilypond: Chord names collide with beams (vertical space missing on second line staff), lilypond, 02:17
  • Re: [Lilypond-auto] Issue 2612 in lilypond: Patch: Issues warning for negative-spanning line spanner., lilypond, 01:40
• July 22, 2012
  • Re: [Lilypond-auto] Issue 2679 in lilypond: Add function for overriding broken spanners to LilyPond, lilypond, 22:24
  • Re: [Lilypond-auto] Issue 2673 in lilypond: Volta improvements, lilypond, 22:23
  • Re: [Lilypond-auto] Issue 2671 in lilypond: Patch: Provide functions ly:moment-main and ly:moment-grace, lilypond, 22:22
  • Re: [Lilypond-auto] Issue 2612 in lilypond: Patch: Issues warning for negative-spanning line spanner., lilypond, 22:21
  • [Lilypond-auto] Patchy email, lilypond-auto, 19:10
  • Re: [Lilypond-auto] Issue 2691 in lilypond: Chord names collide with beams (vertical space missing on second line staff), lilypond, 14:42
  • Re: [Lilypond-auto] Issue 2217 in lilypond: Chord names collide with notes (vertical space missing on second line staff), lilypond, 14:41
  • Re: [Lilypond-auto] Issue 2691 in lilypond: Chord names collide with beams (vertical space missing on second line staff), lilypond, 14:40
  • [Lilypond-auto] Issue 2691 in lilypond: Chord names collide with beams (vertical space missing on second line staff), lilypond, 12:55
  • Re: [Lilypond-auto] Issue 1015 in lilypond: doc line width, lilypond, 10:00
  • Re: [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 08:32
  • Re: [Lilypond-auto] Issue 1015 in lilypond: doc line width, lilypond, 07:48
  • Re: [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 07:41
  • Re: [Lilypond-auto] Issue 1015 in lilypond: doc line width, lilypond, 07:34
  • Re: [Lilypond-auto] Issue 2690 in lilypond: \tweak warning re tied chord no longer applies, lilypond, 07:30
  • Re: [Lilypond-auto] Issue 1163 in lilypond: website "what we wrote", lilypond, 07:06
  • Re: [Lilypond-auto] Issue 2690 in lilypond: \tweak warning re tied chord no longer applies, lilypond, 07:05
  • Re: [Lilypond-auto] Issue 2645 in lilypond: Patch: Adds support for cross-staff-stems, lilypond, 06:07
  • Re: [Lilypond-auto] Issue 2690 in lilypond: \tweak warning re tied chord no longer applies, lilypond, 04:09
  • Re: [Lilypond-auto] Issue 2690 in lilypond: \tweak warning re tied chord no longer applies, lilypond, 03:50
  • Re: [Lilypond-auto] Issue 2690 in lilypond: \tweak warning re tied chord no longer applies, lilypond, 03:48
  • Re: [Lilypond-auto] Issue 1015 in lilypond: doc line width, lilypond, 01:58
• July 21, 2012
  • Re: [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 20:56
  • Re: [Lilypond-auto] Issue 2690 in lilypond: \tweak warning re tied chord no longer applies, lilypond, 18:35
  • [Lilypond-auto] Issue 2690 in lilypond: \tweak warning re tied chord no longer applies, lilypond, 17:41
  • [Lilypond-auto] Patchy email, lilypond-auto, 10:44
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 10:33
  • Re: [Lilypond-auto] Issue 2689 in lilypond: Patch: Avoid duplication between slur and phrasing slur engravers., lilypond, 09:36
  • Re: [Lilypond-auto] Issue 2688 in lilypond: Patch: Add ly:context-mod-apply! function., lilypond, 09:04
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 09:02
  • Re: [Lilypond-auto] Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 08:59
  • Re: [Lilypond-auto] Issue 2689 in lilypond: Patch: Avoid duplication between slur and phrasing slur engravers., lilypond, 08:46
  • [Lilypond-auto] Issue 2689 in lilypond: Patch: Avoid duplication between slur and phrasing slur engravers., lilypond, 08:44
  • Re: [Lilypond-auto] Issue 2687 in lilypond: distinguish odd and even lyrics lines, lilypond, 08:37
  • Re: [Lilypond-auto] Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 08:29
  • Re: [Lilypond-auto] Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 08:18
  • Re: [Lilypond-auto] Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 08:16
  • Re: [Lilypond-auto] Issue 2688 in lilypond: Patch: Add ly:context-mod-apply! function., lilypond, 06:36
  • [Lilypond-auto] Issue 2688 in lilypond: Patch: Add ly:context-mod-apply! function., lilypond, 06:35
  • Re: [Lilypond-auto] Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 06:16
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 06:03
• July 20, 2012
  • Re: [Lilypond-auto] Issue 2683 in lilypond: Beamlets with incorrect orientation and uneven spacing in beamlet-test.ly, lilypond, 21:37
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 16:39
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 16:35
  • [Lilypond-auto] Issue 2687 in lilypond: distinguish odd and even lyrics lines, lilypond, 16:23
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 16:21
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 16:13
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 15:46
  • Re: [Lilypond-auto] Issue 185 in lilypond: RhythmicStaff squishing chords should produce single notes, lilypond, 15:44
  • Re: [Lilypond-auto] Issue 2665 in lilypond: Span Bars missing with alignAboveContext, lilypond, 14:34
  • Re: [Lilypond-auto] Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 12:12
  • Re: [Lilypond-auto] Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 11:49
  • Re: [Lilypond-auto] Issue 1816 in lilypond: Lilypond-book music runs off right side of the page, lilypond, 11:48
  • Re: [Lilypond-auto] Issue 1816 in lilypond: Lilypond-book music runs off right side of the page, lilypond, 11:48
  • Re: [Lilypond-auto] Issue 1015 in lilypond: doc line width, lilypond, 11:47
  • Re: [Lilypond-auto] Issue 1015 in lilypond: doc line width, lilypond, 11:45
  • Re: [Lilypond-auto] Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 11:45
  • Re: [Lilypond-auto] Issue 766 in lilypond: Indent should automatically adapt to instrument names' length., lilypond, 11:43
  • Re: [Lilypond-auto] Issue 1015 in lilypond: doc line width, lilypond, 11:42
  • Re: [Lilypond-auto] Issue 766 in lilypond: Indent should automatically adapt to instrument names' length., lilypond, 11:41
  • Re: [Lilypond-auto] Issue 2649 in lilypond: Patch: Fixes all black bars in NR, lilypond, 11:35
  • Re: [Lilypond-auto] Issue 1995 in lilypond: scheme-tutorial.itely: avoid unnecessary copying, lilypond, 06:05
  • Re: [Lilypond-auto] Issue 1995 in lilypond: scheme-tutorial.itely: avoid unnecessary copying, lilypond, 05:32
  • Re: [Lilypond-auto] Issue 2513 in lilypond: Patch: Build: add -fno-tree-vrp to CXXFLAGS for gcc 4.7.0, lilypond, 04:54
  • Re: [Lilypond-auto] Issue 2666 in lilypond: Patch: Web: remove non-Free software from Easier Editing, lilypond, 04:52
  • Re: [Lilypond-auto] Issue 2651 in lilypond: Patch: web: Linux => GNU/Linux. English only., lilypond, 04:48
  • Re: [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 04:46
  • [Lilypond-auto] Patchy email, lilypond-auto, 04:44
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 02:59
  • Re: [Lilypond-auto] Issue 2441 in lilypond: Stems no longer adjust for merged note heads, lilypond, 02:37
  • Re: [Lilypond-auto] Issue 2686 in lilypond: Regtest collision-head-solfa-fa shows a change in how the notehead shape affects the up lines, lilypond, 02:36
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 02:16
  • Re: [Lilypond-auto] Issue 2669 in lilypond: Patch: Avoid recreating notename hashes from alists unnecessarily., lilypond, 01:59
  • Re: [Lilypond-auto] Issue 2667 in lilypond: Point and click location of chords for q repeats is inaccurate, lilypond, 01:58
  • Re: [Lilypond-auto] Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 01:57
  • Re: [Lilypond-auto] Issue 2661 in lilypond: Patch: parser.yy: remove `fraction', lilypond, 01:56
  • Re: [Lilypond-auto] Issue 2686 in lilypond: Regtest collision-head-solfa-fa shows a change in how the notehead shape affects the up lines, lilypond, 01:46
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 00:47
  • Re: [Lilypond-auto] Issue 2645 in lilypond: Patch: Adds support for cross-staff-stems, lilypond, 00:31
  • Re: [Lilypond-auto] Issue 2655 in lilypond: TextSpanner disappears after linebreak, lilypond, 00:30
  • Re: [Lilypond-auto] Issue 2666 in lilypond: Patch: Web: remove non-Free software from Easier Editing, lilypond, 00:29
  • Re: [Lilypond-auto] Issue 2661 in lilypond: Patch: parser.yy: remove `fraction', lilypond, 00:28
  • Re: [Lilypond-auto] Issue 2667 in lilypond: Point and click location of chords for q repeats is inaccurate, lilypond, 00:27
  • Re: [Lilypond-auto] Issue 2669 in lilypond: Patch: Avoid recreating notename hashes from alists unnecessarily., lilypond, 00:26
• July 19, 2012
  • Re: [Lilypond-auto] Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 21:46
  • Re: [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 20:37
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 18:22
  • [Lilypond-auto] Issue 2686 in lilypond: Regtest collision-head-solfa-fa shows a change in how the notehead shape affects the up lines, lilypond, 18:08
  • [Lilypond-auto] Issue 2685 in lilypond: Regtest chord-tremolo-articulations shows Changes to shape of forte marking, lilypond, 18:04
  • [Lilypond-auto] Issue 2684 in lilypond: Regtest beam-beat-grouping shows Subtle change in text location, lilypond, 18:03
  • Re: [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 17:55
  • Re: [Lilypond-auto] Issue 2657 in lilypond: font kerning on Windows is broken, lilypond, 17:47
  • Re: [Lilypond-auto] Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 13:52
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 13:37
  • Re: [Lilypond-auto] Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 13:36
  • Re: [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 12:38
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 12:36
  • Re: [Lilypond-auto] Issue 2657 in lilypond: font kerning on Windows is broken, lilypond, 12:14
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 12:03
  • Re: [Lilypond-auto] Issue 2584 in lilypond: please make partcombine merge slurs, lilypond, 10:57
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 10:10
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 09:10
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 08:19
  • Re: [Lilypond-auto] Issue 2584 in lilypond: please make partcombine merge slurs, lilypond, 07:01
  • Re: [Lilypond-auto] Issue 2665 in lilypond: Span Bars missing with alignAboveContext, lilypond, 06:51
  • Re: [Lilypond-auto] Issue 2671 in lilypond: Patch: Provide functions ly:moment-main and ly:moment-grace, lilypond, 06:26
  • Re: [Lilypond-auto] Issue 2673 in lilypond: Volta improvements, lilypond, 06:15
  • Re: [Lilypond-auto] Issue 2679 in lilypond: Add function for overriding broken spanners to LilyPond, lilypond, 05:53
  • [Lilypond-auto] Issue 2683 in lilypond: Beamlets with incorrect orientation and uneven spacing in beamlet-test.ly, lilypond, 05:27
  • [Lilypond-auto] Issue 2682 in lilypond: Collision of notehead and beam in beam-collision-basic.ly regression test, lilypond, 05:15
  • Re: [Lilypond-auto] Issue 2584 in lilypond: please make partcombine merge slurs, lilypond, 05:14
  • Re: [Lilypond-auto] Issue 2648 in lilypond: Repeat Dots and Staff Size in 2.15.41, lilypond, 03:39
  • Re: [Lilypond-auto] Issue 2584 in lilypond: please make partcombine merge slurs, lilypond, 03:24
  • Re: [Lilypond-auto] Issue 2584 in lilypond: please make partcombine merge slurs, lilypond, 02:14
  • Re: [Lilypond-auto] Issue 2584 in lilypond: please make partcombine merge slurs, lilypond, 02:06
• July 18, 2012
  • [Lilypond-auto] Patchy email, lilypond-auto, 20:43
  • Re: [Lilypond-auto] Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 19:37
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 16:51
  • [Lilypond-auto] Issue 2681 in lilypond: Conflict Lilypond - GNUCash on Windows, lilypond, 15:38
  • Re: [Lilypond-auto] Issue 2680 in lilypond: Patch: Correct makelsr handling of local update, lilypond, 15:37
  • Re: [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 13:37
  • Re: [Lilypond-auto] Issue 2657 in lilypond: font kerning on Windows is broken, lilypond, 13:36
  • Re: [Lilypond-auto] Issue 2680 in lilypond: Patch: Correct makelsr handling of local update, lilypond, 13:02
  • [Lilypond-auto] Issue 2680 in lilypond: Patch: Correct makelsr handling of local update, lilypond, 11:58
  • [Lilypond-auto] Patchy email, lilypond-auto, 10:46
  • Re: [Lilypond-auto] Issue 2649 in lilypond: Patch: Fixes all black bars in NR, lilypond, 09:34
  • Re: [Lilypond-auto] Issue 2679 in lilypond: Add function for overriding broken spanners to LilyPond, lilypond, 09:19
  • Re: [Lilypond-auto] Issue 2674 in lilypond: Add function for overriding broken spanners to LilyPond, lilypond, 09:18
  • Re: [Lilypond-auto] Issue 2674 in lilypond: Add function for overriding broken spanners to LilyPond, lilypond, 09:17
  • Re: [Lilypond-auto] Issue 2679 in lilypond: Add function for overriding broken spanners to LilyPond, lilypond, 09:16
  • Re: [Lilypond-auto] Issue 2679 in lilypond: Add function for overriding broken spanners to LilyPond, lilypond, 09:15
  • Re: [Lilypond-auto] Issue 2675 in lilypond: Add function for overriding broken spanners to LilyPond, lilypond, 09:14
  • Re: [Lilypond-auto] Issue 2676 in lilypond: Add function for overriding broken spanners to LilyPond, lilypond, 09:13
  • Re: [Lilypond-auto] Issue 2674 in lilypond: Add function for overriding broken spanners to LilyPond, lilypond, 09:09
  • Re: [Lilypond-auto] Issue 2654 in lilypond: Patch: Check in Texinfo 2012-07-03.16, lilypond, 09:08
  • Re: [Lilypond-auto] Issue 2649 in lilypond: Patch: Fixes all black bars in NR, lilypond, 09:07
  • Re: [Lilypond-auto] Issue 2674 in lilypond: Add function for overriding broken spanners to LilyPond, lilypond, 09:04
  • Re: [Lilypond-auto] Issue 2657 in lilypond: font kerning on Windows is broken, lilypond, 08:56
  • Re: [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 08:55
  • Re: [Lilypond-auto] Issue 2674 in lilypond: Add function for overriding broken spanners to LilyPond, lilypond, 08:53
  • Re: [Lilypond-auto] Issue 2674 in lilypond: Add function for overriding broken spanners to LilyPond, lilypond, 08:51
  • [Lilypond-auto] Issue 2679 in lilypond: Add function for overriding broken spanners to LilyPond, lilypond, 08:51
  • [Lilypond-auto] Issue 2674 in lilypond: Add function for overriding broken spanners to LilyPond, lilypond, 08:48
  • [Lilypond-auto] Issue 2676 in lilypond: Add function for overriding broken spanners to LilyPond, lilypond, 08:47
  • [Lilypond-auto] Issue 2677 in lilypond: Add function for overriding broken spanners to LilyPond, lilypond, 08:46
  • [Lilypond-auto] Issue 2678 in lilypond: Add function for overriding broken spanners to LilyPond, lilypond, 08:45
  • [Lilypond-auto] Patchy email, lilypond-auto, 08:44
  • [Lilypond-auto] Issue 2675 in lilypond: Add function for overriding broken spanners to LilyPond, lilypond, 08:44
  • Re: [Lilypond-auto] Issue 2665 in lilypond: Span Bars missing with alignAboveContext, lilypond, 01:27
  • Re: [Lilypond-auto] Issue 1163 in lilypond: website "what we wrote", lilypond, 00:23
• July 17, 2012
  • Re: [Lilypond-auto] Issue 2654 in lilypond: Patch: Check in Texinfo 2012-07-03.16, lilypond, 22:43
  • Re: [Lilypond-auto] Issue 2649 in lilypond: Patch: Fixes all black bars in NR, lilypond, 22:40
  • [Lilypond-auto] Patchy email, lilypond-auto, 18:44
  • [Lilypond-auto] Patchy email, lilypond-auto, 16:44
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 15:44
  • [Lilypond-auto] Patchy email, lilypond-auto, 14:19
  • Re: [Lilypond-auto] Issue 2673 in lilypond: Volta improvements, lilypond, 13:38
  • Re: [Lilypond-auto] Issue 2673 in lilypond: Volta improvements, lilypond, 13:36
  • Re: [Lilypond-auto] Issue 2673 in lilypond: Volta improvements, lilypond, 12:52
  • [Lilypond-auto] Issue 2673 in lilypond: Volta improvements, lilypond, 12:45
  • Re: [Lilypond-auto] Issue 1661 in lilypond: MIDI dynamics take effect one note too late, lilypond, 12:22
  • [Lilypond-auto] Issue 2672 in lilypond: Patch: Midi fixes, lilypond, 12:22
  • Re: [Lilypond-auto] Issue 1163 in lilypond: website "what we wrote", lilypond, 12:01
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 11:11
  • Re: [Lilypond-auto] Issue 2428 in lilypond: symbol is shifted to the left and only partly visible in the snippet output, lilypond, 07:13
  • Re: [Lilypond-auto] Issue 2654 in lilypond: Patch: Check in Texinfo 2012-07-03.16, lilypond, 06:54
  • Re: [Lilypond-auto] Issue 2428 in lilypond: symbol is shifted to the left and only partly visible in the snippet output, lilypond, 06:50
  • Re: [Lilypond-auto] Issue 2428 in lilypond: symbol is shifted to the left and only partly visible in the snippet output, lilypond, 06:34
  • Re: [Lilypond-auto] Issue 2428 in lilypond: symbol is shifted to the left and only partly visible in the snippet output, lilypond, 06:14
  • Re: [Lilypond-auto] Issue 2671 in lilypond: Patch: Provide functions ly:moment-main and ly:moment-grace, lilypond, 05:42
  • [Lilypond-auto] Issue 2671 in lilypond: Patch: Provide functions ly:moment-main and ly:moment-grace, lilypond, 05:40
  • [Lilypond-auto] Issue 2670 in lilypond: change default behavior of convert-ly, lilypond, 05:23
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 05:10
  • Re: [Lilypond-auto] Issue 2653 in lilypond: Midi output does not respect tied notes, lilypond, 04:02
  • Re: [Lilypond-auto] Issue 2653 in lilypond: Midi output does not respect tied notes, lilypond, 03:49
  • Re: [Lilypond-auto] Issue 2653 in lilypond: Midi output does not respect tied notes, lilypond, 03:32
  • Re: [Lilypond-auto] Issue 2653 in lilypond: Midi output does not respect tied notes, lilypond, 03:22
  • Re: [Lilypond-auto] Issue 2653 in lilypond: Midi output does not respect tied notes, lilypond, 03:08
  • Re: [Lilypond-auto] Issue 2653 in lilypond: Midi output does not respect tied notes, lilypond, 02:45
  • Re: [Lilypond-auto] Issue 2653 in lilypond: Midi output does not respect tied notes, lilypond, 02:41
  • Re: [Lilypond-auto] Issue 2665 in lilypond: Span Bars missing with alignAboveContext, lilypond, 00:42
  • Re: [Lilypond-auto] Issue 2655 in lilypond: TextSpanner disappears after linebreak, lilypond, 00:38
• July 16, 2012
  • Re: [Lilypond-auto] Issue 2665 in lilypond: Span Bars missing with alignAboveContext, lilypond, 21:10
  • Re: [Lilypond-auto] Issue 2653 in lilypond: Midi output does not respect tied notes, lilypond, 19:50
  • Re: [Lilypond-auto] Issue 2653 in lilypond: Midi output does not respect tied notes, lilypond, 19:12
  • Re: [Lilypond-auto] Issue 2653 in lilypond: Midi output does not respect tied notes, lilypond, 17:52
  • Re: [Lilypond-auto] Issue 2653 in lilypond: Midi output does not respect tied notes, lilypond, 16:21
  • Re: [Lilypond-auto] Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 16:17
  • Re: [Lilypond-auto] Issue 2645 in lilypond: Patch: Adds support for cross-staff-stems, lilypond, 16:14
  • Re: [Lilypond-auto] Issue 2666 in lilypond: Patch: Web: remove non-Free software from Easier Editing, lilypond, 16:11
  • Re: [Lilypond-auto] Issue 2667 in lilypond: Point and click location of chords for q repeats is inaccurate, lilypond, 16:10
  • Re: [Lilypond-auto] Issue 2653 in lilypond: Midi output does not respect tied notes, lilypond, 15:45
  • Re: [Lilypond-auto] Issue 2669 in lilypond: Patch: Avoid recreating notename hashes from alists unnecessarily., lilypond, 14:36
  • Re: [Lilypond-auto] Issue 2669 in lilypond: Patch: Avoid recreating notename hashes from alists unnecessarily., lilypond, 14:17
  • [Lilypond-auto] Issue 2669 in lilypond: Patch: Avoid recreating notename hashes from alists unnecessarily., lilypond, 13:52
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 13:31
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 13:22
  • Re: [Lilypond-auto] Issue 2655 in lilypond: TextSpanner disappears after linebreak, lilypond, 13:21
  • Re: [Lilypond-auto] Issue 2661 in lilypond: Patch: parser.yy: remove `fraction', lilypond, 13:20
  • Re: [Lilypond-auto] Issue 2653 in lilypond: Midi output does not respect tied notes, lilypond, 12:56
  • Re: [Lilypond-auto] Issue 2653 in lilypond: Midi output does not respect tied notes, lilypond, 12:34
  • Re: [Lilypond-auto] Issue 1163 in lilypond: website "what we wrote", lilypond, 12:02
  • Re: [Lilypond-auto] Issue 2664 in lilypond: stringTunings snippet in NR 2.4.1, lilypond, 11:58
  • Re: [Lilypond-auto] Issue 2668 in lilypond: Accidental rules should first be cleared when being reset, lilypond, 11:24
  • Re: [Lilypond-auto] Issue 2178 in lilypond: NR: clarify the subsection "Automatic accidentals" of section 1.1.3, lilypond, 11:23
  • [Lilypond-auto] Issue 2668 in lilypond: Accidental rules should first be cleared when being reset, lilypond, 11:21
  • Re: [Lilypond-auto] Issue 2178 in lilypond: NR: clarify the subsection "Automatic accidentals" of section 1.1.3, lilypond, 11:15
  • Re: [Lilypond-auto] Issue 2667 in lilypond: Point and click location of chords for q repeats is inaccurate, lilypond, 11:08
  • Re: [Lilypond-auto] Issue 2667 in lilypond: Point and click location of chords for q repeats is inaccurate, lilypond, 11:07
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 10:35
  • [Lilypond-auto] Patchy email, lilypond-auto, 07:33
  • Re: [Lilypond-auto] Issue 2178 in lilypond: NR: clarify the subsection "Automatic accidentals" of section 1.1.3, lilypond, 06:40
  • Re: [Lilypond-auto] Issue 2639 in lilypond: lilypond-book titles corrupted when exported to pdfs, lilypond, 06:33
  • Re: [Lilypond-auto] Issue 2178 in lilypond: NR: clarify the subsection "Automatic accidentals" of section 1.1.3, lilypond, 06:17
  • Re: [Lilypond-auto] Issue 2667 in lilypond: Point and click location of chords for q repeats is inaccurate, lilypond, 05:47
  • [Lilypond-auto] Issue 2667 in lilypond: Point and click location of chords for q repeats is inaccurate, lilypond, 05:23
  • Re: [Lilypond-auto] Issue 2650 in lilypond: Patch: Rewrite incipit snippet using #{ ... #} in preference to Scheme, lilypond, 05:02
  • Re: [Lilypond-auto] Issue 2322 in lilypond: Document use of property-setting music in output definitions, lilypond, 04:32
  • [Lilypond-auto] Issue 2666 in lilypond: Patch: Web: remove non-Free software from Easier Editing, lilypond, 02:40
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 02:06
  • Re: [Lilypond-auto] Issue 2322 in lilypond: Document use of property-setting music in output definitions, lilypond, 00:42
  • Re: [Lilypond-auto] Issue 2650 in lilypond: Patch: Rewrite incipit snippet using #{ ... #} in preference to Scheme, lilypond, 00:41
• July 15, 2012
  • [Lilypond-auto] Issue 2665 in lilypond: Span Bars missing with alignAboveContext, lilypond, 22:40
  • Re: [Lilypond-auto] Issue 1163 in lilypond: website "what we wrote", lilypond, 19:32
  • [Lilypond-auto] Issue 2664 in lilypond: stringTunings snippet in NR 2.4.1, lilypond, 17:56
  • Re: [Lilypond-auto] Issue 2410 in lilypond: Doc: Translation German NR 5.1.4 - Typo for engraver type, lilypond, 17:14
  • Re: [Lilypond-auto] Issue 1163 in lilypond: website "what we wrote", lilypond, 16:47
  • [Lilypond-auto] Patchy email, lilypond-auto, 14:42
  • Re: [Lilypond-auto] Issue 2599 in lilypond: Use of autochange, lilypond, 13:45
  • Re: [Lilypond-auto] Issue 2644 in lilypond: Inconsistency in documentation for baseMoment, lilypond, 12:49
  • [Lilypond-auto] Issue 2663 in lilypond: add a command to tell LilyPond where on the staff to change the direction of stem or beams, lilypond, 10:33
  • [Lilypond-auto] Patchy email, lilypond-auto, 08:42
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 07:32
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 07:26
  • Re: [Lilypond-auto] Issue 1320 in lilypond: Enhancement: user-customizable barlines through a Scheme interface., lilypond, 07:20
  • Re: [Lilypond-auto] Issue 2662 in lilypond: lsr #3 output does not correspond to the description, lilypond, 06:51
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 06:41
  • Re: [Lilypond-auto] Issue 2662 in lilypond: lsr #3 output does not correspond to the description, lilypond, 06:39
  • Re: [Lilypond-auto] Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 05:47
  • Re: [Lilypond-auto] Issue 2655 in lilypond: TextSpanner disappears after linebreak, lilypond, 03:24
  • Re: [Lilypond-auto] Issue 2655 in lilypond: TextSpanner disappears after linebreak, lilypond, 01:11
• July 14, 2012
  • [Lilypond-auto] Patchy email, lilypond-auto, 22:43
  • Re: [Lilypond-auto] Issue 2585 in lilypond: current po breaks GUB, lilypond, 21:53
  • Re: [Lilypond-auto] Issue 2655 in lilypond: TextSpanner disappears after linebreak, lilypond, 21:39
  • Re: [Lilypond-auto] Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 21:36
  • Re: [Lilypond-auto] Issue 2634 in lilypond: aclocal.m4 incorrectly remove parts of python-cflags output, lilypond, 20:26
  • Re: [Lilypond-auto] Issue 2635 in lilypond: Configure search for NCSB fonts does not work in Debian Squeeze, lilypond, 20:25
  • Re: [Lilypond-auto] Issue 2628 in lilypond: Patch: Clean fonts and docs makefiles, trying to fix 'make -j' race conditions, lilypond, 20:18
  • Re: [Lilypond-auto] Issue 2628 in lilypond: Patch: Clean fonts and docs makefiles, trying to fix 'make -j' race conditions, lilypond, 20:17
  • Re: [Lilypond-auto] Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 20:13
  • Re: [Lilypond-auto] Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 20:08
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 20:03
  • [Lilypond-auto] Issue 2662 in lilypond: lsr #3 output does not correspond to the description, lilypond, 18:41
  • [Lilypond-auto] Patchy email, lilypond-auto, 16:42
  • Re: [Lilypond-auto] Issue 2655 in lilypond: TextSpanner disappears after linebreak, lilypond, 14:56
  • Re: [Lilypond-auto] Issue 2533 in lilypond: Patch: line_count fixes, lilypond, 14:46
  • Re: [Lilypond-auto] Issue 2648 in lilypond: Repeat Dots and Staff Size in 2.15.41, lilypond, 14:42
  • Re: [Lilypond-auto] Issue 2441 in lilypond: Stems no longer adjust for merged note heads, lilypond, 14:40
  • Re: [Lilypond-auto] Issue 2645 in lilypond: Patch: Adds support for cross-staff-stems, lilypond, 11:21
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 10:58
  • Re: [Lilypond-auto] Issue 2570 in lilypond: Add the one-line-breaking page-breaking algorithm., lilypond, 10:21
  • Re: [Lilypond-auto] Issue 2452 in lilypond: consonant prepositions in Lyrics should be placed to the left of the note, lilypond, 10:19
  • Re: [Lilypond-auto] Issue 2453 in lilypond: Long syllables shouldn't be centered under notes, lilypond, 10:18
  • Re: [Lilypond-auto] Issue 2453 in lilypond: Long syllables shouldn't be centered under notes, lilypond, 10:17
  • Re: [Lilypond-auto] Issue 2463 in lilypond: Lyrics: add "hard" (always visible) hyphens, lilypond, 10:16
  • Re: [Lilypond-auto] Issue 2613 in lilypond: Patch: add general_alignment method (Rietveld 6308093), lilypond, 10:15
  • Re: [Lilypond-auto] Issue 2641 in lilypond: Patch: Add documentation for ly:one-line-breaking., lilypond, 10:14
  • Re: [Lilypond-auto] Issue 2646 in lilypond: Parenthesizing multi measure rests, lilypond, 10:08
  • Re: [Lilypond-auto] Issue 2643 in lilypond: Attach lilypond source in pdf, lilypond, 09:09
  • Re: [Lilypond-auto] Issue 2148 in lilypond: vertical skylines should use stencil integrals, lilypond, 08:28
  • Re: [Lilypond-auto] Issue 2148 in lilypond: vertical skylines should use stencil integrals, lilypond, 05:48
  • Re: [Lilypond-auto] Issue 2148 in lilypond: vertical skylines should use stencil integrals, lilypond, 05:46
  • Re: [Lilypond-auto] Issue 2661 in lilypond: Patch: parser.yy: remove `fraction', lilypond, 05:32
  • [Lilypond-auto] Issue 2661 in lilypond: Patch: parser.yy: remove `fraction', lilypond, 05:20
  • Re: [Lilypond-auto] Issue 2655 in lilypond: TextSpanner disappears after linebreak, lilypond, 04:42
  • Re: [Lilypond-auto] Issue 2648 in lilypond: Repeat Dots and Staff Size in 2.15.41, lilypond, 03:50
  • Re: [Lilypond-auto] Issue 2646 in lilypond: Parenthesizing multi measure rests, lilypond, 03:12
  • Re: [Lilypond-auto] Issue 2655 in lilypond: TextSpanner disappears after linebreak, lilypond, 02:12
  • Re: [Lilypond-auto] Issue 2654 in lilypond: Patch: Check in Texinfo 2012-07-03.16, lilypond, 01:13
• July 13, 2012
  • Re: [Lilypond-auto] Issue 2646 in lilypond: Parenthesizing multi measure rests, lilypond, 23:42
  • Re: [Lilypond-auto] Issue 2654 in lilypond: Patch: Check in Texinfo 2012-07-03.16, lilypond, 23:37
  • [Lilypond-auto] Issue 2660 in lilypond: add website link to tunefl.com, lilypond, 23:22
  • [Lilypond-auto] Patchy email, lilypond-auto, 18:43
  • Re: [Lilypond-auto] Issue 2645 in lilypond: Patch: Adds support for cross-staff-stems, lilypond, 18:27
  • Re: [Lilypond-auto] Issue 2646 in lilypond: Parenthesizing multi measure rests, lilypond, 17:05
  • Re: [Lilypond-auto] Issue 2641 in lilypond: Patch: Add documentation for ly:one-line-breaking., lilypond, 16:18
  • [Lilypond-auto] Issue 2659 in lilypond: hairpin - bound-padding doesn't work sometimes, lilypond, 16:15
  • [Lilypond-auto] Issue 2658 in lilypond: wrong stem rendering (inconsistent thickness), lilypond, 16:09
  • [Lilypond-auto] Issue 2657 in lilypond: font kerning on Windows is broken, lilypond, 15:57
  • [Lilypond-auto] Issue 2656 in lilypond: font ligatures don't work on Windows, lilypond, 15:56
  • [Lilypond-auto] Issue 2655 in lilypond: TextSpanner disappears after linebreak, lilypond, 14:03
  • Re: [Lilypond-auto] Issue 2654 in lilypond: Patch: Check in Texinfo 2012-07-03.16, lilypond, 13:03
  • Re: [Lilypond-auto] Issue 2654 in lilypond: Patch: Check in Texinfo 2012-07-03.16, lilypond, 13:02
  • Re: [Lilypond-auto] Issue 2654 in lilypond: Patch: Check in Texinfo 2012-07-03.16, lilypond, 12:57
  • [Lilypond-auto] Issue 2654 in lilypond: Patch: Check in Texinfo 2012-07-03.16, lilypond, 12:56
  • Re: [Lilypond-auto] Issue 2474 in lilypond: tuplet beaming may be confusing, lilypond, 12:31
  • Re: [Lilypond-auto] Issue 2474 in lilypond: tuplet beaming may be confusing, lilypond, 12:03
  • Re: [Lilypond-auto] Issue 2591 in lilypond: NR: repeat slurs and glissando workaround, lilypond, 11:11
  • Re: [Lilypond-auto] Issue 2591 in lilypond: NR: repeat slurs and glissando workaround, lilypond, 09:22
  • Re: [Lilypond-auto] Issue 2591 in lilypond: NR: repeat slurs and glissando workaround, lilypond, 09:15
  • Re: [Lilypond-auto] Issue 2645 in lilypond: Patch: Adds support for cross-staff-stems, lilypond, 07:35
  • Re: [Lilypond-auto] Issue 2645 in lilypond: Patch: Adds support for cross-staff-stems, lilypond, 07:34
  • [Lilypond-auto] Patchy email, lilypond-auto, 06:45
  • Re: [Lilypond-auto] Issue 2474 in lilypond: tuplet beaming may be confusing, lilypond, 04:34
  • Re: [Lilypond-auto] Issue 2474 in lilypond: tuplet beaming may be confusing, lilypond, 03:16
  • Re: [Lilypond-auto] Issue 2474 in lilypond: tuplet beaming may be confusing, lilypond, 01:09
  • Re: [Lilypond-auto] Issue 2474 in lilypond: tuplet beaming may be confusing, lilypond, 00:47
• July 12, 2012
  • Re: [Lilypond-auto] Issue 2634 in lilypond: aclocal.m4 incorrectly remove parts of python-cflags output, lilypond, 22:59
  • Re: [Lilypond-auto] Issue 2641 in lilypond: Patch: Add documentation for ly:one-line-breaking., lilypond, 22:58
  • [Lilypond-auto] Issue 2653 in lilypond: Midi output does not respect tied notes, lilypond, 16:54
  • [Lilypond-auto] Issue 2652 in lilypond: If the book only has a single score, the \header block may be placed inside or outside of the \score block, lilypond, 16:13
  • Re: [Lilypond-auto] Issue 2650 in lilypond: Patch: Rewrite incipit snippet using #{ ... #} in preference to Scheme, lilypond, 15:52
  • Re: [Lilypond-auto] Issue 2322 in lilypond: Document use of property-setting music in output definitions, lilypond, 15:51
  • Re: [Lilypond-auto] Issue 2401 in lilypond: NR 1.2.4 - Not working snippet in German translation, lilypond, 12:20
  • [Lilypond-auto] Patchy email, lilypond-auto, 10:48
  • Re: [Lilypond-auto] Issue 2322 in lilypond: Document use of property-setting music in output definitions, lilypond, 09:00
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 08:58
  • Re: [Lilypond-auto] Issue 2651 in lilypond: Patch: web: Linux => GNU/Linux. English only., lilypond, 08:48
  • [Lilypond-auto] Issue 2651 in lilypond: Patch: web: Linux => GNU/Linux. English only., lilypond, 08:43
  • [Lilypond-auto] Patchy email, lilypond-auto, 08:03
  • Re: [Lilypond-auto] Issue 1719 in lilypond: list of places to send release announcements, lilypond, 08:00
  • [Lilypond-auto] Issue 2650 in lilypond: Patch: Rewrite incipit snippet using #{ ... #} in preference to Scheme, lilypond, 07:21
  • Re: [Lilypond-auto] Issue 2563 in lilypond: Link to PostScript Language Reference broken, lilypond, 04:30
  • Re: [Lilypond-auto] Issue 2401 in lilypond: NR 1.2.4 - Not working snippet in German translation, lilypond, 00:48
  • Re: [Lilypond-auto] Issue 2563 in lilypond: Link to PostScript Language Reference broken, lilypond, 00:11
• July 11, 2012
  • Re: [Lilypond-auto] Issue 2322 in lilypond: Document use of property-setting music in output definitions, lilypond, 16:55
  • [Lilypond-auto] Patchy email, lilypond-auto, 16:42
  • Re: [Lilypond-auto] Issue 2474 in lilypond: tuplet beaming may be confusing, lilypond, 16:20
  • Re: [Lilypond-auto] Issue 2322 in lilypond: Document use of property-setting music in output definitions, lilypond, 12:24
  • Re: [Lilypond-auto] Issue 2649 in lilypond: Patch: Fixes all black bars in NR, lilypond, 12:23
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 09:58
  • Re: [Lilypond-auto] Issue 2322 in lilypond: Document use of property-setting music in output definitions, lilypond, 09:50
  • [Lilypond-auto] Issue 2649 in lilypond: Patch: Fixes all black bars in NR, lilypond, 09:49
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 09:03
  • Re: [Lilypond-auto] Issue 2146 in lilypond: Error: Illegal entry in bfrange block in ToUnicode CMap, lilypond, 08:28
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 07:47
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 07:37
  • Re: [Lilypond-auto] Issue 2322 in lilypond: Document use of property-setting music in output definitions, lilypond, 06:28
  • Re: [Lilypond-auto] Issue 2322 in lilypond: Document use of property-setting music in output definitions, lilypond, 05:31
  • [Lilypond-auto] Patchy email, lilypond-auto, 04:42
  • Re: [Lilypond-auto] Issue 2487 in lilypond: LyX integration of lilypond, lilypond, 03:03
  • Re: [Lilypond-auto] Issue 2557 in lilypond: alignAboveContext was removed from the NR, lilypond, 03:01
  • Re: [Lilypond-auto] Issue 2560 in lilypond: Documentation suggestion (was: strange behaviour of \layout block variable), lilypond, 02:59
  • Re: [Lilypond-auto] Issue 2579 in lilypond: doc enhancement: on-the-fly specifications, lilypond, 02:53
• July 10, 2012
  • Re: [Lilypond-auto] Issue 2635 in lilypond: Configure search for NCSB fonts does not work in Debian Squeeze, lilypond, 23:04
  • Re: [Lilypond-auto] Issue 2579 in lilypond: doc enhancement: on-the-fly specifications, lilypond, 23:03
  • Re: [Lilypond-auto] Issue 2560 in lilypond: Documentation suggestion (was: strange behaviour of \layout block variable), lilypond, 23:02
  • Re: [Lilypond-auto] Issue 2557 in lilypond: alignAboveContext was removed from the NR, lilypond, 23:01
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 19:55
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 19:16
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 18:26
  • Re: [Lilypond-auto] Issue 2648 in lilypond: Repeat Dots and Staff Size in 2.15.41, lilypond, 17:16
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 16:42
  • Re: [Lilypond-auto] Issue 2634 in lilypond: aclocal.m4 incorrectly remove parts of python-cflags output, lilypond, 16:00
  • Re: [Lilypond-auto] Issue 2474 in lilypond: tuplet beaming may be confusing, lilypond, 13:07
  • Re: [Lilypond-auto] Issue 2487 in lilypond: LyX integration of lilypond, lilypond, 11:59
  • Re: [Lilypond-auto] Issue 2537 in lilypond: musicxml2ly: chordnames-placement-bug, lilypond, 11:57
  • Re: [Lilypond-auto] Issue 2596 in lilypond: Patch: Protect a few events from gc., lilypond, 11:55
  • Re: [Lilypond-auto] Issue 2522 in lilypond: duration*0 considered harmful, lilypond, 11:41
  • Re: [Lilypond-auto] Issue 492 in lilypond: piano pedal disappears during RehearsalMark, lilypond, 11:40
  • Re: [Lilypond-auto] Issue 1976 in lilypond: Patch: Handle quartertone pitch differences in fingering calculations., lilypond, 11:39
  • Re: [Lilypond-auto] Issue 1983 in lilypond: musicxml2ly: single words with punctuation marks in score header lead to compilation failure, lilypond, 11:38
  • Re: [Lilypond-auto] Issue 2317 in lilypond: document Kievan square notation support, lilypond, 11:37
  • Re: [Lilypond-auto] Issue 2415 in lilypond: make doc clean does not delete logfiles, lilypond, 11:36
  • Re: [Lilypond-auto] Issue 2524 in lilypond: Patch: CG: add updating of lilypond.pot in the release process, lilypond, 11:34
  • Re: [Lilypond-auto] Issue 2570 in lilypond: Add the one-line-breaking page-breaking algorithm., lilypond, 11:30
  • Re: [Lilypond-auto] Issue 2577 in lilypond: Patch: CG tweak: some extra info on make doc and doc build times., lilypond, 11:29
  • Re: [Lilypond-auto] Issue 2580 in lilypond: Apparent mistake in output-lib.scm - fine barglyph-alist, lilypond, 11:28
  • Re: [Lilypond-auto] Issue 2584 in lilypond: please make partcombine merge slurs, lilypond, 11:27
  • Re: [Lilypond-auto] Issue 2585 in lilypond: current po breaks GUB, lilypond, 11:25
  • Re: [Lilypond-auto] Issue 2604 in lilypond: LILYPOND_BUILD_DIR, lilypond, 11:24
  • Re: [Lilypond-auto] Issue 2588 in lilypond: Patch: Uses Flag width in slur encompass calculations, lilypond, 11:23
  • Re: [Lilypond-auto] Issue 2598 in lilypond: Patch: Allow brackets and parens to start lyrics, disallow "accents", lilypond, 11:23
  • Re: [Lilypond-auto] Issue 2590 in lilypond: GUB release instructions fail for upload, lilypond, 11:20
  • Re: [Lilypond-auto] Issue 2597 in lilypond: Consecutive melismata possible error in NR, lilypond, 11:18
  • Re: [Lilypond-auto] Issue 2606 in lilypond: Patch: Let cue commands deal consistently with #CENTER direction., lilypond, 11:11
  • Re: [Lilypond-auto] Issue 2607 in lilypond: Patch: Allow immediate Scheme expressions to take multiple values, lilypond, 11:11
  • Re: [Lilypond-auto] Issue 2614 in lilypond: Missing Shebang line in MacOSX instructions, lilypond, 11:09
  • Re: [Lilypond-auto] Issue 2615 in lilypond: Patch: Treat accidentals parentheses as cautionary, lilypond, 11:09
  • Re: [Lilypond-auto] Issue 2619 in lilypond: Remove 'fragment' from ancient.itely, lilypond, 11:08
  • Re: [Lilypond-auto] Issue 2620 in lilypond: Patch: (ly:pitch<? #{ des #} #{ d #}) => #t, lilypond, 11:06
  • Re: [Lilypond-auto] Issue 2621 in lilypond: Patch: Scheme-callable functions should never return SCM_UNDEFINED, lilypond, 11:06
  • Re: [Lilypond-auto] Issue 2622 in lilypond: Patch: Make third argument @var{alter} of ly:make-pitch optional., lilypond, 11:04
  • Re: [Lilypond-auto] Issue 2623 in lilypond: Lilypond-book fails due to include_path.insert call in lilypond-book.py, lilypond, 11:03
  • Re: [Lilypond-auto] Issue 2624 in lilypond: Patch: Bumps Mike to Frog meister, lilypond, 11:02
  • Re: [Lilypond-auto] Issue 2625 in lilypond: Patch: Add blurb about Kievan notation to changes, lilypond, 11:02
  • Re: [Lilypond-auto] Issue 2627 in lilypond: Patch: Include +inf.0 and -inf.0 in conversions of Rational to SCM and back, lilypond, 11:01
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 09:46
  • [Lilypond-auto] Patchy email, lilypond-auto, 06:45
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 06:14
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 06:12
  • Re: [Lilypond-auto] Issue 2634 in lilypond: aclocal.m4 incorrectly remove parts of python-cflags output, lilypond, 05:57
  • Re: [Lilypond-auto] Issue 2648 in lilypond: Repeat Dots and Staff Size in 2.15.41, lilypond, 03:44
  • Re: [Lilypond-auto] Issue 2648 in lilypond: Repeat Dots and Staff Size in 2.15.41, lilypond, 03:15
  • Re: [Lilypond-auto] Issue 2648 in lilypond: Repeat Dots and Staff Size in 2.15.41, lilypond, 01:12
  • Re: [Lilypond-auto] Issue 2441 in lilypond: Stems no longer adjust for merged note heads, lilypond, 01:07
  • Re: [Lilypond-auto] Issue 1327 in lilypond: Slur crosses Flag, lilypond, 01:00
• July 09, 2012
  • Re: [Lilypond-auto] Issue 2647 in lilypond: Doc: Clicking on lilypond example images to obtain source file, lilypond, 19:34
  • [Lilypond-auto] Issue 2648 in lilypond: Repeat Dots and Staff Size in 2.15.41, lilypond, 19:11
  • [Lilypond-auto] Issue 2647 in lilypond: Doc: Clicking on lilypond example images to obtain source file, lilypond, 19:01
  • [Lilypond-auto] Issue 2646 in lilypond: Parenthesizing multi measure rests, lilypond, 18:28
  • Re: [Lilypond-auto] Issue 2474 in lilypond: tuplet beaming may be confusing, lilypond, 16:46
  • Re: [Lilypond-auto] Issue 2645 in lilypond: Patch: Adds support for cross-staff-stems, lilypond, 16:44
  • Re: [Lilypond-auto] Issue 2644 in lilypond: Inconsistency in documentation for baseMoment, lilypond, 14:45
  • Re: [Lilypond-auto] Issue 2148 in lilypond: vertical skylines should use stencil integrals, lilypond, 11:33
  • Re: [Lilypond-auto] Issue 2148 in lilypond: vertical skylines should use stencil integrals, lilypond, 10:41
  • [Lilypond-auto] Issue 2645 in lilypond: Patch: Adds support for cross-staff-stems, lilypond, 10:35
  • Re: [Lilypond-auto] Issue 2148 in lilypond: vertical skylines should use stencil integrals, lilypond, 09:56
  • Re: [Lilypond-auto] Issue 2644 in lilypond: Inconsistency in documentation for baseMoment, lilypond, 06:30
  • Re: [Lilypond-auto] Issue 2148 in lilypond: vertical skylines should use stencil integrals, lilypond, 06:17
  • Re: [Lilypond-auto] Issue 2148 in lilypond: vertical skylines should use stencil integrals, lilypond, 05:58
  • Re: [Lilypond-auto] Issue 2148 in lilypond: vertical skylines should use stencil integrals, lilypond, 05:56
  • Re: [Lilypond-auto] Issue 2148 in lilypond: vertical skylines should use stencil integrals, lilypond, 05:45
  • Re: [Lilypond-auto] Issue 2641 in lilypond: Patch: Add documentation for ly:one-line-breaking., lilypond, 04:43
  • [Lilypond-auto] Patchy email, lilypond-auto, 02:43
  • Re: [Lilypond-auto] Issue 2148 in lilypond: vertical skylines should use stencil integrals, lilypond, 02:27
  • Re: [Lilypond-auto] Issue 2637 in lilypond: Patch: Interpret #... inside of music lists as music instead of ignoring it, lilypond, 01:52
  • Re: [Lilypond-auto] Issue 2637 in lilypond: Patch: Interpret #... inside of music lists as music instead of ignoring it, lilypond, 00:17
• July 08, 2012
  • Re: [Lilypond-auto] Issue 2642 in lilypond: Typo in documentation 3.5 MIDI Output, lilypond, 19:14
  • Re: [Lilypond-auto] Issue 2640 in lilypond: doc enhancement for \headers, lilypond, 18:31
  • [Lilypond-auto] Issue 2644 in lilypond: Inconsistency in documentation for baseMoment, lilypond, 18:22
  • [Lilypond-auto] Issue 2643 in lilypond: Attach lilypond source in pdf, lilypond, 18:17
  • Re: [Lilypond-auto] Issue 2642 in lilypond: Typo in documentation 3.5 MIDI Output, lilypond, 17:55
  • [Lilypond-auto] Issue 2642 in lilypond: Typo in documentation 3.5 MIDI Output, lilypond, 17:51
  • [Lilypond-auto] Patchy email, lilypond-auto, 16:43
  • Re: [Lilypond-auto] Issue 2322 in lilypond: Document use of property-setting music in output definitions, lilypond, 16:22
  • [Lilypond-auto] Issue 2641 in lilypond: Patch: Add documentation for ly:one-line-breaking., lilypond, 15:25
  • Re: [Lilypond-auto] Issue 2463 in lilypond: Lyrics: add "hard" (always visible) hyphens, lilypond, 14:22
  • Re: [Lilypond-auto] Issue 427 in lilypond: ugly collision slur and phrasing slur, lilypond, 14:03
  • Re: [Lilypond-auto] Issue 2208 in lilypond: Problem running midi2ly on Mac OS X 10.6.8 : 32- vs. 64-bit code, lilypond, 08:55
  • Re: [Lilypond-auto] Issue 2557 in lilypond: alignAboveContext was removed from the NR, lilypond, 06:53
  • Re: [Lilypond-auto] Issue 2557 in lilypond: alignAboveContext was removed from the NR, lilypond, 04:12
• July 07, 2012
  • Re: [Lilypond-auto] Issue 2560 in lilypond: Documentation suggestion (was: strange behaviour of \layout block variable), lilypond, 15:57
  • [Lilypond-auto] Issue 2640 in lilypond: doc enhancement for \headers, lilypond, 14:28
  • [Lilypond-auto] Issue 2639 in lilypond: lilypond-book titles corrupted when exported to pdfs, lilypond, 14:16
  • Re: [Lilypond-auto] Issue 2560 in lilypond: Documentation suggestion (was: strange behaviour of \layout block variable), lilypond, 07:00
• July 06, 2012
  • [Lilypond-auto] Patchy email, lilypond-auto, 18:43
  • Re: [Lilypond-auto] Issue 2560 in lilypond: Documentation suggestion (was: strange behaviour of \layout block variable), lilypond, 18:29
  • Re: [Lilypond-auto] Issue 2560 in lilypond: Documentation suggestion (was: strange behaviour of \layout block variable), lilypond, 18:28
  • Re: [Lilypond-auto] Issue 2540 in lilypond: Patch: Give \tweak an optional grob parameter for tweaking indirect grobs, lilypond, 18:26
  • Re: [Lilypond-auto] Issue 2540 in lilypond: Patch: Give \tweak an optional grob parameter for tweaking indirect grobs, lilypond, 18:05
  • Re: [Lilypond-auto] Issue 2560 in lilypond: Documentation suggestion (was: strange behaviour of \layout block variable), lilypond, 16:29
  • Re: [Lilypond-auto] Issue 2565 in lilypond: Doc-suggestion: Clarify that phrasing slurs do not create melismata, lilypond, 16:06
  • Re: [Lilypond-auto] Issue 2565 in lilypond: Doc-suggestion: Clarify that phrasing slurs do not create melismata, lilypond, 15:27
  • Re: [Lilypond-auto] Issue 2595 in lilypond: Slurs in polyphony and TabStaff problems, lilypond, 14:44
  • Re: [Lilypond-auto] Issue 2587 in lilypond: Ugly slur in TabStaff if font is changed, lilypond, 14:42
  • Re: [Lilypond-auto] Issue 2574 in lilypond: Footnote on first time signature gets mark but no footnote text, lilypond, 14:40
  • Re: [Lilypond-auto] Issue 1546 in lilypond: breve collides with heads in other voice in short intervals, lilypond, 14:36
  • Re: [Lilypond-auto] Issue 427 in lilypond: ugly collision slur and phrasing slur, lilypond, 14:31
  • Re: [Lilypond-auto] Issue 379 in lilypond: ugly slur with key signature and linebreak, lilypond, 14:29
  • Re: [Lilypond-auto] Issue 2557 in lilypond: alignAboveContext was removed from the NR, lilypond, 12:30
  • Re: [Lilypond-auto] Issue 2579 in lilypond: doc enhancement: on-the-fly specifications, lilypond, 12:25
  • [Lilypond-auto] Patchy email, lilypond-auto, 10:43
  • Re: [Lilypond-auto] Issue 2638 in lilypond: Lyric Hyphens aren't placed equally far from neighbor syllables, lilypond, 07:24
  • [Lilypond-auto] Issue 2638 in lilypond: Lyric Hyphens aren't placed equally far from neighbor syllables, lilypond, 07:15
  • Re: [Lilypond-auto] Issue 2557 in lilypond: alignAboveContext was removed from the NR, lilypond, 06:45
  • Re: [Lilypond-auto] Issue 2618 in lilypond: Doc: Clarify interaction of \inversion and \relative, lilypond, 06:14
  • Re: [Lilypond-auto] Issue 2557 in lilypond: alignAboveContext was removed from the NR, lilypond, 05:59
  • Re: [Lilypond-auto] Issue 2602 in lilypond: \unfoldRepeats and \repeat tremolo 7, 14, 15 produces weird output, lilypond, 05:47
  • Re: [Lilypond-auto] Issue 2601 in lilypond: \rep eat tremolo 9 {…} should issue an error, lilypond, 05:42
  • Re: [Lilypond-auto] Issue 2579 in lilypond: doc enhancement: on-the-fly specifications, lilypond, 03:27
  • [Lilypond-auto] Patchy email, lilypond-auto, 02:43
  • Re: [Lilypond-auto] Issue 2632 in lilypond: Allow multiple occurences of Footnote_engraver, lilypond, 01:52
  • Re: [Lilypond-auto] Issue 2632 in lilypond: Allow multiple occurences of Footnote_engraver, lilypond, 00:42
  • Re: [Lilypond-auto] Issue 2628 in lilypond: Patch: Clean fonts and docs makefiles, trying to fix 'make -j' race conditions, lilypond, 00:41
  • Re: [Lilypond-auto] Issue 2579 in lilypond: doc enhancement: on-the-fly specifications, lilypond, 00:40
• July 05, 2012
  • [Lilypond-auto] Patchy email, lilypond-auto, 16:43
  • Re: [Lilypond-auto] Issue 2148 in lilypond: vertical skylines should use stencil integrals, lilypond, 12:02
  • Re: [Lilypond-auto] Issue 2148 in lilypond: vertical skylines should use stencil integrals, lilypond, 11:22
  • Re: [Lilypond-auto] Issue 2557 in lilypond: alignAboveContext was removed from the NR, lilypond, 10:49
  • [Lilypond-auto] Patchy email, lilypond-auto, 10:43
  • Re: [Lilypond-auto] Issue 2637 in lilypond: Patch: Interpret #... inside of music lists as music instead of ignoring it, lilypond, 07:49
  • Re: [Lilypond-auto] Issue 2637 in lilypond: Patch: Interpret #... inside of music lists as music instead of ignoring it, lilypond, 07:09
  • [Lilypond-auto] Issue 2637 in lilypond: Patch: Interpret #... inside of music lists as music instead of ignoring it, lilypond, 07:03
• July 04, 2012
  • Re: [Lilypond-auto] Issue 2635 in lilypond: Configure search for NCSB fonts does not work in Debian Squeeze, lilypond, 20:37
  • Re: [Lilypond-auto] Issue 2557 in lilypond: alignAboveContext was removed from the NR, lilypond, 17:34
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 13:49
  • [Lilypond-auto] Patchy email, lilypond-auto, 10:44
  • Re: [Lilypond-auto] Issue 2635 in lilypond: Configure search for NCSB fonts does not work in Debian Squeeze, lilypond, 09:23
  • Re: [Lilypond-auto] Issue 2626 in lilypond: Patch: which-page, lilypond, 09:01
  • Re: [Lilypond-auto] Issue 2626 in lilypond: Patch: which-page, lilypond, 09:00
  • [Lilypond-auto] Patchy email, lilypond-auto, 02:44
  • Re: [Lilypond-auto] Issue 2632 in lilypond: Allow multiple occurences of Footnote_engraver, lilypond, 02:05
  • Re: [Lilypond-auto] Issue 2636 in lilypond: Patch: Reject \footnote ... \default without grob specification, lilypond, 02:04
  • Re: [Lilypond-auto] Issue 2626 in lilypond: Patch: which-page, lilypond, 01:48
  • Re: [Lilypond-auto] Issue 2626 in lilypond: Patch: which-page, lilypond, 01:29
  • Re: [Lilypond-auto] Issue 2627 in lilypond: Patch: Include +inf.0 and -inf.0 in conversions of Rational to SCM and back, lilypond, 01:28
• July 03, 2012
  • Re: [Lilypond-auto] Issue 2626 in lilypond: Patch: which-page, lilypond, 21:43
  • Re: [Lilypond-auto] Issue 2627 in lilypond: Patch: Include +inf.0 and -inf.0 in conversions of Rational to SCM and back, lilypond, 21:42
  • Re: [Lilypond-auto] Issue 2579 in lilypond: doc enhancement: on-the-fly specifications, lilypond, 19:59
  • Re: [Lilypond-auto] Issue 2579 in lilypond: doc enhancement: on-the-fly specifications, lilypond, 18:22
  • Re: [Lilypond-auto] Issue 2632 in lilypond: Allow multiple occurences of Footnote_engraver, lilypond, 07:29
  • Re: [Lilypond-auto] Issue 2632 in lilypond: Allow multiple occurences of Footnote_engraver, lilypond, 05:51
  • Re: [Lilypond-auto] Issue 2636 in lilypond: Patch: Reject \footnote ... \default without grob specification, lilypond, 05:48
  • Re: [Lilypond-auto] Issue 2632 in lilypond: Allow multiple occurences of Footnote_engraver, lilypond, 05:11
  • [Lilypond-auto] Patchy email, lilypond-auto, 02:43
• July 02, 2012
  • Re: [Lilypond-auto] Issue 2625 in lilypond: Patch: Add blurb about Kievan notation to changes, lilypond, 20:49
  • Re: [Lilypond-auto] Issue 2273 in lilypond: Translations: Links in the translated documentation should point to the appropriate language if available, lilypond, 18:50
  • [Lilypond-auto] Patchy email, lilypond-auto, 18:43
  • Re: [Lilypond-auto] Issue 2635 in lilypond: Configure search for NCSB fonts does not work in Debian Squeeze, lilypond, 15:17
  • Re: [Lilypond-auto] Issue 2636 in lilypond: Patch: Reject \footnote ... \default without grob specification, lilypond, 15:14
  • [Lilypond-auto] Issue 2636 in lilypond: Patch: Reject \footnote ... \default without grob specification, lilypond, 14:42
  • Re: [Lilypond-auto] Issue 2632 in lilypond: Allow multiple occurences of Footnote_engraver, lilypond, 14:18
  • Re: [Lilypond-auto] Issue 2635 in lilypond: Configure search for NCSB fonts does not work in Debian Squeeze, lilypond, 14:17
  • Re: [Lilypond-auto] Issue 2632 in lilypond: Allow multiple occurences of Footnote_engraver, lilypond, 12:33
  • Re: [Lilypond-auto] Issue 2635 in lilypond: Configure search for NCSB fonts does not work in Debian Squeeze, lilypond, 10:22
  • Re: [Lilypond-auto] Issue 2635 in lilypond: Configure search for NCSB fonts does not work in Debian Squeeze, lilypond, 10:19
  • Re: [Lilypond-auto] Issue 2635 in lilypond: Configure search for NCSB fonts does not work in Debian Squeeze, lilypond, 10:17
  • [Lilypond-auto] Issue 2635 in lilypond: Configure search for NCSB fonts does not work in Debian Squeeze, lilypond, 10:12
  • [Lilypond-auto] Patchy email, lilypond-auto, 06:44
  • Re: [Lilypond-auto] Issue 2632 in lilypond: Allow multiple occurences of Footnote_engraver, lilypond, 06:14
  • Re: [Lilypond-auto] Issue 2632 in lilypond: Allow multiple occurences of Footnote_engraver, lilypond, 05:57
  • [Lilypond-auto] Issue 2634 in lilypond: aclocal.m4 incorrectly remove parts of python-cflags output, lilypond, 05:50
  • Re: [Lilypond-auto] Issue 2148 in lilypond: vertical skylines should use stencil integrals, lilypond, 05:23
  • [Lilypond-auto] Issue 2633 in lilypond: Browser language should persist across different pages, lilypond, 05:22
  • Re: [Lilypond-auto] Issue 2632 in lilypond: Allow multiple occurences of Footnote_engraver, lilypond, 05:14
  • Re: [Lilypond-auto] Issue 1721 in lilypond: Translations: Use @rlsrnamed instead of @rlsr, lilypond, 05:09
  • [Lilypond-auto] Issue 2632 in lilypond: Allow multiple occurences of Footnote_engraver, lilypond, 04:10
• July 01, 2012
  • Re: [Lilypond-auto] Issue 2625 in lilypond: Patch: Add blurb about Kievan notation to changes, lilypond, 22:38
  • Re: [Lilypond-auto] Issue 2626 in lilypond: Patch: which-page, lilypond, 21:04
  • Re: [Lilypond-auto] Issue 2631 in lilypond: Kievan notation should space melismas, not notes, lilypond, 20:08
  • Re: [Lilypond-auto] Issue 2345 in lilypond: Kievan notation - there should be no space after a final note, lilypond, 19:59
  • [Lilypond-auto] Issue 2631 in lilypond: Kievan notation should space melismas, not notes, lilypond, 19:56
  • Re: [Lilypond-auto] Issue 2629 in lilypond: Patch: Get texidoc translations out of snippets source files, lilypond, 19:20
  • Re: [Lilypond-auto] Issue 2604 in lilypond: LILYPOND_BUILD_DIR, lilypond, 19:17
  • Re: [Lilypond-auto] Issue 2524 in lilypond: Patch: CG: add updating of lilypond.pot in the release process, lilypond, 19:16
  • Re: [Lilypond-auto] Issue 2604 in lilypond: LILYPOND_BUILD_DIR, lilypond, 19:15
  • Re: [Lilypond-auto] Issue 2625 in lilypond: Patch: Add blurb about Kievan notation to changes, lilypond, 18:42
  • Re: [Lilypond-auto] Issue 2148 in lilypond: vertical skylines should use stencil integrals, lilypond, 10:55
  • Re: [Lilypond-auto] Issue 2619 in lilypond: Remove 'fragment' from ancient.itely, lilypond, 01:39

---

[Prev Period]

[Next Period]

---

Mail converted by MHonArc