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: Mon Dec 31 2012 18:46:00 -0500 Messages in reverse chronological order

[Next Period]

---

• December 31, 2012
  • Re: [Lilypond-auto] Issue 677 in lilypond: \score markup confuses paper settings, lilypond, 18:46
  • Re: [Lilypond-auto] Issue 677 in lilypond: \score markup confuses paper settings, lilypond, 18:32
  • Re: [Lilypond-auto] Issue 677 in lilypond: \score markup confuses paper settings, lilypond, 14:10
  • Re: [Lilypond-auto] Issue 677 in lilypond: \score markup confuses paper settings, lilypond, 13:35
  • Re: [Lilypond-auto] Issue 3073 in lilypond: Context definitions and context mods ignore \unset, lilypond, 13:24
  • Re: [Lilypond-auto] Issue 3071 in lilypond: Introduce markup-commands: \draw-dashed-line and \draw-dotted-line, lilypond, 13:23
  • Re: [Lilypond-auto] Issue 2983 in lilypond: assertion failed with \glissando, lilypond, 13:22
  • Re: [Lilypond-auto] Issue 1354 in lilypond: associatedVoice fails for second syllable, lilypond, 13:11
  • Re: [Lilypond-auto] Issue 677 in lilypond: \score markup confuses paper settings, lilypond, 12:26
  • Re: [Lilypond-auto] Issue 677 in lilypond: \score markup confuses paper settings, lilypond, 12:20
  • Re: [Lilypond-auto] Issue 3071 in lilypond: Introduce markup-commands: \draw-dashed-line and \draw-dotted-line, lilypond, 12:13
  • Re: [Lilypond-auto] Issue 3071 in lilypond: Introduce markup-commands: \draw-dashed-line and \draw-dotted-line, lilypond, 11:49
  • Re: [Lilypond-auto] Issue 712 in lilypond: alignment of multiple \tempo marks over `church rests', lilypond, 11:05
  • Re: [Lilypond-auto] Issue 3073 in lilypond: Context definitions and context mods ignore \unset, lilypond, 11:01
  • Re: [Lilypond-auto] Issue 1263 in lilypond: MetronomeMark can not be aligned on note if MMR in another voice, lilypond, 10:57
  • Re: [Lilypond-auto] Issue 3073 in lilypond: Context definitions and context mods ignore \unset, lilypond, 10:56
  • Re: [Lilypond-auto] Issue 720 in lilypond: incorrect bbox values for EPS images, lilypond, 10:55
  • Re: [Lilypond-auto] Issue 712 in lilypond: alignment of multiple \tempo marks over `church rests', lilypond, 10:53
  • Re: [Lilypond-auto] Issue 712 in lilypond: alignment of multiple \tempo marks over `church rests', lilypond, 10:47
  • Re: [Lilypond-auto] Issue 346 in lilypond: monochord issues, lilypond, 10:41
  • Re: [Lilypond-auto] Issue 677 in lilypond: \score markup confuses paper settings, lilypond, 10:34
  • Re: [Lilypond-auto] Issue 3073 in lilypond: Context definitions and context mods ignore \unset, lilypond, 08:13
  • [Lilypond-auto] Issue 3073 in lilypond: Context definitions and context mods ignore \unset, lilypond, 07:40
  • Re: [Lilypond-auto] Issue 3051 in lilypond: [DOC ]Update Contributor’s Guide 5.2 to mention use of LSR, lilypond, 06:08
  • Re: [Lilypond-auto] Issue 3015 in lilypond: Move Appendix C to the NR, LilyPond Grammar, to the CG, lilypond, 06:01
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 05:28
  • Re: [Lilypond-auto] Issue 3058 in lilypond: Patch: Make lexer more robust against unexpected EOF, lilypond, 05:07
  • Re: [Lilypond-auto] Issue 2870 in lilypond: NR Document \single command, lilypond, 03:42
• December 30, 2012
  • Re: [Lilypond-auto] Issue 3063 in lilypond: Make \articulate handle grace notes, lilypond, 21:44
  • Re: [Lilypond-auto] Issue 3060 in lilypond: False warnings produced by simultaneous key changes, lilypond, 21:42
  • Re: [Lilypond-auto] Issue 3058 in lilypond: Patch: Make lexer more robust against unexpected EOF, lilypond, 21:42
  • Re: [Lilypond-auto] Issue 3051 in lilypond: [DOC ]Update Contributor’s Guide 5.2 to mention use of LSR, lilypond, 21:41
  • Re: [Lilypond-auto] Issue 3015 in lilypond: Move Appendix C to the NR, LilyPond Grammar, to the CG, lilypond, 21:39
  • Re: [Lilypond-auto] Issue 2527 in lilypond: Finger-flag collision, lilypond, 21:39
  • Re: [Lilypond-auto] Issue 847 in lilypond: python scripts should add an autogenerated marker, lilypond, 21:36
  • Re: [Lilypond-auto] Issue 3071 in lilypond: Introduce markup-commands: \draw-dashed-line and \draw-dotted-line, lilypond, 15:51
  • [Lilypond-auto] Issue 3072 in lilypond: Nested overrides get confused with multiple contexts in play, lilypond, 15:00
  • Re: [Lilypond-auto] Issue 1494 in lilypond: including alternate fonts, lilypond, 11:37
  • Re: [Lilypond-auto] Issue 3071 in lilypond: Introduce markup-commands: \draw-dashed-line and \draw-dotted-line, lilypond, 11:13
  • [Lilypond-auto] Issue 3071 in lilypond: Introduce markup-commands: \draw-dashed-line and \draw-dotted-line, lilypond, 10:59
  • Re: [Lilypond-auto] Issue 3027 in lilypond: Changing document fonts with non-standard global font size leads to scaling errors, lilypond, 09:58
  • Re: [Lilypond-auto] Issue 3003 in lilypond: Document the MIDI backend, lilypond, 08:33
  • Re: [Lilypond-auto] Issue 2992 in lilypond: Closer nestling of grobs has spoilt some examples in the LM, lilypond, 06:08
  • Re: [Lilypond-auto] Issue 3003 in lilypond: Document the MIDI backend, lilypond, 05:48
  • Re: [Lilypond-auto] Issue 3027 in lilypond: Changing document fonts with non-standard global font size leads to scaling errors, lilypond, 05:02
• December 29, 2012
  • Re: [Lilypond-auto] Issue 3056 in lilypond: Barring example in Notation Reference, lilypond, 15:34
  • Re: [Lilypond-auto] Issue 3070 in lilypond: Patch: PO: remove duplicates entries for hh and cc from ALL_PO_SOURCES, lilypond, 14:39
  • Re: [Lilypond-auto] Issue 3006 in lilypond: Clarify context creation in NR 5.1.2, lilypond, 14:07
  • Re: [Lilypond-auto] Issue 2870 in lilypond: NR Document \single command, lilypond, 14:06
  • [Lilypond-auto] Issue 3070 in lilypond: Patch: PO: remove duplicates entries for hh and cc from ALL_PO_SOURCES, lilypond, 13:48
  • Re: [Lilypond-auto] Issue 2961 in lilypond: \fret-diagram-verbose with capo > 1 puts capo in the 1st fret wrongly, lilypond, 11:15
  • Re: [Lilypond-auto] Issue 2961 in lilypond: \fret-diagram-verbose with capo > 1 puts capo in the 1st fret wrongly, lilypond, 11:09
  • Re: [Lilypond-auto] Issue 2870 in lilypond: NR Document \single command, lilypond, 11:03
  • Re: [Lilypond-auto] Issue 3062 in lilypond: LP doesn't report unterminated ties that are left hanging at the end of input, lilypond, 10:25
  • Re: [Lilypond-auto] Issue 3067 in lilypond: Patch: Rewrite of Midi.c in Python, lilypond, 10:24
  • Re: [Lilypond-auto] Issue 3060 in lilypond: False warnings produced by simultaneous key changes, lilypond, 10:23
  • Re: [Lilypond-auto] Issue 3063 in lilypond: Make \articulate handle grace notes, lilypond, 10:22
  • Re: [Lilypond-auto] Issue 3051 in lilypond: [DOC ]Update Contributor’s Guide 5.2 to mention use of LSR, lilypond, 10:21
  • Re: [Lilypond-auto] Issue 2582 in lilypond: Change GUB github links from janneke to gperciva, lilypond, 10:10
  • Re: [Lilypond-auto] Issue 3006 in lilypond: Clarify context creation in NR 5.1.2, lilypond, 10:09
  • Re: [Lilypond-auto] Issue 2961 in lilypond: \fret-diagram-verbose with capo > 1 puts capo in the 1st fret wrongly, lilypond, 09:37
  • Re: [Lilypond-auto] Issue 3069 in lilypond: Patch: Several property code cleanups:, lilypond, 09:24
  • Re: [Lilypond-auto] Issue 3069 in lilypond: Patch: Several property code cleanups:, lilypond, 09:11
  • [Lilypond-auto] Issue 3069 in lilypond: Patch: Several property code cleanups:, lilypond, 08:23
  • Re: [Lilypond-auto] Issue 3069 in lilypond: Patch: Several property code cleanups:, lilypond, 08:22
  • Re: [Lilypond-auto] Issue 2266 in lilypond: Translations: links to untranslated nodes of external manuals are broken because of node conflicts, lilypond, 05:59
  • Re: [Lilypond-auto] Issue 2266 in lilypond: Translations: @rlsrnamed{Name, Translation} translates also the name in the URI, lilypond, 05:27
  • Re: [Lilypond-auto] Issue 1721 in lilypond: Translations: Use @rlsrnamed instead of @rlsr, lilypond, 05:26
  • Re: [Lilypond-auto] Issue 2273 in lilypond: Translations: Links in the translated documentation should point to the appropriate language if available, lilypond, 05:24
  • Re: [Lilypond-auto] Issue 2633 in lilypond: Browser language should persist across different pages, lilypond, 05:23
• December 28, 2012
  • Re: [Lilypond-auto] Issue 3065 in lilypond: Baroque french tab support, lilypond, 23:48
  • Re: [Lilypond-auto] Issue 2741 in lilypond: Thank donations and services for development infrastructure, lilypond, 02:22
  • Re: [Lilypond-auto] Issue 3056 in lilypond: Barring example in Notation Reference, lilypond, 01:22
• December 27, 2012
  • Re: [Lilypond-auto] Issue 3056 in lilypond: Barring example in Notation Reference, lilypond, 22:10
  • Re: [Lilypond-auto] Issue 3056 in lilypond: Barring example in Notation Reference, lilypond, 21:43
  • Re: [Lilypond-auto] Issue 3056 in lilypond: Barring example in Notation Reference, lilypond, 21:40
  • Re: [Lilypond-auto] Issue 2961 in lilypond: \fret-diagram-verbose with capo > 1 puts capo in the 1st fret wrongly, lilypond, 21:29
  • Re: [Lilypond-auto] Issue 2741 in lilypond: Thank donations and services for development infrastructure, lilypond, 21:28
  • Re: [Lilypond-auto] Issue 2348 in lilypond: Patch: Handling of open strings in tablature, lilypond, 21:27
  • Re: [Lilypond-auto] Issue 3068 in lilypond: Patch: Simplify several library functions., lilypond, 16:31
  • Re: [Lilypond-auto] Issue 3056 in lilypond: Barring example in Notation Reference, lilypond, 15:32
  • Re: [Lilypond-auto] Issue 3056 in lilypond: Barring example in Notation Reference, lilypond, 15:27
  • Re: [Lilypond-auto] Issue 3056 in lilypond: Barring example in Notation Reference, lilypond, 15:17
  • Re: [Lilypond-auto] Issue 3068 in lilypond: Patch: Simplify several library functions., lilypond, 13:48
  • [Lilypond-auto] Issue 3068 in lilypond: Patch: Simplify several library functions., lilypond, 13:47
  • Re: [Lilypond-auto] Issue 3049 in lilypond: Parser outputs Lyric events for illegal note names, lilypond, 10:24
  • Re: [Lilypond-auto] Issue 3067 in lilypond: Patch: Rewrite of Midi.c in Python, lilypond, 07:21
  • Re: [Lilypond-auto] Issue 3056 in lilypond: Barring example in Notation Reference, lilypond, 04:32
  • Re: [Lilypond-auto] Issue 847 in lilypond: python scripts should add an autogenerated marker, lilypond, 03:45
  • Re: [Lilypond-auto] Issue 3056 in lilypond: Barring example in Notation Reference, lilypond, 03:38
  • Re: [Lilypond-auto] Issue 3056 in lilypond: Barring example in Notation Reference, lilypond, 00:38
• December 26, 2012
  • Re: [Lilypond-auto] Issue 3062 in lilypond: LP doesn't report unterminated ties that are left hanging at the end of input, lilypond, 19:56
  • Re: [Lilypond-auto] Issue 3049 in lilypond: Parser outputs Lyric events for illegal note names, lilypond, 19:05
  • Re: [Lilypond-auto] Issue 3051 in lilypond: [DOC ]Update Contributor’s Guide 5.2 to mention use of LSR, lilypond, 18:40
  • Re: [Lilypond-auto] Issue 3063 in lilypond: Make \articulate handle grace notes, lilypond, 18:32
  • Re: [Lilypond-auto] Issue 3062 in lilypond: LP doesn't report unterminated ties that are left hanging at the end of input, lilypond, 18:31
  • Re: [Lilypond-auto] Issue 3060 in lilypond: False warnings produced by simultaneous key changes, lilypond, 18:29
  • Re: [Lilypond-auto] Issue 3063 in lilypond: Make \articulate handle grace notes, lilypond, 16:41
  • Re: [Lilypond-auto] Issue 3061 in lilypond: make \articulate handle colon-type tremolos, lilypond, 16:40
  • Re: [Lilypond-auto] Issue 3063 in lilypond: Make \articulate handle grace notes, lilypond, 16:35
  • Re: [Lilypond-auto] Issue 3060 in lilypond: False warnings produced by simultaneous key changes, lilypond, 16:31
  • Re: [Lilypond-auto] Issue 3062 in lilypond: LP doesn't report unterminated ties that are left hanging at the end of input, lilypond, 16:23
  • Re: [Lilypond-auto] Issue 3049 in lilypond: Parser outputs Lyric events for illegal note names, lilypond, 16:17
  • Re: [Lilypond-auto] Issue 3067 in lilypond: Patch: Rewrite of Midi.c in Python, lilypond, 16:08
  • [Lilypond-auto] Issue 3067 in lilypond: Patch: Rewrite of Midi.c in Python, lilypond, 16:05
  • Re: [Lilypond-auto] Issue 3051 in lilypond: [DOC ]Update Contributor’s Guide 5.2 to mention use of LSR, lilypond, 15:51
  • Re: [Lilypond-auto] Issue 3066 in lilypond: tie in TabStaff (using q) displays one of the unisone notes in a chord, lilypond, 15:11
  • Re: [Lilypond-auto] Issue 3066 in lilypond: tie in TabStaff (using q) displays one of the unisone notes in a chord, lilypond, 15:09
  • Re: [Lilypond-auto] Issue 3066 in lilypond: tie in TabStaff (using q) displays one of the unisone notes in a chord, lilypond, 14:55
  • [Lilypond-auto] Issue 3066 in lilypond: tie in TabStaff (using q) displays one of the unisone notes in a chord, lilypond, 14:54
  • Re: [Lilypond-auto] Issue 847 in lilypond: python scripts should add an autogenerated marker, lilypond, 11:15
  • Re: [Lilypond-auto] Issue 847 in lilypond: python scripts should add an autogenerated marker, lilypond, 10:48
  • Re: [Lilypond-auto] Issue 847 in lilypond: python scripts should add an autogenerated marker, lilypond, 10:45
  • Re: [Lilypond-auto] Issue 2731 in lilypond: missing link on v2.15/Documentation/web-big-page, lilypond, 08:41
  • Re: [Lilypond-auto] Issue 3015 in lilypond: Move Appendix C to the NR, LilyPond Grammar, to the CG, lilypond, 08:13
  • Re: [Lilypond-auto] Issue 3015 in lilypond: Move Appendix C to the NR, LilyPond Grammar, to the CG, lilypond, 08:12
  • Re: [Lilypond-auto] Issue 3056 in lilypond: Barring example in Notation Reference, lilypond, 06:11
  • Re: [Lilypond-auto] Issue 3015 in lilypond: Move Appendix C to the NR, LilyPond Grammar, to the CG, lilypond, 03:16
  • Re: [Lilypond-auto] Issue 3015 in lilypond: Move Appendix C to the NR, LilyPond Grammar, to the CG, lilypond, 03:14
  • Re: [Lilypond-auto] Issue 3051 in lilypond: [DOC ]Update Contributor’s Guide 5.2 to mention use of LSR, lilypond, 02:34
• December 25, 2012
  • [Lilypond-auto] Issue 3065 in lilypond: Baroque french tab support, lilypond, 20:48
  • Re: [Lilypond-auto] Issue 3054 in lilypond: wrong vertical distance after wrapped lines, lilypond, 18:33
  • Re: [Lilypond-auto] Issue 3064 in lilypond: deadNotes example is not playable, lilypond, 13:26
  • Re: [Lilypond-auto] Issue 3064 in lilypond: deadNotes example is not playable, lilypond, 12:36
  • Re: [Lilypond-auto] Issue 2074 in lilypond: Add crossreferences to NR Appendix C "Lilypond Grammar", lilypond, 04:30
  • Re: [Lilypond-auto] Issue 3064 in lilypond: deadNotes example is not playable, lilypond, 04:19
  • Re: [Lilypond-auto] Issue 3064 in lilypond: deadNotes example is not playable, lilypond, 04:16
  • Re: [Lilypond-auto] Issue 3032 in lilypond: \textLengthOn no longer works correctly, lilypond, 03:37
  • [Lilypond-auto] Issue 3064 in lilypond: deadNotes example is not playable, lilypond, 03:08
  • Re: [Lilypond-auto] Issue 2074 in lilypond: Add crossreferences to NR Appendix C "Lilypond Grammar", lilypond, 02:57
  • Re: [Lilypond-auto] Issue 2074 in lilypond: Add crossreferences to NR Appendix C "Lilypond Grammar", lilypond, 02:07
  • Re: [Lilypond-auto] Issue 3015 in lilypond: Move Appendix C to the NR, LilyPond Grammar, to the CG, lilypond, 02:07
  • Re: [Lilypond-auto] Issue 3063 in lilypond: Make \articulate handle grace notes, lilypond, 01:26
  • Re: [Lilypond-auto] Issue 3061 in lilypond: make \articulate handle colon-type tremolos, lilypond, 01:25
  • [Lilypond-auto] Issue 3063 in lilypond: Make \articulate handle grace notes, lilypond, 01:24
  • Re: [Lilypond-auto] Issue 3062 in lilypond: LP doesn't report unterminated ties that are left hanging at the end of input, lilypond, 01:23
  • Re: [Lilypond-auto] Issue 3051 in lilypond: [DOC ]Update Contributor’s Guide 5.2 to mention use of LSR, lilypond, 01:19
  • Re: [Lilypond-auto] Issue 3056 in lilypond: Barring example in Notation Reference, lilypond, 00:58
  • [Lilypond-auto] Issue 3062 in lilypond: LP doesn't report unterminated ties that are left hanging at the end of input, lilypond, 00:39
  • [Lilypond-auto] Issue 3061 in lilypond: make \articulate handle colon-type tremolos, lilypond, 00:37
  • Re: [Lilypond-auto] Issue 3060 in lilypond: False warnings produced by simultaneous key changes, lilypond, 00:35
  • [Lilypond-auto] Issue 3060 in lilypond: False warnings produced by simultaneous key changes, lilypond, 00:34
  • Re: [Lilypond-auto] Issue 2864 in lilypond: [Web]Productions: The critical edition of Tommaso Traetta's Enea nel Lazio (1760), lilypond, 00:21
  • Re: [Lilypond-auto] Issue 3021 in lilypond: wrong midi instrument in NR, lilypond, 00:11
• December 24, 2012
  • Re: [Lilypond-auto] Issue 3052 in lilypond: Lilypond-book 2.16.1 fails on Windows XP and Windows 8, lilypond, 06:02
  • Re: [Lilypond-auto] Issue 3059 in lilypond: Patch: Allows for easier creation of many Lilypond objects via Scheme., lilypond, 03:50
  • Re: [Lilypond-auto] Issue 3059 in lilypond: Patch: Allows for easier creation of many Lilypond objects via Scheme., lilypond, 02:50
  • Re: [Lilypond-auto] Issue 2731 in lilypond: missing link on v2.15/Documentation/web-big-page, lilypond, 02:34
  • Re: [Lilypond-auto] Issue 3058 in lilypond: Patch: Make lexer more robust against unexpected EOF, lilypond, 02:21
  • Re: [Lilypond-auto] Issue 3041 in lilypond: Patch: Fix a few segfaulting cases in hara-kiri-group-spanner, lilypond, 02:10
  • Re: [Lilypond-auto] Issue 3024 in lilypond: Patch: Add dead-is-alive boolean property to Hara_kiri_group_spanner, lilypond, 01:51
• December 23, 2012
  • Re: [Lilypond-auto] Issue 3024 in lilypond: Patch: Add dead-is-alive boolean property to Hara_kiri_group_spanner, lilypond, 21:40
  • Re: [Lilypond-auto] Issue 3041 in lilypond: Patch: Fix a few segfaulting cases in hara-kiri-group-spanner, lilypond, 21:37
  • Re: [Lilypond-auto] Issue 3044 in lilypond: Dual license the files under mf/ using OFL., lilypond, 21:36
  • Re: [Lilypond-auto] Issue 3037 in lilypond: The end of a ligature bracket doesn't appear at the start of a line, lilypond, 21:35
  • Re: [Lilypond-auto] Issue 3021 in lilypond: wrong midi instrument in NR, lilypond, 21:34
  • Re: [Lilypond-auto] Issue 3032 in lilypond: \textLengthOn no longer works correctly, lilypond, 21:33
  • Re: [Lilypond-auto] Issue 2864 in lilypond: [Doc]Productions: The critical edition of Tommaso Traetta's Enea nel Lazio (1760), lilypond, 21:32
  • Re: [Lilypond-auto] Issue 3057 in lilypond: missbehavior of \deadNotesOn in the begining of LilyPond code, lilypond, 17:34
  • Re: [Lilypond-auto] Issue 3059 in lilypond: Patch: Allows for easier creation of many Lilypond objects via Scheme., lilypond, 16:54
  • [Lilypond-auto] Issue 3059 in lilypond: Patch: Allows for easier creation of many Lilypond objects via Scheme., lilypond, 16:35
  • Re: [Lilypond-auto] Issue 3052 in lilypond: Lilypond-book 2.16.1 fails on Windows XP and Windows 8, lilypond, 16:33
  • Re: [Lilypond-auto] Issue 3056 in lilypond: Barring example in Notation Reference, lilypond, 16:32
  • Re: [Lilypond-auto] Issue 3058 in lilypond: Patch: Make lexer more robust against unexpected EOF, lilypond, 16:25
  • [Lilypond-auto] Issue 3058 in lilypond: Patch: Make lexer more robust against unexpected EOF, lilypond, 16:24
  • Re: [Lilypond-auto] Issue 3057 in lilypond: missbehavior of \deadNotesOn in the begining of LilyPond code, lilypond, 13:41
  • Re: [Lilypond-auto] Issue 3057 in lilypond: missbehavior of \deadNotesOn in the begining of LilyPond code, lilypond, 13:38
  • Re: [Lilypond-auto] Issue 2731 in lilypond: missing link on v2.15/Documentation/web-big-page, lilypond, 12:26
  • Re: [Lilypond-auto] Issue 2731 in lilypond: missing link on v2.15/Documentation/web-big-page, lilypond, 12:03
  • Re: [Lilypond-auto] Issue 2731 in lilypond: missing link on v2.15/Documentation/web-big-page, lilypond, 11:47
  • Re: [Lilypond-auto] Issue 2961 in lilypond: \fret-diagram-verbose with capo > 1 puts capo in the 1st fret wrongly, lilypond, 11:11
  • [Lilypond-auto] Issue 3057 in lilypond: missbehavior of \deadNotesOn in the begining of LilyPond code, lilypond, 10:52
  • Re: [Lilypond-auto] Issue 2731 in lilypond: missing link on v2.15/Documentation/web-big-page, lilypond, 07:25
  • Re: [Lilypond-auto] Issue 2961 in lilypond: \fret-diagram-verbose with capo > 1 puts capo in the 1st fret wrongly, lilypond, 07:20
  • Re: [Lilypond-auto] Issue 2117 in lilypond: Update git-cl to use Type-Patch, lilypond, 07:19
  • Re: [Lilypond-auto] Issue 2186 in lilypond: git-cl always uses first commit's message, lilypond, 07:18
  • Re: [Lilypond-auto] Issue 2187 in lilypond: git-cl doesn't 'always' remember (the last) tracker issue number you used, lilypond, 07:17
  • Re: [Lilypond-auto] Issue 2202 in lilypond: issues created by git-cl have status "new" instead of "started", lilypond, 07:16
  • Re: [Lilypond-auto] Issue 2900 in lilypond: Patch: Could git-cl set the owner?, lilypond, 07:15
  • Re: [Lilypond-auto] Issue 3053 in lilypond: Further website updates needed, lilypond, 07:11
  • Re: [Lilypond-auto] Issue 3027 in lilypond: Changing document fonts with non-standard global font size leads to scaling errors, lilypond, 06:24
  • Re: [Lilypond-auto] Issue 3020 in lilypond: Patch: Documentation/GNUmakefile: Add dependencies for internals.texi, lilypond, 05:52
  • Re: [Lilypond-auto] Issue 3052 in lilypond: Lilypond-book 2.16.1 fails on Windows XP and Windows 8, lilypond, 04:23
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 03:52
• December 22, 2012
  • Re: [Lilypond-auto] Issue 2741 in lilypond: Thank donations and services for development infrastructure, lilypond, 19:20
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 18:18
  • Re: [Lilypond-auto] Issue 2940 in lilypond: Patch: Add alias in Spanish for espanol note names language, lilypond, 17:45
  • Re: [Lilypond-auto] Issue 3052 in lilypond: Lilypond-book 2.16.1 fails on Windows XP and Windows 8, lilypond, 17:09
  • [Lilypond-auto] Issue 3056 in lilypond: Barring example in Notation Reference, lilypond, 17:01
  • [Lilypond-auto] Issue 3055 in lilypond: Poor barring indicator spanner, lilypond, 16:55
  • Re: [Lilypond-auto] Issue 3054 in lilypond: wrong vertical distance after wrapped lines, lilypond, 16:50
  • [Lilypond-auto] Issue 3054 in lilypond: wrong vertical distance after wrapped lines, lilypond, 16:39
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 16:21
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 16:14
  • Re: [Lilypond-auto] Issue 2741 in lilypond: Thank donations and services for development infrastructure, lilypond, 15:57
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 15:46
  • Re: [Lilypond-auto] Issue 2527 in lilypond: Finger-flag collision, lilypond, 14:59
  • Re: [Lilypond-auto] Issue 3053 in lilypond: Further website updates needed, lilypond, 14:54
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 14:53
  • Re: [Lilypond-auto] Issue 2703 in lilypond: Patch: Set indent based on instrument name, lilypond, 12:48
  • Re: [Lilypond-auto] Issue 2709 in lilypond: Patch: Changes make test to allow output to be reviewed in a browser, lilypond, 12:47
  • Re: [Lilypond-auto] Issue 3053 in lilypond: Further website updates needed, lilypond, 12:45
  • [Lilypond-auto] Issue 3053 in lilypond: Further website updates needed, lilypond, 12:00
  • Re: [Lilypond-auto] Issue 2527 in lilypond: Finger-flag collision, lilypond, 11:09
  • Re: [Lilypond-auto] Issue 3052 in lilypond: Lilypond-book 2.16.1 fails on Windows XP and Windows 8, lilypond, 10:26
  • Re: [Lilypond-auto] Issue 2940 in lilypond: Patch: Add alias in Spanish for espanol note names language, lilypond, 10:03
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 09:42
  • Re: [Lilypond-auto] Issue 3052 in lilypond: Lilypond-book 2.16.1 fails on Windows XP and Windows 8, lilypond, 08:37
  • Re: [Lilypond-auto] Issue 3052 in lilypond: Lilypond-book 2.16.1 fails on Windows XP and Windows 8, lilypond, 07:54
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 07:19
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 07:11
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 06:46
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 06:37
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 06:16
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 06:00
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 05:37
  • Re: [Lilypond-auto] Issue 3013 in lilypond: Patch: Amend \overrideProperty example, lilypond, 04:53
  • Re: [Lilypond-auto] Issue 3019 in lilypond: Patch: Let ly:event-property take an optional default argument, lilypond, 04:52
  • Re: [Lilypond-auto] Issue 3018 in lilypond: Patch: lilypond-mode.el: Replace use of obsoleted compile-internal, lilypond, 04:48
  • Re: [Lilypond-auto] Issue 2172 in lilypond: Get line and column numbers right., lilypond, 04:46
  • Re: [Lilypond-auto] Issue 1029 in lilypond: \thumb should behave like other fingerings, lilypond, 04:44
  • Re: [Lilypond-auto] Issue 3023 in lilypond: Papersizes with landscape/portrait suffix are not recognized by -dpapersize, lilypond, 03:56
  • Re: [Lilypond-auto] Issue 3023 in lilypond: Papersizes with landscape/portrait suffix are not recognized by -dpapersize, lilypond, 03:53
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 03:27
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 01:42
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 01:41
• December 21, 2012
  • [Lilypond-auto] Issue 3052 in lilypond: Lilypond-book 2.16.1 fails on Windows XP and Windows 8, lilypond, 18:54
  • Re: [Lilypond-auto] Issue 3023 in lilypond: Papersizes with landscape/portrait suffix are not recognized by -dpapersize, lilypond, 18:42
  • [Lilypond-auto] Issue 3051 in lilypond: [DOC ]Update Contributor’s Guide 5.2 to mention use of LSR, lilypond, 15:38
  • Re: [Lilypond-auto] Issue 3020 in lilypond: Patch: Documentation/GNUmakefile: Add dependencies for internals.texi, lilypond, 13:42
  • [Lilypond-auto] Patchy email, phileholmes, 10:52
  • Re: [Lilypond-auto] Issue 2895 in lilypond: Enhancement request for web page http://lilypond.org/manuals.html, lilypond, 10:42
  • Re: [Lilypond-auto] Issue 3050 in lilypond: displayLilyMusic produced erroneous code for rightHandFinger arguments, lilypond, 05:38
  • [Lilypond-auto] Issue 3050 in lilypond: displayLilyMusic produced erroneous code for rightHandFinger arguments, lilypond, 04:30
  • Re: [Lilypond-auto] Issue 3037 in lilypond: The end of a ligature bracket doesn't appear at the start of a line, lilypond, 03:38
  • Re: [Lilypond-auto] Issue 3027 in lilypond: Changing document fonts with non-standard global font size leads to scaling errors, lilypond, 03:37
  • [Lilypond-auto] Issue 3049 in lilypond: Parser outputs Lyric events for illegal note names, lilypond, 03:31
  • Re: [Lilypond-auto] Issue 3001 in lilypond: Patch: Changes to Kievan documentation, lilypond, 02:56
  • [Lilypond-auto] Issue 3048 in lilypond: Write a message when somebody tries to \set a grob property, lilypond, 02:52
  • Re: [Lilypond-auto] Issue 3020 in lilypond: Patch: Documentation/GNUmakefile: Add dependencies for internals.texi, lilypond, 02:16
  • Re: [Lilypond-auto] Issue 3004 in lilypond: Web documentation needs updates, lilypond, 02:14
  • Re: [Lilypond-auto] Issue 3028 in lilypond: lyqi link from LP web site not valid, lilypond, 02:11
  • Re: [Lilypond-auto] Issue 3033 in lilypond: Doc: Usage - clarifying the documentation of advanced command-line options, lilypond, 02:09
  • Re: [Lilypond-auto] Issue 3018 in lilypond: Patch: lilypond-mode.el: Replace use of obsoleted compile-internal, lilypond, 00:52
  • Re: [Lilypond-auto] Issue 3033 in lilypond: Doc: Usage - clarifying the documentation of advanced command-line options, lilypond, 00:51
  • Re: [Lilypond-auto] Issue 3028 in lilypond: lyqi link from LP web site not valid, lilypond, 00:50
  • Re: [Lilypond-auto] Issue 3020 in lilypond: Patch: Documentation/GNUmakefile: Add dependencies for internals.texi, lilypond, 00:49
  • Re: [Lilypond-auto] Issue 3004 in lilypond: Web documentation needs updates, lilypond, 00:48
  • Re: [Lilypond-auto] Issue 2895 in lilypond: Enhancement request for web page http://lilypond.org/manuals.html, lilypond, 00:47
  • Re: [Lilypond-auto] Issue 2172 in lilypond: Get line and column numbers right., lilypond, 00:46
  • Re: [Lilypond-auto] Issue 1029 in lilypond: \thumb should behave like other fingerings, lilypond, 00:45
• December 20, 2012
  • Re: [Lilypond-auto] Issue 2965 in lilypond: packed-spacing and \newSpacingSection lead to collision of dots and notes, lilypond, 21:00
  • Re: [Lilypond-auto] Issue 2965 in lilypond: packed-spacing and \newSpacingSection lead to collision of dots and notes, lilypond, 20:56
  • Re: [Lilypond-auto] Issue 2940 in lilypond: Patch: Add alias in Spanish for espanol note names language, lilypond, 10:18
  • Re: [Lilypond-auto] Issue 2966 in lilypond: Enhancement: introduces rest-by-number and rest, lilypond, 09:38
  • Re: [Lilypond-auto] Issue 3001 in lilypond: Patch: Changes to Kievan documentation, lilypond, 09:35
  • Re: [Lilypond-auto] Issue 2940 in lilypond: Patch: Add alias in Spanish for espanol note names language, lilypond, 09:34
  • [Lilypond-auto] Issue 3046 in lilypond: add "real" string number extenders, lilypond, 09:21
  • [Lilypond-auto] Issue 3047 in lilypond: Add real string number extenders, lilypond, 05:18
  • Re: [Lilypond-auto] Issue 3023 in lilypond: Papersizes with landscape/portrait suffix are not recognized by -dpapersize, lilypond, 04:52
  • [Lilypond-auto] Issue 3045 in lilypond: Document changing default rest position in NR 1.2.2, lilypond, 04:50
  • Re: [Lilypond-auto] Issue 2971 in lilypond: Clarify the limitation on footnotes as articulations, lilypond, 04:16
  • Re: [Lilypond-auto] Issue 3016 in lilypond: Fix of bad example in \rest-by-number, lilypond, 04:06
  • Re: [Lilypond-auto] Issue 3010 in lilypond: Removes '-signs from vectors, lilypond, 04:04
  • Re: [Lilypond-auto] Issue 3027 in lilypond: Changing document fonts with non-standard global font size leads to scaling errors, lilypond, 02:40
• December 19, 2012
  • [Lilypond-auto] Patchy report, grenouille, 21:38
  • Re: [Lilypond-auto] Issue 1263 in lilypond: MetronomeMark can not be aligned on note if MMR in another voice, lilypond, 21:30
  • Re: [Lilypond-auto] Issue 3044 in lilypond: Dual license the files under mf/ using OFL., lilypond, 18:24
  • Re: [Lilypond-auto] Issue 3044 in lilypond: Dual license the files under mf/ using OFL., lilypond, 17:24
  • [Lilypond-auto] Issue 3044 in lilypond: Dual license the files under mf/ using OFL., lilypond, 17:22
  • Re: [Lilypond-auto] Issue 3020 in lilypond: Patch: Documentation/GNUmakefile: Add dependencies for internals.texi, lilypond, 17:17
  • [Lilypond-auto] Issue 3043 in lilypond: Avoiding collisions involving full-bar rests, lilypond, 16:12
  • Re: [Lilypond-auto] Issue 3020 in lilypond: Patch: Documentation/GNUmakefile: Add dependencies for internals.texi, lilypond, 16:09
  • Re: [Lilypond-auto] Issue 3012 in lilypond: Patch: Flag an error for isolated post-events occuring in music lists, lilypond, 15:41
  • Re: [Lilypond-auto] Issue 3012 in lilypond: Patch: Flag an error for isolated post-events occuring in music lists, lilypond, 12:34
  • Re: [Lilypond-auto] Issue 1263 in lilypond: MetronomeMark can not be aligned on note if MMR in another voice, lilypond, 10:06
  • Re: [Lilypond-auto] Issue 3012 in lilypond: Patch: Flag an error for isolated post-events occuring in music lists, lilypond, 09:39
  • Re: [Lilypond-auto] Issue 1263 in lilypond: MetronomeMark can not be aligned on note if MMR in another voice, lilypond, 07:42
  • Re: [Lilypond-auto] Issue 3012 in lilypond: Patch: Flag an error for isolated post-events occuring in music lists, lilypond, 07:13
  • Re: [Lilypond-auto] Issue 3012 in lilypond: Patch: Flag an error for isolated post-events occuring in music lists, lilypond, 06:57
  • Re: [Lilypond-auto] Issue 2970 in lilypond: Patch: Doc: include aliases for note name languages., lilypond, 06:19
  • Re: [Lilypond-auto] Issue 1263 in lilypond: MetronomeMark can not be aligned on note if MMR in another voice, lilypond, 04:17
  • Re: [Lilypond-auto] Issue 3042 in lilypond: MetronomeMarks do not align correctly when MultiMeasureRest is parent, lilypond, 04:16
  • [Lilypond-auto] Issue 3042 in lilypond: MetronomeMarks do not align correctly when MultiMeasureRest is parent, lilypond, 02:45
  • [Lilypond-auto] Patchy report, grenouille, 02:38
• December 18, 2012
  • [Lilypond-auto] Patchy report, grenouille, 22:35
  • Re: [Lilypond-auto] Issue 3012 in lilypond: Patch: Flag an error for isolated post-events occuring in music lists, lilypond, 21:43
  • Re: [Lilypond-auto] Issue 3013 in lilypond: Patch: Amend \overrideProperty example, lilypond, 21:41
  • Re: [Lilypond-auto] Issue 3019 in lilypond: Patch: Let ly:event-property take an optional default argument, lilypond, 21:40
  • Re: [Lilypond-auto] Issue 3016 in lilypond: Fix of bad example in \rest-by-number, lilypond, 21:39
  • Re: [Lilypond-auto] Issue 3019 in lilypond: Patch: Let ly:event-property take an optional default argument, lilypond, 21:38
  • Re: [Lilypond-auto] Issue 3013 in lilypond: Patch: Amend \overrideProperty example, lilypond, 21:36
  • Re: [Lilypond-auto] Issue 3012 in lilypond: Patch: Flag an error for isolated post-events occuring in music lists, lilypond, 21:35
  • Re: [Lilypond-auto] Issue 3010 in lilypond: Removes '-signs from vectors, lilypond, 21:34
  • Re: [Lilypond-auto] Issue 2971 in lilypond: Clarify the limitation on footnotes as articulations, lilypond, 21:33
  • [Lilypond-auto] Patchy report, grenouille, 18:39
  • Re: [Lilypond-auto] Issue 3034 in lilypond: DOC: Thumb but also "finger changes" should be Fingering, lilypond, 16:07
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 14:59
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 13:51
  • Re: [Lilypond-auto] Issue 3040 in lilypond: Segfault (infinite recursion) in add_interior_skylines, lilypond, 13:26
  • Re: [Lilypond-auto] Issue 3041 in lilypond: Patch: Fix a few segfaulting cases in hara-kiri-group-spanner, lilypond, 13:07
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 13:04
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 12:50
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 12:30
  • Re: [Lilypond-auto] Issue 3041 in lilypond: Patch: Fix a few segfaulting cases in hara-kiri-group-spanner, lilypond, 11:53
  • Re: [Lilypond-auto] Issue 732 in lilypond: Alignment problems when vertically stacking horizontally centered stencils., lilypond, 11:37
  • Re: [Lilypond-auto] Issue 2916 in lilypond: Doc : NR Document \hide command, lilypond, 11:36
  • Re: [Lilypond-auto] Issue 2972 in lilypond: Adding StringNumber 0 in TabStaff crashes, lilypond, 11:35
  • Re: [Lilypond-auto] Issue 2981 in lilypond: Let \set ... = *undefined* unset values rather than overwriting, lilypond, 11:34
  • Re: [Lilypond-auto] Issue 2982 in lilypond: Patch: Remove "selective" contextmods., lilypond, 11:33
  • Re: [Lilypond-auto] Issue 2984 in lilypond: Patch: Use define-void-function rather than define-music-function in several places, lilypond, 11:32
  • Re: [Lilypond-auto] Issue 2991 in lilypond: Ensure all level 3 and 4 headings have nodes (2), lilypond, 11:31
  • Re: [Lilypond-auto] Issue 2993 in lilypond: The improved positioning of Slurs has made an example in the LM redundant, lilypond, 11:30
  • Re: [Lilypond-auto] Issue 2996 in lilypond: Patch: Eliminate LYRIC_MARKUP and LYRICS_STRING tokens, lilypond, 11:29
  • Re: [Lilypond-auto] Issue 2997 in lilypond: Patch: parser.yy: avoid premature work in make_music_from_simple, lilypond, 11:28
  • Re: [Lilypond-auto] Issue 3000 in lilypond: Explain how to suppress cautionary accidentals following an explicit key change, lilypond, 11:27
  • Re: [Lilypond-auto] Issue 3005 in lilypond: Patch: A bit of rectification for learning/tweaks regarding Scheme values, lilypond, 11:26
  • Re: [Lilypond-auto] Issue 3008 in lilypond: articulate can't deal with <>, lilypond, 11:25
  • Re: [Lilypond-auto] Issue 3009 in lilypond: Patch: Make \revert work again as context modification, lilypond, 11:14
  • Re: [Lilypond-auto] Issue 3037 in lilypond: The end of a ligature bracket doesn't appear at the start of a line, lilypond, 10:01
  • Re: [Lilypond-auto] Issue 3041 in lilypond: Patch: Fix a few segfaulting cases in hara-kiri-group-spanner, lilypond, 09:56
  • Re: [Lilypond-auto] Issue 3041 in lilypond: Patch: Fix a few segfaulting cases in hara-kiri-group-spanner, lilypond, 09:39
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 08:28
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 08:27
  • Re: [Lilypond-auto] Issue 3041 in lilypond: Patch: Fix a few segfaulting cases in hara-kiri-group-spanner, lilypond, 08:09
  • Re: [Lilypond-auto] Issue 3040 in lilypond: Segfault (infinite recursion) in add_interior_skylines, lilypond, 08:02
  • Re: [Lilypond-auto] Issue 3041 in lilypond: Patch: Fix a few segfaulting cases in hara-kiri-group-spanner, lilypond, 07:59
  • Re: [Lilypond-auto] Issue 3041 in lilypond: Patch: Fix a few segfaulting cases in hara-kiri-group-spanner, lilypond, 07:55
  • Re: [Lilypond-auto] Issue 3041 in lilypond: Patch: Fix a few segfaulting cases in hara-kiri-group-spanner, lilypond, 07:53
  • [Lilypond-auto] Issue 3041 in lilypond: Patch: Fix a few segfaulting cases in hara-kiri-group-spanner, lilypond, 07:05
  • Re: [Lilypond-auto] Issue 3041 in lilypond: Patch: Fix a few segfaulting cases in hara-kiri-group-spanner, lilypond, 07:05
  • Re: [Lilypond-auto] Issue 3040 in lilypond: Segfault (infinite recursion) in add_interior_skylines, lilypond, 05:42
  • Re: [Lilypond-auto] Issue 2990 in lilypond: \RemoveEmptyStaves in StaffGroup context crashes, lilypond, 05:41
  • Re: [Lilypond-auto] Issue 3040 in lilypond: Segfault (infinite recursion) in add_interior_skylines, lilypond, 05:22
  • Re: [Lilypond-auto] Issue 3040 in lilypond: Segfault (infinite recursion) in add_interior_skylines, lilypond, 05:19
  • Re: [Lilypond-auto] Issue 3040 in lilypond: Segfault (infinite recursion) in add_interior_skylines, lilypond, 05:08
  • [Lilypond-auto] Issue 3040 in lilypond: Segfault (infinite recursion) in add_interior_skylines, lilypond, 04:50
  • Re: [Lilypond-auto] Issue 3037 in lilypond: The end of a ligature bracket doesn't appear at the start of a line, lilypond, 03:44
  • Re: [Lilypond-auto] Issue 3037 in lilypond: The end of a ligature bracket doesn't appear at the start of a line, lilypond, 03:40
  • Re: [Lilypond-auto] Issue 2724 in lilypond: This natural stem is too short, lilypond, 02:58
  • Re: [Lilypond-auto] Issue 2348 in lilypond: Patch: Handling of open strings in tablature, lilypond, 01:52
  • Re: [Lilypond-auto] Issue 3015 in lilypond: Move Appendix C to the NR, LilyPond Grammar, to the CG, lilypond, 01:24
• December 17, 2012
  • [Lilypond-auto] Patchy report, grenouille, 21:36
  • Re: [Lilypond-auto] Issue 2864 in lilypond: [Doc]Productions: The critical edition of Tommaso Traetta's Enea nel Lazio (1760), lilypond, 17:17
  • Re: [Lilypond-auto] Issue 2741 in lilypond: Thank donations and services for development infrastructure, lilypond, 17:16
  • Re: [Lilypond-auto] Issue 2741 in lilypond: Thank donations and services for development infrastructure, lilypond, 17:15
  • Re: [Lilypond-auto] Issue 2864 in lilypond: [Doc]Productions: The critical edition of Tommaso Traetta's Enea nel Lazio (1760), lilypond, 17:14
  • Re: [Lilypond-auto] Issue 3015 in lilypond: Move Appendix C to the NR, LilyPond Grammar, to the CG, lilypond, 16:53
  • Re: [Lilypond-auto] Issue 2741 in lilypond: Thank donations and services for development infrastructure, lilypond, 16:30
  • Re: [Lilypond-auto] Issue 2864 in lilypond: [Doc]Productions: The critical edition of Tommaso Traetta's Enea nel Lazio (1760), lilypond, 15:37
  • Re: [Lilypond-auto] Issue 3021 in lilypond: wrong midi instrument in NR, lilypond, 15:04
  • Re: [Lilypond-auto] Issue 3021 in lilypond: wrong midi instrument in NR, lilypond, 15:03
  • Re: [Lilypond-auto] Issue 2527 in lilypond: Finger-flag collision, lilypond, 14:51
  • Re: [Lilypond-auto] Issue 2348 in lilypond: Patch: Handling of open strings in tablature, lilypond, 13:40
  • Re: [Lilypond-auto] Issue 3029 in lilypond: restrainOpenStrings and minimumFret, lilypond, 13:39
  • Re: [Lilypond-auto] Issue 2348 in lilypond: Patch: Handling of open strings in tablature, lilypond, 13:38
  • Re: [Lilypond-auto] Issue 1523 in lilypond: Parenthesizing breath marks, lilypond, 12:02
  • Re: [Lilypond-auto] Issue 1523 in lilypond: Parenthesizing breath marks, lilypond, 11:17
  • [Lilypond-auto] Issue 3039 in lilypond: Certain loose columns don't block before barlines, lilypond, 10:33
  • [Lilypond-auto] Issue 3038 in lilypond: Add countUnfoldRepeats feature to new Measure_counter_engraver, lilypond, 06:20
  • Re: [Lilypond-auto] Issue 2527 in lilypond: Finger-flag collision, lilypond, 05:50
  • Re: [Lilypond-auto] Issue 3014 in lilypond: Allow for non-continuing broken spanners, lilypond, 05:45
  • [Lilypond-auto] Issue 3037 in lilypond: The end of a ligature bracket doesn't appear at the start of a line, lilypond, 05:37
  • Re: [Lilypond-auto] Issue 3036 in lilypond: Ligature brackets and suggested accidentals don't avoid each other well, lilypond, 05:27
  • [Lilypond-auto] Issue 3036 in lilypond: Ligature brackets and suggested accidentals don't avoid each other well, lilypond, 05:26
  • [Lilypond-auto] Issue 3035 in lilypond: Lyrics too cozy with notes, lilypond, 05:01
  • Re: [Lilypond-auto] Issue 3032 in lilypond: \textLengthOn no longer works correctly, lilypond, 04:41
  • Re: [Lilypond-auto] Issue 3032 in lilypond: \textLengthOn no longer works correctly, lilypond, 04:06
  • Re: [Lilypond-auto] Issue 3034 in lilypond: DOC: Thumb but also "finger changes" should be Fingering, lilypond, 03:39
  • [Lilypond-auto] Patchy report, grenouille, 02:43
  • [Lilypond-auto] Issue 3034 in lilypond: DOC: Thumb but also "finger changes" should be Fingering, lilypond, 01:48
• December 16, 2012
  • [Lilypond-auto] Patchy report, grenouille, 22:36
  • [Lilypond-auto] Patchy report, grenouille, 18:37
  • Re: [Lilypond-auto] Issue 3032 in lilypond: \textLengthOn no longer works correctly, lilypond, 18:36
  • Re: [Lilypond-auto] Issue 3032 in lilypond: \textLengthOn no longer works correctly, lilypond, 18:28
  • Re: [Lilypond-auto] Issue 3033 in lilypond: Doc: Usage - clarifying the documentation of advanced command-line options, lilypond, 18:04
  • Re: [Lilypond-auto] Issue 3004 in lilypond: Web documentation needs updates, lilypond, 18:03
  • Re: [Lilypond-auto] Issue 3033 in lilypond: Doc: Usage - clarifying the documentation of advanced command-line options, lilypond, 17:18
  • Re: [Lilypond-auto] Issue 3031 in lilypond: slur between notes inside chords, lilypond, 15:49
  • [Lilypond-auto] Issue 3033 in lilypond: Doc: Usage - clarifying the documentation of advanced command-line options, lilypond, 14:21
  • Re: [Lilypond-auto] Issue 3004 in lilypond: Web documentation needs updates, lilypond, 14:17
  • [Lilypond-auto] Issue 3032 in lilypond: \textLengthOn no longer works correctly, lilypond, 13:27
  • Re: [Lilypond-auto] Issue 3021 in lilypond: wrong midi instrument in NR, lilypond, 09:48
  • Re: [Lilypond-auto] Issue 3021 in lilypond: wrong midi instrument in NR, lilypond, 09:48
  • [Lilypond-auto] Issue 3031 in lilypond: slur between notes inside chords, lilypond, 09:19
  • Re: [Lilypond-auto] Issue 3028 in lilypond: lyqi link from LP web site not valid, lilypond, 08:57
  • Re: [Lilypond-auto] Issue 3028 in lilypond: lyqi link from LP web site not valid, lilypond, 08:56
  • Re: [Lilypond-auto] Issue 3017 in lilypond: Finger numbers and string numbers are placed wrongly when not using chord <> braces, lilypond, 08:16
  • [Lilypond-auto] Patchy email, phileholmes, 08:06
  • Re: [Lilypond-auto] Issue 2908 in lilypond: Cross-staff arpeggios and dynamics collide, lilypond, 08:02
  • Re: [Lilypond-auto] Issue 3017 in lilypond: Finger numbers and string numbers are placed wrongly when not using chord <> braces, lilypond, 08:01
  • Re: [Lilypond-auto] Issue 3026 in lilypond: staff-padding should measure to the alignment-points, lilypond, 08:01
  • Re: [Lilypond-auto] Issue 3021 in lilypond: wrong midi instrument in NR, lilypond, 07:35
  • Re: [Lilypond-auto] Issue 3028 in lilypond: lyqi link from LP web site not valid, lilypond, 07:34
  • Re: [Lilypond-auto] Issue 2172 in lilypond: Get line and column numbers right., lilypond, 06:58
  • Re: [Lilypond-auto] Issue 2172 in lilypond: Get line and column numbers right., lilypond, 06:57
  • Re: [Lilypond-auto] Issue 2172 in lilypond: Get line and column numbers right., lilypond, 06:47
  • Re: [Lilypond-auto] Issue 2172 in lilypond: Get line and column numbers right., lilypond, 06:46
  • Re: [Lilypond-auto] Issue 2527 in lilypond: Finger-flag collision, lilypond, 06:42
  • Re: [Lilypond-auto] Issue 2172 in lilypond: Get line and column numbers right., lilypond, 06:35
  • Re: [Lilypond-auto] Issue 2527 in lilypond: Finger-flag collision, lilypond, 06:02
  • Re: [Lilypond-auto] Issue 2527 in lilypond: Finger-flag collision, lilypond, 06:01
  • Re: [Lilypond-auto] Issue 2527 in lilypond: Finger-flag collision, lilypond, 05:58
  • Re: [Lilypond-auto] Issue 2172 in lilypond: Get line and column numbers right., lilypond, 05:47
  • [Lilypond-auto] Issue 3030 in lilypond: midi2ly failure, lilypond, 05:18
  • Re: [Lilypond-auto] Issue 3029 in lilypond: restrainOpenStrings and minimumFret, lilypond, 04:23
  • [Lilypond-auto] Issue 3029 in lilypond: restrainOpenStrings and minimumFret, lilypond, 04:08
  • [Lilypond-auto] Issue 3028 in lilypond: lyqi link from LP web site not valid, lilypond, 03:42
  • [Lilypond-auto] Issue 3027 in lilypond: Changing document fonts with non-standard global font size leads to scaling errors, lilypond, 03:31
• December 15, 2012
  • [Lilypond-auto] Patchy report, grenouille, 21:34
  • Re: [Lilypond-auto] Issue 2348 in lilypond: Patch: Handling of open strings in tablature, lilypond, 16:19
  • [Lilypond-auto] Issue 3026 in lilypond: staff-padding should measure to the alignment-points, lilypond, 15:56
  • [Lilypond-auto] Patchy email, phileholmes, 08:28
  • Re: [Lilypond-auto] Issue 2895 in lilypond: Enhancement request for web page http://lilypond.org/manuals.html, lilypond, 07:49
  • [Lilypond-auto] Issue 3025 in lilypond: crossStaff breaks, if stem-direction changes, lilypond, 07:01
  • Re: [Lilypond-auto] Issue 3024 in lilypond: Patch: Add dead-is-alive boolean property to Hara_kiri_group_spanner, lilypond, 05:43
  • Re: [Lilypond-auto] Issue 3024 in lilypond: Patch: Add dead-is-alive boolean property to Hara_kiri_group_spanner, lilypond, 05:24
  • Re: [Lilypond-auto] Issue 3024 in lilypond: Patch: Add dead-is-alive boolean property to Hara_kiri_group_spanner, lilypond, 04:30
  • [Lilypond-auto] Issue 3024 in lilypond: Patch: Add dead-is-alive boolean property to Hara_kiri_group_spanner, lilypond, 04:29
• December 14, 2012
  • [Lilypond-auto] Patchy report, grenouille, 21:35
  • Re: [Lilypond-auto] Issue 3023 in lilypond: Automatic scaling to landscape paper size leads to collisions, lilypond, 10:17
  • Re: [Lilypond-auto] Issue 3021 in lilypond: wrong midi instrument in NR, lilypond, 09:57
  • Re: [Lilypond-auto] Issue 3023 in lilypond: Automatic scaling to landscape paper size leads to collisions, lilypond, 09:34
  • [Lilypond-auto] Issue 3023 in lilypond: Automatic scaling to landscape paper size leads to collisions, lilypond, 05:45
  • [Lilypond-auto] Issue 3022 in lilypond: Documentation: NoteHead X-offset conflict with ly:grob-relative-coordinate, lilypond, 05:25
  • Re: [Lilypond-auto] Issue 2981 in lilypond: Let \set ... = *undefined* unset values rather than overwriting, lilypond, 03:52
  • Re: [Lilypond-auto] Issue 3008 in lilypond: articulate can't deal with <>, lilypond, 03:51
  • [Lilypond-auto] Issue 3021 in lilypond: wrong midi instrument in NR, lilypond, 03:50
  • [Lilypond-auto] Patchy report, grenouille, 02:09
  • Re: [Lilypond-auto] Issue 3008 in lilypond: articulate can't deal with <>, lilypond, 00:21
  • Re: [Lilypond-auto] Issue 2981 in lilypond: Let \set ... = *undefined* unset values rather than overwriting, lilypond, 00:20
• December 13, 2012
  • [Lilypond-auto] Patchy report, grenouille, 22:08
  • [Lilypond-auto] Patchy report, grenouille, 18:37
  • Re: [Lilypond-auto] Issue 3018 in lilypond: Patch: lilypond-mode.el: Replace use of obsoleted compile-internal, lilypond, 17:17
  • Re: [Lilypond-auto] Issue 3020 in lilypond: Patch: Documentation/GNUmakefile: Add dependencies for internals.texi, lilypond, 17:16
  • [Lilypond-auto] Issue 3020 in lilypond: Patch: Documentation/GNUmakefile: Add dependencies for internals.texi, lilypond, 16:43
  • Re: [Lilypond-auto] Issue 1029 in lilypond: \thumb should behave like other fingerings, lilypond, 15:42
  • Re: [Lilypond-auto] Issue 1029 in lilypond: \thumb should behave like other fingerings, lilypond, 12:44
  • Re: [Lilypond-auto] Issue 1029 in lilypond: \thumb should behave like other fingerings, lilypond, 12:17
  • Re: [Lilypond-auto] Issue 3019 in lilypond: Patch: Let ly:event-property take an optional default argument, lilypond, 11:43
  • Re: [Lilypond-auto] Issue 1029 in lilypond: \thumb should behave like other fingerings, lilypond, 11:19
  • Re: [Lilypond-auto] Issue 3019 in lilypond: Patch: Let ly:event-property take an optional default argument, lilypond, 10:09
  • [Lilypond-auto] Issue 3019 in lilypond: Patch: Let ly:event-property take an optional default argument, lilypond, 10:08
  • Re: [Lilypond-auto] Issue 3016 in lilypond: Fix of bad example in \rest-by-number, lilypond, 08:33
  • Re: [Lilypond-auto] Issue 2172 in lilypond: Get line and column numbers right., lilypond, 08:28
  • Re: [Lilypond-auto] Issue 3016 in lilypond: Fix of bad example in \rest-by-number, lilypond, 07:54
  • Re: [Lilypond-auto] Issue 3016 in lilypond: Fix of bad example in \rest-by-number, lilypond, 07:50
  • Re: [Lilypond-auto] Issue 3016 in lilypond: Fix of bad example in \rest-by-number, lilypond, 07:24
  • Re: [Lilypond-auto] Issue 3016 in lilypond: Fix of bad example in \rest-by-number, lilypond, 07:08
  • Re: [Lilypond-auto] Issue 3018 in lilypond: Patch: lilypond-mode.el: Replace use of obsoleted compile-internal, lilypond, 06:41
  • Re: [Lilypond-auto] Issue 2172 in lilypond: Get line and column numbers right., lilypond, 06:03
  • [Lilypond-auto] Issue 3018 in lilypond: Patch: lilypond-mode.el: Replace use of obsoleted compile-internal, lilypond, 05:02
  • Re: [Lilypond-auto] Issue 3018 in lilypond: Patch: lilypond-mode.el: Replace use of obsoleted compile-internal, lilypond, 05:01
  • Re: [Lilypond-auto] Issue 3016 in lilypond: Fix of bad example in \rest-by-number, lilypond, 02:10
  • Re: [Lilypond-auto] Issue 1029 in lilypond: \thumb should behave like other fingerings, lilypond, 01:34
  • Re: [Lilypond-auto] Issue 1029 in lilypond: \thumb should behave like other fingerings, lilypond, 01:25
  • [Lilypond-auto] Issue 3017 in lilypond: Finger numbers and string numbers are placed wrongly when not using chord <> braces, lilypond, 00:20
• December 12, 2012
  • [Lilypond-auto] Patchy report, grenouille, 21:35
  • Re: [Lilypond-auto] Issue 3006 in lilypond: Clarify context creation in NR 5.1.2, lilypond, 18:32
  • Re: [Lilypond-auto] Issue 3016 in lilypond: Fix of bad example in \rest-by-number, lilypond, 17:04
  • [Lilypond-auto] Issue 3016 in lilypond: Fix of bad example in \rest-by-number, lilypond, 16:52
  • Re: [Lilypond-auto] Issue 2888 in lilypond: [musicxml2ly] beams and lost lyric syllables, lilypond, 10:48
  • Re: [Lilypond-auto] Issue 2888 in lilypond: [musicxml2ly] beams and lost lyric syllables, lilypond, 10:40
  • [Lilypond-auto] Patchy report, grenouille, 01:38
• December 11, 2012
  • [Lilypond-auto] Patchy report, grenouille, 21:56
  • Re: [Lilypond-auto] Issue 2971 in lilypond: Clarify the limitation on footnotes as articulations, lilypond, 18:22
  • [Lilypond-auto] Issue 3015 in lilypond: Move Appendix C to the NR, LilyPond Grammar, to the CG, lilypond, 18:21
  • Re: [Lilypond-auto] Issue 2971 in lilypond: Clarify the limitation on footnotes as articulations, lilypond, 18:07
  • [Lilypond-auto] Issue 3014 in lilypond: Allow for non-continuing broken spanners, lilypond, 17:38
  • Re: [Lilypond-auto] Issue 2966 in lilypond: Enhancement: introduces rest-by-number and rest, lilypond, 17:16
  • Re: [Lilypond-auto] Issue 734 in lilypond: tremolos beams placement on a (single) whole note, lilypond, 14:58
  • Re: [Lilypond-auto] Issue 2971 in lilypond: Clarify the limitation on footnotes as articulations, lilypond, 14:08
  • Re: [Lilypond-auto] Issue 3011 in lilypond: Crash moving voice into Devnull context, lilypond, 12:25
  • Re: [Lilypond-auto] Issue 2971 in lilypond: Clarify the limitation on footnotes as articulations, lilypond, 12:24
  • Re: [Lilypond-auto] Issue 3010 in lilypond: Removes '-signs from vectors, lilypond, 10:00
  • Re: [Lilypond-auto] Issue 3013 in lilypond: Patch: Amend \overrideProperty example, lilypond, 09:47
  • Re: [Lilypond-auto] Issue 3010 in lilypond: Removes '-signs from vectors, lilypond, 09:13
  • Re: [Lilypond-auto] Issue 3013 in lilypond: Patch: Amend \overrideProperty example, lilypond, 07:51
  • [Lilypond-auto] Issue 3013 in lilypond: Patch: Amend \overrideProperty example, lilypond, 07:50
  • Re: [Lilypond-auto] Issue 3012 in lilypond: Patch: Flag an error for isolated post-events occuring in music lists, lilypond, 07:03
  • [Lilypond-auto] Patchy report, grenouille, 06:36
  • Re: [Lilypond-auto] Issue 3012 in lilypond: Patch: Flag an error for isolated post-events occuring in music lists, lilypond, 06:31
  • [Lilypond-auto] Issue 3012 in lilypond: Patch: Flag an error for isolated post-events occuring in music lists, lilypond, 06:30
  • Re: [Lilypond-auto] Issue 3005 in lilypond: Patch: A bit of rectification for learning/tweaks regarding Scheme values, lilypond, 04:22
  • Re: [Lilypond-auto] Issue 3000 in lilypond: Explain how to suppress cautionary accidentals following an explicit key change, lilypond, 04:19
  • Re: [Lilypond-auto] Issue 2993 in lilypond: The improved positioning of Slurs has made an example in the LM redundant, lilypond, 04:16
  • Re: [Lilypond-auto] Issue 3000 in lilypond: Explain how to suppress cautionary accidentals following an explicit key change, lilypond, 00:58
  • Re: [Lilypond-auto] Issue 3005 in lilypond: Patch: A bit of rectification for learning/tweaks regarding Scheme values, lilypond, 00:57
  • Re: [Lilypond-auto] Issue 3001 in lilypond: Patch: Changes to Kievan documentation, lilypond, 00:56
  • Re: [Lilypond-auto] Issue 3000 in lilypond: Explain how to suppress cautionary accidentals following an explicit key change, lilypond, 00:55
  • Re: [Lilypond-auto] Issue 2993 in lilypond: The improved positioning of Slurs has made an example in the LM redundant, lilypond, 00:54
  • Re: [Lilypond-auto] Issue 2966 in lilypond: Enhancement: introduces rest-by-number and rest, lilypond, 00:53
  • Re: [Lilypond-auto] Issue 2895 in lilypond: Enhancement request for web page http://lilypond.org/manuals.html, lilypond, 00:52
• December 10, 2012
  • [Lilypond-auto] Patchy report, grenouille, 21:08
  • [Lilypond-auto] Issue 3011 in lilypond: Crash moving voice into Devnull context, lilypond, 20:21
  • [Lilypond-auto] Issue 3010 in lilypond: Removes '-signs from vectors, lilypond, 19:18
  • [Lilypond-auto] Patchy report, grenouille, 18:31
  • [Lilypond-auto] Patchy report, grenouille, 16:39
  • Re: [Lilypond-auto] Issue 2998 in lilypond: Patch: IR: Improve performer documentation, lilypond, 15:59
  • Re: [Lilypond-auto] Issue 3003 in lilypond: Document the MIDI backend, lilypond, 15:58
  • [Lilypond-auto] Patchy report, grenouille, 11:48
  • Re: [Lilypond-auto] Issue 2971 in lilypond: Clarify the limitation on footnotes as articulations, lilypond, 10:13
  • [Lilypond-auto] Patchy report, grenouille, 05:48
  • Re: [Lilypond-auto] Issue 1228 in lilypond: \override RestCollision #'positioning-done = #merge-rests-on-positioning, lilypond, 05:03
  • Re: [Lilypond-auto] Issue 2971 in lilypond: Clarify the limitation on footnotes as articulations, lilypond, 04:48
  • [Lilypond-auto] Patchy report, grenouille, 00:49
• December 09, 2012
  • Re: [Lilypond-auto] Issue 2794 in lilypond: Bookparts have lost their page numbers, lilypond, 23:45
  • [Lilypond-auto] Patchy report, grenouille, 21:34
  • [Lilypond-auto] Patchy report, grenouille, 17:48
  • Re: [Lilypond-auto] Issue 2794 in lilypond: Bookparts have lost their page numbers, lilypond, 17:35
  • Re: [Lilypond-auto] Issue 2989 in lilypond: Funny alignment of different bar lines at the end of a system, lilypond, 16:15
  • [Lilypond-auto] Patchy report, grenouille, 11:48
  • Re: [Lilypond-auto] Issue 2877 in lilypond: [Doc]NR 3.5.7: the articulate script: why not suggesting two \score blocks?, lilypond, 09:50
  • Re: [Lilypond-auto] Issue 2981 in lilypond: Let \set ... = *undefined* unset values rather than overwriting, lilypond, 09:20
  • Re: [Lilypond-auto] Issue 2981 in lilypond: Let \set ... = *undefined* unset values rather than overwriting, lilypond, 08:52
  • Re: [Lilypond-auto] Issue 2981 in lilypond: Bugs with \set Staff.whichBar, lilypond, 08:47
  • Re: [Lilypond-auto] Issue 3008 in lilypond: articulate can't deal with <>, lilypond, 07:46
  • Re: [Lilypond-auto] Issue 2981 in lilypond: Bugs with \set Staff.whichBar, lilypond, 07:45
  • Re: [Lilypond-auto] Issue 2981 in lilypond: Bugs with \set Staff.whichBar, lilypond, 07:22
  • Re: [Lilypond-auto] Issue 2877 in lilypond: [Doc]NR 3.5.7: the articulate script: why not suggesting two \score blocks?, lilypond, 05:54
  • [Lilypond-auto] Patchy report, grenouille, 05:48
  • Re: [Lilypond-auto] Issue 3008 in lilypond: articulate can't deal with <>, lilypond, 04:34
  • [Lilypond-auto] Patchy report, grenouille, 00:50
• December 08, 2012
  • [Lilypond-auto] Patchy report, grenouille, 21:34
  • [Lilypond-auto] Patchy report, grenouille, 17:48
  • Re: [Lilypond-auto] Issue 2981 in lilypond: Bugs with \set Staff.whichBar, lilypond, 17:43
  • Re: [Lilypond-auto] Issue 2989 in lilypond: Funny alignment of different bar lines at the end of a system, lilypond, 17:39
  • Re: [Lilypond-auto] Issue 2989 in lilypond: Funny alignment of different bar lines at the end of a system, lilypond, 17:17
  • Re: [Lilypond-auto] Issue 245 in lilypond: partcombine multiple tuplet brackets false warning, lilypond, 16:51
  • [Lilypond-auto] Patchy report, grenouille, 11:48
  • Re: [Lilypond-auto] Issue 2777 in lilypond: Learning Manual has version 2.14.2 instead of 2.16.0, lilypond, 11:13
  • Re: [Lilypond-auto] Issue 3009 in lilypond: Patch: Make \revert work again as context modification, lilypond, 06:28
  • Re: [Lilypond-auto] Issue 3009 in lilypond: Patch: Make \revert work again as context modification, lilypond, 06:03
  • [Lilypond-auto] Patchy report, grenouille, 05:48
  • Re: [Lilypond-auto] Issue 3009 in lilypond: Patch: Make \revert work again as context modification, lilypond, 05:28
  • Re: [Lilypond-auto] Issue 3009 in lilypond: Patch: Make \revert work again as context modification, lilypond, 05:23
  • [Lilypond-auto] Issue 3009 in lilypond: Patch: Make \revert work again as context modification, lilypond, 05:22
  • [Lilypond-auto] Patchy report, grenouille, 00:50
• December 07, 2012
  • [Lilypond-auto] Patchy report, grenouille, 21:35
  • [Lilypond-auto] Patchy report, grenouille, 17:51
  • [Lilypond-auto] Issue 3008 in lilypond: articulate can't deal with <>, lilypond, 16:18
  • [Lilypond-auto] Patchy report, grenouille, 11:48
  • Re: [Lilypond-auto] Issue 2996 in lilypond: Patch: Eliminate LYRIC_MARKUP and LYRICS_STRING tokens, lilypond, 08:47
  • Re: [Lilypond-auto] Issue 2801 in lilypond: Patch: Approximates cross-staff slurs in VerticalAxisGroup vertical-skylines., lilypond, 08:06
  • [Lilypond-auto] Patchy report, grenouille, 05:48
  • Re: [Lilypond-auto] Issue 2991 in lilypond: Ensure all level 3 and 4 headings have nodes (2), lilypond, 02:55
  • [Lilypond-auto] Patchy report, grenouille, 00:49
  • Re: [Lilypond-auto] Issue 2996 in lilypond: Patch: Eliminate LYRIC_MARKUP and LYRICS_STRING tokens, lilypond, 00:32
  • Re: [Lilypond-auto] Issue 2991 in lilypond: Ensure all level 3 and 4 headings have nodes (2), lilypond, 00:31
  • Re: [Lilypond-auto] Issue 2527 in lilypond: Finger-flag collision, lilypond, 00:30
• December 06, 2012
  • [Lilypond-auto] Patchy report, grenouille, 21:34
  • [Lilypond-auto] Patchy report, grenouille, 17:50
  • Re: [Lilypond-auto] Issue 2989 in lilypond: Funny alignment of different bar lines at the end of a system, lilypond, 15:20
  • [Lilypond-auto] Issue 3007 in lilypond: Implement customizable fret-diagram mark properties, lilypond, 15:05
  • Re: [Lilypond-auto] Issue 3005 in lilypond: Patch: A bit of rectification for learning/tweaks regarding Scheme values, lilypond, 08:44
  • Re: [Lilypond-auto] Issue 3005 in lilypond: Patch: A bit of rectification for learning/tweaks regarding Scheme values, lilypond, 08:06
• December 05, 2012
  • [Lilypond-auto] Patchy report, grenouille, 21:34
  • Re: [Lilypond-auto] Issue 3005 in lilypond: Patch: A bit of rectification for learning/tweaks regarding Scheme values, lilypond, 19:28
  • Re: [Lilypond-auto] Issue 2966 in lilypond: Enhancement: introduces rest-by-number and rest, lilypond, 19:21
  • Re: [Lilypond-auto] Issue 3000 in lilypond: Explain how to suppress cautionary accidentals following an explicit key change, lilypond, 19:20
  • Re: [Lilypond-auto] Issue 2926 in lilypond: divisioMaior broke, lilypond, 16:09
  • [Lilypond-auto] Issue 3006 in lilypond: Clarify context creation in NR 5.1.2, lilypond, 03:57
  • Re: [Lilypond-auto] Issue 732 in lilypond: Alignment problems when vertically stacking horizontally centered stencils., lilypond, 00:53
• December 04, 2012
  • [Lilypond-auto] Patchy report, grenouille, 21:34
  • Re: [Lilypond-auto] Issue 2966 in lilypond: Enhancement: introduces rest-by-number and rest, lilypond, 20:01
  • Re: [Lilypond-auto] Issue 3000 in lilypond: Explain how to suppress cautionary accidentals following an explicit key change, lilypond, 17:36
  • Re: [Lilypond-auto] Issue 3005 in lilypond: Patch: A bit of rectification for learning/tweaks regarding Scheme values, lilypond, 16:03
  • [Lilypond-auto] Issue 3005 in lilypond: Patch: A bit of rectification for learning/tweaks regarding Scheme values, lilypond, 16:02
  • Re: [Lilypond-auto] Issue 2895 in lilypond: Enhancement request for web page http://lilypond.org/manuals.html, lilypond, 14:12
  • Re: [Lilypond-auto] Issue 2895 in lilypond: Enhancement request for web page http://lilypond.org/manuals.html, lilypond, 13:37
  • Re: [Lilypond-auto] Issue 3002 in lilypond: fret-diagram-interface, lilypond, 12:46
  • Re: [Lilypond-auto] Issue 2982 in lilypond: Patch: Remove "selective" contextmods., lilypond, 10:30
  • Re: [Lilypond-auto] Issue 2916 in lilypond: Doc : NR Document \hide command, lilypond, 03:09
  • Re: [Lilypond-auto] Issue 2982 in lilypond: Patch: Remove "selective" contextmods., lilypond, 03:08
  • Re: [Lilypond-auto] Issue 2972 in lilypond: Adding StringNumber 0 in TabStaff crashes, lilypond, 03:06
  • Re: [Lilypond-auto] Issue 2984 in lilypond: Patch: Use define-void-function rather than define-music-function in several places, lilypond, 03:05
  • Re: [Lilypond-auto] Issue 2998 in lilypond: Patch: IR: Improve performer documentation, lilypond, 00:51
  • Re: [Lilypond-auto] Issue 732 in lilypond: Alignment problems when vertically stacking horizontally centered stencils., lilypond, 00:49
  • Re: [Lilypond-auto] Issue 2984 in lilypond: Patch: Use define-void-function rather than define-music-function in several places, lilypond, 00:43
  • Re: [Lilypond-auto] Issue 2972 in lilypond: Adding StringNumber 0 in TabStaff crashes, lilypond, 00:42
  • Re: [Lilypond-auto] Issue 2916 in lilypond: Doc : NR Document \hide command, lilypond, 00:41
  • Re: [Lilypond-auto] Issue 2982 in lilypond: Patch: Remove "selective" contextmods., lilypond, 00:40
  • Re: [Lilypond-auto] Issue 2527 in lilypond: Finger-flag collision, lilypond, 00:39
• December 03, 2012
  • [Lilypond-auto] Patchy report, grenouille, 22:06
  • Re: [Lilypond-auto] Issue 3002 in lilypond: fret-diagram-interface, lilypond, 19:41
  • Re: [Lilypond-auto] Issue 3001 in lilypond: Patch: Changes to Kievan documentation, lilypond, 15:09
  • Re: [Lilypond-auto] Issue 2993 in lilypond: The improved positioning of Slurs has made an example in the LM redundant, lilypond, 15:08
  • Re: [Lilypond-auto] Issue 3002 in lilypond: fret-diagram-interface, lilypond, 13:40
  • Re: [Lilypond-auto] Issue 3002 in lilypond: fret-diagram-interface, lilypond, 13:29
  • [Lilypond-auto] Issue 3004 in lilypond: Web documentation needs updates, lilypond, 13:28
  • Re: [Lilypond-auto] Issue 3001 in lilypond: Patch: Changes to Kievan documentation, lilypond, 13:21
  • [Lilypond-auto] Issue 3003 in lilypond: Document the MIDI backend, lilypond, 09:24
  • Re: [Lilypond-auto] Issue 2997 in lilypond: Patch: parser.yy: avoid premature work in make_music_from_simple, lilypond, 08:51
  • Re: [Lilypond-auto] Issue 2997 in lilypond: Patch: parser.yy: avoid premature work in make_music_from_simple, lilypond, 08:50
  • Re: [Lilypond-auto] Issue 2995 in lilypond: Patch: git-cly: Update to latest upload.py from google, lilypond, 06:50
  • Re: [Lilypond-auto] Issue 2995 in lilypond: Patch: git-cly: Update to latest upload.py from google, lilypond, 06:43
  • Re: [Lilypond-auto] Issue 2966 in lilypond: Enhancement: introduces rest-by-number and rest, lilypond, 03:51
  • Re: [Lilypond-auto] Issue 2998 in lilypond: Patch: IR: Improve performer documentation, lilypond, 03:50
  • Re: [Lilypond-auto] Issue 3000 in lilypond: Explain how to suppress cautionary accidentals following an explicit key change, lilypond, 03:49
  • Re: [Lilypond-auto] Issue 3001 in lilypond: Patch: Changes to Kievan documentation, lilypond, 03:47
  • [Lilypond-auto] Issue 3002 in lilypond: fret-diagram-interface, lilypond, 02:51
• December 02, 2012
  • [Lilypond-auto] Patchy report, grenouille, 21:35
  • Re: [Lilypond-auto] Issue 2966 in lilypond: Enhancement: introduces rest-by-number and rest, lilypond, 21:04
  • Re: [Lilypond-auto] Issue 3001 in lilypond: Patch: Changes to Kievan documentation, lilypond, 19:41
  • Re: [Lilypond-auto] Issue 3001 in lilypond: Patch: Changes to Kievan documentation, lilypond, 19:38
  • [Lilypond-auto] Issue 3001 in lilypond: Patch: Changes to Kievan documentation, lilypond, 19:37
  • Re: [Lilypond-auto] Issue 3000 in lilypond: Explain how to suppress cautionary accidentals following an explicit key change, lilypond, 18:42
  • Re: [Lilypond-auto] Issue 3000 in lilypond: Explain how to suppress cautionary accidentals following an explicit key change, lilypond, 18:00
  • [Lilypond-auto] Issue 3000 in lilypond: Explain how to suppress cautionary accidentals following an explicit key change, lilypond, 17:55
  • Re: [Lilypond-auto] Issue 2943 in lilypond: [DOC] Centering dynamic, lilypond, 16:42
  • Re: [Lilypond-auto] Issue 2967 in lilypond: @unnumberedsubsubsec should always have an accompanying @node, lilypond, 16:41
  • Re: [Lilypond-auto] Issue 2973 in lilypond: Patch: parser.yy: give check_scheme_arg optional argument for error display, lilypond, 16:40
  • Re: [Lilypond-auto] Issue 2974 in lilypond: Patch: music-functions-init.ly: Avoid unnecessary use of $ instead of #, lilypond, 16:39
  • Re: [Lilypond-auto] Issue 2975 in lilypond: Patch: beam.cc: let a loop run backwards for better Scheme-fu., lilypond, 16:38
  • Re: [Lilypond-auto] Issue 2976 in lilypond: Patch: Allow ly:grob-set-nested-property! to set a single (unnested) property, lilypond, 16:37
  • Re: [Lilypond-auto] Issue 2977 in lilypond: Patch: Allow tweaks to deal with setting nested properties., lilypond, 16:36
  • Re: [Lilypond-auto] Issue 2936 in lilypond: Modify documentation text to match new syntax for \tweak, \override, etc, lilypond, 16:35
  • Re: [Lilypond-auto] Issue 2978 in lilypond: Patch: Simplify calculation of pitch-alist in determine-frets-and-strings, lilypond, 16:34
  • Re: [Lilypond-auto] Issue 2980 in lilypond: LM doc files in language subdirectories are incomplete, lilypond, 16:33
  • Re: [Lilypond-auto] Issue 2868 in lilypond: Patch: Various clean-ups in stems and beams., lilypond, 16:32
  • Re: [Lilypond-auto] Issue 2951 in lilypond: Patch: Allow music of nominally zero duration to be typeset., lilypond, 16:31
  • Re: [Lilypond-auto] Issue 2969 in lilypond: Patch: Fix and document usage of `convert-ly - < test.ly'., lilypond, 16:22
  • Re: [Lilypond-auto] Issue 2963 in lilypond: doc: chord notes and fret diagram indications don't match, lilypond, 16:20
  • Re: [Lilypond-auto] Issue 2999 in lilypond: Patch: Change to CG for purely testing purposes, lilypond, 09:46
  • Re: [Lilypond-auto] Issue 2999 in lilypond: Patch: Change to CG for purely testing purposes, lilypond, 09:46
  • [Lilypond-auto] Issue 2999 in lilypond: Patch: Change to CG for purely testing purposes, lilypond, 09:37
  • Re: [Lilypond-auto] Issue 2993 in lilypond: The improved positioning of Slurs has made an example in the LM redundant, lilypond, 06:17
  • [Lilypond-auto] Issue 2998 in lilypond: Patch: IR: Improve performer documentation, lilypond, 05:56
  • Re: [Lilypond-auto] Issue 2993 in lilypond: The improved positioning of Slurs has made an example in the LM redundant, lilypond, 03:30
  • Re: [Lilypond-auto] Issue 2991 in lilypond: Ensure all level 3 and 4 headings have nodes (2), lilypond, 03:13
  • Re: [Lilypond-auto] Issue 2991 in lilypond: Ensure all level 3 and 4 headings have nodes (2), lilypond, 02:54
  • Re: [Lilypond-auto] Issue 2967 in lilypond: @unnumberedsubsubsec should always have an accompanying @node, lilypond, 02:46
  • Re: [Lilypond-auto] Issue 2989 in lilypond: Funny alignment of different bar lines at the end of a system, lilypond, 01:00
• December 01, 2012
  • [Lilypond-auto] Patchy report, grenouille, 21:34
  • Re: [Lilypond-auto] Issue 2926 in lilypond: divisioMaior broke, lilypond, 18:10
  • Re: [Lilypond-auto] Issue 2989 in lilypond: Funny alignment of different bar lines at the end of a system, lilypond, 16:14
  • Re: [Lilypond-auto] Issue 2996 in lilypond: Patch: Eliminate LYRIC_MARKUP and LYRICS_STRING tokens, lilypond, 15:24
  • Re: [Lilypond-auto] Issue 2997 in lilypond: Patch: parser.yy: avoid premature work in make_music_from_simple, lilypond, 15:15
  • Re: [Lilypond-auto] Issue 2997 in lilypond: Patch: parser.yy: avoid premature work in make_music_from_simple, lilypond, 13:45
  • [Lilypond-auto] Issue 2997 in lilypond: Patch: parser.yy: avoid premature work in make_music_from_simple, lilypond, 13:44
  • Re: [Lilypond-auto] Issue 2996 in lilypond: Patch: Eliminate LYRIC_MARKUP and LYRICS_STRING tokens, lilypond, 13:18
  • [Lilypond-auto] Issue 2996 in lilypond: Patch: Eliminate LYRIC_MARKUP and LYRICS_STRING tokens, lilypond, 13:17
  • Re: [Lilypond-auto] Issue 2994 in lilypond: Patch: Test commit, lilypond, 12:25
  • Re: [Lilypond-auto] Issue 2995 in lilypond: Patch: git-cly: Update to latest upload.py from google, lilypond, 12:23
  • [Lilypond-auto] Issue 2995 in lilypond: Patch: git-cly: Update to latest upload.py from google, lilypond, 12:22
  • Re: [Lilypond-auto] Issue 2994 in lilypond: Patch: Test commit, lilypond, 12:20
  • [Lilypond-auto] Issue 2994 in lilypond: Patch: Test commit, lilypond, 12:19
  • Re: [Lilypond-auto] Issue 2989 in lilypond: Funny alignment of different bar lines at the end of a system, lilypond, 07:53
  • [Lilypond-auto] Issue 2993 in lilypond: The improved positioning of Slurs has made an example in the LM redundant, lilypond, 07:08
  • [Lilypond-auto] Issue 2992 in lilypond: Closer nestling of grobs has spoilt some examples in the LM, lilypond, 06:52
  • Re: [Lilypond-auto] Issue 2985 in lilypond: lilypond: Umlauts and other special characters incorrectly exported to PDF meta data, lilypond, 06:39
  • Re: [Lilypond-auto] Issue 2985 in lilypond: lilypond: Umlauts and other special characters incorrectly exported to PDF meta data, lilypond, 06:18
  • [Lilypond-auto] Issue 2991 in lilypond: Ensure all level 3 and 4 headings have nodes (2), lilypond, 03:42

---

[Prev Period]

[Next Period]

---

Mail converted by MHonArc