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

bug-lilypond (date)

[Thread Index][Top][All Lists]

Advanced

[Prev Period]

Last Modified: Sun Jan 31 2010 23:45:51 -0500 Messages in reverse chronological order

[Next Period]

---

• January 31, 2010
  • bug team, Graham Percival, 23:45
• January 30, 2010
  • Re: Accidentals and Fingerings, Trevor Daniels, 19:14
  • Re: Issue 976 in lilypond: Difficulties with tablature angle brackets, lilypond, 17:40
  • Issue 1004 in lilypond: more thought needed for website integration, lilypond, 16:29
  • Re: [regtests] some other things to improve, Graham Percival, 15:56
  • Re: [regtests] some other things to improve, Joe Neeman, 15:44
  • Re: Issue 947 in lilypond: Build failure on OS X on std-vector.hh, lilypond, 11:42
  • Re: Issue 867 in lilypond: lilypond-book can have hash collisions, lilypond, 11:38
  • Re: Issue 859 in lilypond: unhack web-texi2html.pl, lilypond, 11:34
  • Re: Issue 854 in lilypond: lilycontrib.tcl, lilypond, 11:30
  • Re: Issue 749 in lilypond: SpacingSpanner doesn't work when using gregorian.ly, lilypond, 11:26
  • Re: [regtests] some other things to improve, Graham Percival, 11:09
  • Re: Issue 957 in lilypond: remove duplicate anchor generation in texi2html, lilypond, 10:58
  • Re: Issue 842 in lilypond: bibliography not built, lilypond, 10:54
  • [regtests] some other things to improve, Dmytro O. Redchuk, 05:53
  • Re: [2.13.11] Overriding font-name in markups increases font-size [was:] strange problem with markup in \tempo, Dmytro O. Redchuk, 05:27
• January 29, 2010
  • Re: Issue 405 in lilypond: tupletBracket not printed despite #'bracket-visibility=##t, lilypond, 15:03
  • Re: Issue 1003 in lilypond: Chord repetition: 'q' shall not repeat fingerings, lilypond, 13:50
  • Re: Issue 925 in lilypond: chord repetition character doesn't handle cautionaries correctly, lilypond, 13:39
  • Re: Issue 1003 in lilypond: Chord repetition: 'q' shall not repeat fingerings, lilypond, 13:03
  • Issue 1003 in lilypond: Chord repetition: 'q' shall not repeat fingerings, lilypond, 12:59
  • Re: Issue 405 in lilypond: tupletBracket not printed despite #'bracket-visibility=##t, lilypond, 10:06
  • Re: CG lilybuntu link issue, Trevor Daniels, 05:04
  • Re: Issue 541 in lilypond: Hebrew lyrics diacritic not well aligned, lilypond, 02:53
• January 28, 2010
  • Issue 1002 in lilypond: textedit URIs should correctly support backslashes in filenames, lilypond, 22:05
  • Re: Issue 1001 in lilypond: LilyPad cannot open filenames with non-ASCII characters, lilypond, 20:45
  • Re: Issue 379 in lilypond: ugly slur with key signature and linebreak, lilypond, 20:32
  • Re: Issue 887 in lilypond: Non-ASCII characters in textedit URIs should be percent-encoded, lilypond, 20:17
  • Issue 1001 in lilypond: LilyPad cannot open filenames with non-ASCII characters, lilypond, 20:13
  • Re: Issue 887 in lilypond: Non-ASCII characters in textedit URIs should be percent-encoded, lilypond, 19:58
  • Re: "centered dynamics" piano template broken on 2.13.11?, Patrick McCarty, 15:31
  • Re: "centered dynamics" piano template broken on 2.13.11?, Alexander Kobel, 15:25
  • Re: "centered dynamics" piano template broken on 2.13.11?, Patrick McCarty, 15:24
  • "centered dynamics" piano template broken on 2.13.11?, Ken, 15:15
  • Re: CG lilybuntu link issue, Valentin Villenave, 04:15
  • Re: CG lilybuntu link issue, Bertalan Fodor, 01:07
• January 27, 2010
  • Re: Font woes with lilypond on Ubuntu (was Re: svg output from version 2.13.12 cannot cope with numeric time signature), Patrick McCarty, 19:01
  • Re: CG lilybuntu link issue, Valentin Villenave, 18:47
  • Re: CG lilybuntu link issue, Valentin Villenave, 18:45
  • Re: Pango font tree not handled at non-default score size, Boris Shingarov, 15:51
  • Re: Pango font tree not handled at non-default score size, Neil Puttock, 15:45
  • Re: Issue 917 in lilypond: Regression: Full-bar rests take more space at the beginning of a line, lilypond, 09:50
  • Font woes with lilypond on Ubuntu (was Re: svg output from version 2.13.12 cannot cope with numeric time signature), Bernard Hurley, 09:44
  • Re: CG lilybuntu link issue, Graham Percival, 08:11
  • CG lilybuntu link issue, Bertalan Fodor (LilyPondTool), 07:24
  • minimum-Y-extent has no effect on Lyrics placement, Jiri Zurek (Prague), 06:32
  • Re: Pango font tree not handled at non-default score size, Boris Shingarov, 03:23
  • [2.13.11] Overriding font-name in markups increases font-size [was:] strange problem with markup in \tempo, Dmytro O. Redchuk, 03:12
• January 26, 2010
  • Re: Issue 405 in lilypond: tupletBracket not printed despite #'bracket-visibility=##t, Ian Hulin, 19:48
  • Re: Pango font tree not handled at non-default score size, Neil Puttock, 19:05
  • Re: Issue 836 in lilypond: [in progress] output-suffix as a (Score) context property, Ian Hulin, 18:12
  • Re: Page Spacer gets confused by next-space leading to unusable layout, Joe Neeman, 15:54
  • Re: Page Spacer gets confused by next-space leading to unusable layout, Joe Neeman, 15:50
  • Re: Issue 775 in lilypond: configure/autogen should detect doc requirements, lilypond, 14:16
  • Re: [2.13.11] strange problem with markup in \tempo, Dmytro O. Redchuk, 14:06
  • [2.13.11] strange problem with markup in \tempo, Dmytro O. Redchuk, 14:03
  • Re: Page Spacer gets confused by next-space leading to unusable layout, Boris Shingarov, 12:58
  • Re: Page Spacer gets confused by next-space leading to unusable layout, Boris Shingarov, 12:48
  • Pango font tree not handled at non-default score size, Jiri Zurek (Prague), 10:48
  • Re: Issue 996 in lilypond: Wrong beaming of eighth notes in 2/8 measures, lilypond, 03:56
• January 25, 2010
  • Re: svg output from version 2.13.12 cannot cope with numeric time signature, Bernard Hurley, 23:18
  • Re: Issue 928 in lilypond: `Dynamics' items aren't vertically centered, lilypond, 20:44
  • Re: Issue 405 in lilypond: tupletBracket not printed despite #'bracket-visibility=##t, Neil Puttock, 20:38
  • Re: Issue 189 in lilypond: \episem over a single note, lilypond, 20:37
  • Re: Issue 305 in lilypond: positioning of hairpins and dynamics, lilypond, 20:33
  • Re: Issue 999 in lilypond: Enhancement: Dynamics could switch from one staff to another, lilypond, 20:29
  • Re: Issue 997 in lilypond: RehearsalMarks are not kept inside the page, lilypond, 20:25
  • Re: Issue 997 in lilypond: RehearsalMarks are not kept inside the page, lilypond, 20:13
  • Re: Issue 997 in lilypond: RehearsalMarks are not kept inside the page, lilypond, 20:09
  • Re: Issue 997 in lilypond: RehearsalMarks are not kept inside the page, lilypond, 19:52
  • Re: svg output from version 2.13.12 cannot cope with numeric time signature, Patrick McCarty, 15:15
  • Re: Wrong accidentals when notes are octave apart, Valentin Villenave, 15:11
  • Re: Wrong accidentals when notes are octave apart, Graham Percival, 15:02
  • Re: 2.13.11-1: Y-offset for RehearsalMark?, Trevor Daniels, 14:39
  • Re: Issue 986 in lilypond: collision tuplet number and partcombine text, lilypond, 14:36
  • Re: Issue 880 in lilypond: Regression: Arpeggios collide with notes when connectArpeggios is set, lilypond, 14:32
  • Re: 2.13.11-1: Y-offset for RehearsalMark?, Trevor Daniels, 14:28
  • Re: Issue 821 in lilypond: Regression: arpeggios may collide with barlines in a PianoStaff with multiple voices, lilypond, 14:27
  • Wrong accidentals when notes are octave apart, Ran Rutenberg, 12:50
  • Re: Issue 1000 in lilypond: send texi2html patches upstream, lilypond, 12:00
  • Re: Issue 216 in lilypond: Enhancement: the ability to change staff line spacing inside a \layout{} block, lilypond, 11:57
  • Issue 1000 in lilypond: send texi2html patches upstream, lilypond, 09:43
  • Re: Issue 997 in lilypond: RehearsalMarks are not kept inside the page, lilypond, 09:38
  • Re: Lilly Pond Download, Valentin Villenave, 08:59
  • Re: Dynamics placed incorrectly around staff changes, Valentin Villenave, 08:56
  • Issue 999 in lilypond: Enhancement: Dynamics could switch from one staff to another, lilypond, 08:56
  • Re: Issue 216 in lilypond: Enhancement: the ability to change staff line spacing inside a \layout{} block, lilypond, 08:50
  • Issue 998 in lilypond: Tuplet should not be beamed with non-tuplet notes., lilypond, 08:45
  • Re: Default beaming with tuplets, Valentin Villenave, 08:45
  • Re: Issue 997 in lilypond: RehearsalMarks are not kept inside the page, lilypond, 08:40
  • Re: problem with input/regression/page-label.ly, Valentin Villenave, 08:37
  • Issue 997 in lilypond: RehearsalMarks are not kept inside the page, lilypond, 08:35
  • Re: Different size staves?, Valentin Villenave, 08:20
  • Re: Issue 216 in lilypond: Enhancement: the ability to change staff line spacing inside a \layout{} block, lilypond, 08:18
  • Re: Tempo / tuplet bracket bug, Valentin Villenave, 08:01
  • Issue 996 in lilypond: Wrong beaming of eighth notes in 2/8 measures, lilypond, 08:01
  • Re: svg output from version 2.13.12 cannot cope with numeric time signature, Bernard Hurley, 08:00
  • Re: Issue 887 in lilypond: Non-ASCII characters in textedit URIs should be percent-encoded, lilypond, 07:56
  • Re: Tempo / tuplet bracket bug, Carl Sorensen, 07:04
• January 24, 2010
  • Re: Issue 887 in lilypond: Non-ASCII characters in textedit URIs should be percent-encoded, lilypond, 19:38
  • duplte/triple time versus binary/ternary rhythm, Mark Van den Borre, 18:35
  • Re: svg output from version 2.13.12 cannot cope with numeric time signature, Patrick McCarty, 16:24
  • Re: svg output from version 2.13.12 cannot cope with numeric time signature, Patrick McCarty, 16:15
  • svg output from version 2.13.12 cannot cope with numeric time signature, Bernard Hurley, 15:58
  • Re: Tempo / tuplet bracket bug, Valentin Villenave, 15:22
  • Re: Issue 887 in lilypond: Non-ASCII characters in textedit URIs should be percent-encoded, lilypond, 15:20
  • Issue 995 in lilypond: tuplets cannot begin with a \tempo indication, lilypond, 15:16
  • Re: Issue 993 in lilypond: translation infrastructure for new website, lilypond, 15:10
  • Re: Issue 993 in lilypond: translation infrastructure for new website, lilypond, 15:00
  • Re: Issue 898 in lilypond: Enhancement: rests should be taken into account when determining beaming intervals, lilypond, 14:57
  • Re: Issue 405 in lilypond: tupletBracket not printed despite #'bracket-visibility=##t, Ian Hulin, 14:54
  • Issue 994 in lilypond: Enhancement: the ability to automatically beam across rests., lilypond, 14:52
  • Re: Issue 783 in lilypond: release list for 2.14, lilypond, 14:48
  • Re: Issue 846 in lilypond: copyright years for manuals, lilypond, 14:44
  • Re: Issue 836 in lilypond: [in progress] output-suffix as a (Score) context property, lilypond, 14:40
  • Re: Issue 398 in lilypond: collision clef / stem with changing piano staff, lilypond, 14:36
  • Re: Issue 337 in lilypond: collision: \arpeggioUp should increase horizontal space of \arpeggio, lilypond, 14:31
  • Re: Issue 941 in lilypond: Enhancement: merging make-markup-command and make-builtin-markup-command, lilypond, 14:27
  • Re: Issue 988 in lilypond: input/regresstion/quote-tie.ly : missing note, lilypond, 14:23
  • Re: Issue 961 in lilypond: Þrows error upon using character combination !} in ðe closing p art of a lyrics block., lilypond, 14:19
  • Re: Issue 596 in lilypond: collision tuplet number and slur, lilypond, 14:15
  • Re: Issue 936 in lilypond: \tempo makes TextSpanner too long, lilypond, 14:11
  • Re: Issue 991 in lilypond: automatically include propert-init.ly in docs, lilypond, 14:07
  • Re: Issue 918 in lilypond: Enhancement: \RemoveEmpty*StaffContext for all appropriate contexts, lilypond, 14:03
  • Re: Issue 959 in lilypond: Enhancement Request: Easy shape-note heads with a scale degree, lilypond, 13:59
  • Re: Issue 927 in lilypond: UTF-8 bidi/rtl/ltr characters are not correctly implemented, lilypond, 13:55
  • Re: Issue 945 in lilypond: warning about \version for short snippets, lilypond, 13:51
  • Re: Issue 932 in lilypond: Vertical spacing: repeat brackets and tablatures exceeding page bottom, lilypond, 13:47
  • Re: Issue 898 in lilypond: Enhancement: rests should be taken into account when determining beaming intervals, Valentin Villenave, 13:44
  • Re: Issue 916 in lilypond: Broken regtest: spacing-loose-grace-linebreak.ly, lilypond, 13:43
  • Re: Issue 909 in lilypond: Redundant \consists produce a segfault, lilypond, 13:39
  • Re: Issue 950 in lilypond: /input/regression/spacing-knee-compressed.ly broken, lilypond, 13:35
  • Re: Issue 987 in lilypond: input/regression/quote-cyclic.ly : some notes too small, lilypond, 13:31
  • Re: Issue 951 in lilypond: input/regression/system-overstrike.ly broken, lilypond, 13:27
  • Re: Issue 901 in lilypond: gub: lilypad.exe has a 40% chance of being included, lilypond, 13:23
  • Re: Issue 898 in lilypond: Enhancement: rests should be taken into account when determining beaming intervals, David Kastrup, 13:21
  • Re: Issue 928 in lilypond: `Dynamics' items aren't vertically centered, lilypond, 13:19
  • Re: Issue 898 in lilypond: Enhancement: rests should be taken into account when determining beaming intervals, lilypond, 13:15
  • Re: Issue 883 in lilypond: stems may collide with noteheads in tightly-spaced music, lilypond, 13:11
  • Re: Issue 830 in lilypond: Task: rename feta filenames in English, lilypond, 13:07
  • Re: Issue 787 in lilypond: script stack order fails with 2 more notes, lilypond, 13:02
  • Re: Issue 784 in lilypond: augmentation dots not shifted away from some chords, lilypond, 12:59
  • Re: Issue 755 in lilypond: SVG backend improvements, lilypond, 12:55
  • Re: Issue 638 in lilypond: auto-beam-settings do not take into account *all* durations covered by the beam, lilypond, 12:51
  • Re: Issue 911 in lilypond: convert-ly rules for vertical spacing variables, lilypond, 12:47
  • Re: Issue 628 in lilypond: Regression: markup \note doesn't work as a TimeSignature stencil, lilypond, 12:42
  • Re: Issue 993 in lilypond: translation infrastructure for new website, lilypond, 11:05
  • Re: Issue 993 in lilypond: translation infrastructure for new website, lilypond, 10:54
  • Re: Issue 783 in lilypond: release list for 2.14, lilypond, 10:41
  • Re: Issue 993 in lilypond: translation infrastructure for new website, lilypond, 10:37
  • Issue 993 in lilypond: translation infrastructure for new website, lilypond, 10:28
  • Re: Cannot connect tie in a voice of polyphony, Trevor Daniels, 06:03
  • Re: Cannot connect tie in a voice of polyphony, Patrick McCarty, 05:44
  • Re: Cannot connect tie in a voice of polyphony, Trevor Daniels, 05:04
  • Re: Cannot connect tie in a voice of polyphony, Trevor Daniels, 04:02
• January 23, 2010
  • Re: Issue 957 in lilypond: remove duplicate anchor generation in texi2html, lilypond, 20:47
  • Re: Issue 990 in lilypond: automatically include property-init.ly in docs, lilypond, 20:19
  • Re: Issue 980 in lilypond: separate git repositories for lilypad and/or gub, lilypond, 20:14
  • Lilly Pond Download, Aykut Sahin, 12:35
  • Re: Issue 939 in lilypond: shared location for included docs, lilypond, 09:19
  • Re: Issue 957 in lilypond: remove duplicate anchor generation in texi2html, lilypond, 08:30
  • Re: Issue 852 in lilypond: stop google from indexing old docs, lilypond, 08:26
• January 22, 2010
  • Re: Vertical space page layout, Graham Percival, 20:23
  • Vertical space page layout, Didi Kanjahn, 20:10
  • Re: Issue 957 in lilypond: remove duplicate anchor generation in texi2html, lilypond, 14:51
  • Re: Issue 842 in lilypond: bibliography not built, lilypond, 13:51
• January 21, 2010
  • Issue 992 in lilypond: input/regression/tuplet-rest.ly collision tuplet and note head, lilypond, 15:17
  • Re: [regtests] tuplet-bracket-cross-staff.ly: bracket collides with notehead (and ledger), Graham Percival, 15:17
  • Re: [regtests] utf-8-mixed-text.ly: The re should be ""Здравствуйте" !-), Graham Percival, 15:12
  • Re: Issue 967 in lilypond: Add a --svg option to the LilyPond binary, lilypond, 10:37
  • [regtests] utf-8-mixed-text.ly: There should be ""З дравствуйте" !-), Dmytro O. Redchuk, 05:21
  • Re: [regtests] tuplet-bracket-cross-staff.ly: bracket collides with notehead (and ledger), Dmytro O. Redchuk, 05:19
  • [regtests] tuplet-bracket-cross-staff.ly: bracket collides with notehead (and ledger), Dmytro O. Redchuk, 05:14
  • Re: [regtests] quote-during.ly: collision between "orig" and "quoted", Dmytro O. Redchuk, 04:17
• January 20, 2010
  • Re: Issue 880 in lilypond: Regression: Arpeggios collide with notes when connectArpeggios is set, lilypond, 19:19
  • Re: Issue 821 in lilypond: Regression: arpeggios may collide with barlines in a PianoStaff with multiple voices, lilypond, 19:15
  • Re: Issue 981 in lilypond: input/regression/fermata-rest-position.ly, lilypond, 17:13
  • Re: Issue 986 in lilypond: collision tuplet number and partcombine text, lilypond, 16:47
  • Re: Issue 988 in lilypond: input/regresstion/quote-tie.ly : missing note, lilypond, 16:40
  • Re: Issue 985 in lilypond: Noteheads don't merge when one of the voices contains a second, lilypond, 16:26
  • Re: Issue 988 in lilypond: input/regresstion/quote-tie.ly : missing note, lilypond, 16:22
  • Re: Issue 987 in lilypond: input/regression/quote-cyclic.ly : some notes too small, lilypond, 16:16
  • Re: Issue 987 in lilypond: input/regression/quote-cyclic.ly : some notes too small, lilypond, 16:13
  • Re: Issue 988 in lilypond: input/regresstion/quote-tie.ly : missing note, lilypond, 16:01
  • Re: Issue 987 in lilypond: input/regression/quote-cyclic.ly : some notes too small, lilypond, 15:34
  • Re: misaligned incipits for clefs exceeding staff-lines, Neil Puttock, 15:09
  • Re: Issue 990 in lilypond: automatically include propert-init.ly in docs, lilypond, 14:42
  • Re: Issue 991 in lilypond: automatically include propert-init.ly in docs, lilypond, 14:38
  • Issue 991 in lilypond: automatically include propert-init.ly in docs, lilypond, 14:34
  • Issue 990 in lilypond: automatically include propert-init.ly in docs, lilypond, 14:30
  • Issue 989 in lilypond: ensure that no information is only in the regtests, lilypond, 14:01
  • Re: Issue 986 in lilypond: collision tuplet number and partcombine text, lilypond, 13:53
  • Re: Issue 987 in lilypond: input/regression/quote-cyclic.ly : some notes too small, lilypond, 13:49
  • Issue 988 in lilypond: input/regresstion/quote-tie.ly : missing note, lilypond, 13:45
  • Re: [regtests] quote-tie.ly: illegal example?.. BUG?.., Graham Percival, 13:45
  • Re: [regtests] quote-during.ly: collision between "orig" and "quoted", Graham Percival, 13:38
  • Re: [regtests] quote-cyclic.ly: main voice has small notes, Graham Percival, 13:36
  • Issue 987 in lilypond: input/regression/quote-cyclic.ly : some notes too small, lilypond, 13:35
  • [regtests] quote-tie.ly: illegal example?.. BUG?.., Dmytro O. Redchuk, 11:31
  • [regtests] quote-during.ly: collision between "orig" and "quoted", Dmytro O. Redchuk, 10:57
  • [regtests] quote-cyclic.ly: main voice has small notes, Dmytro O. Redchuk, 10:42
  • Tie positioning in chords with large intervals [engraving-nitpick?], Alexander Kobel, 09:11
  • Issue 986 in lilypond: collision tuplet number and partcombine text, lilypond, 08:30
  • Re: Issue 596 in lilypond: collision tuplet number and slur, lilypond, 08:26
  • Re: [regtests] part-combine-text.ly: "solo 2" or "Solo II" ?.., Graham Percival, 08:23
  • Re: Issue 307 in lilypond: collision slur with tuplet bracket, lilypond, 08:21
  • Re: [regtests] part-combine-tuplet-end.ly: collision between tuplet digit and partcombine text, Graham Percival, 08:21
  • Re: Issue 596 in lilypond: collision tuplet number and slur, lilypond, 08:18
  • verifying issues since 2.13.9 ?, Graham Percival, 07:58
  • misaligned incipits for clefs exceeding staff-lines, Martin Straeten, 07:20
  • Re: [regtests] part-combine-tuplet-end.ly: collision between tuplet digit and partcombine text, Trevor Daniels, 06:01
  • [regtests] part-combine-tuplet-end.ly: collision between tuplet digit and partcombine text, Dmytro O. Redchuk, 05:13
  • [regtests] part-combine-text.ly: "solo 2" or "Solo II" ?.., Dmytro O. Redchuk, 05:06
  • Re: Issue 969 in lilypond: find a tool to convert SVG->EPS, lilypond, 03:41
• January 19, 2010
  • Re: Issue 969 in lilypond: find a tool to convert SVG->EPS, lilypond, 23:03
  • Re: Issue 969 in lilypond: find a tool to convert SVG->EPS, lilypond, 22:32
  • Re: Issue 969 in lilypond: find a tool to convert SVG->EPS, lilypond, 22:24
  • Re: Issue 985 in lilypond: Noteheads don't merge when one of the voices contains a second, lilypond, 22:06
  • Re: Issue 975 in lilypond: Font caching problem with networked home folders, lilypond, 21:58
  • \repeatTie problem with lyrics, Peter Dingley, 16:06
  • Issue 985 in lilypond: Noteheads don't merge when one of the voices contains a second, lilypond, 13:48
  • Issue 984 in lilypond: Noteheads don't merge when one of the voices contains a second, lilypond, 13:44
  • Re: Issue 590 in lilypond: Ties can collide with augmentation dots, lilypond, 12:39
  • Re: Issue 570 in lilypond: Articulations can collide with ties, lilypond, 12:35
  • Issue 983 in lilypond: relative location of css/ and pictures/ dir, lilypond, 12:26
  • Issue 982 in lilypond: web big-html and pdf look bad, lilypond, 12:21
  • Re: Issue 980 in lilypond: separate git repositories for lilypad and/or gub, lilypond, 11:12
  • Re: [regtests] paper-margins-line-width.ly: TYPO? "horizontally", not "vertically"?.., Graham Percival, 10:59
  • [regtests] paper-margins-line-width.ly: TYPO? "horizontally", not "vertically"?.., Dmytro O. Redchuk, 10:36
  • Re: [regtests] hairpin-circled.ly: "failed to check" if there is one circle, Graham Percival, 09:57
  • Re: Issue 981 in lilypond: input/regression/fermata-rest-position.ly, lilypond, 09:48
  • Re: [regtests] fermata-rest-position.ly: \fermataMarkup positioned higher then \fermata, Graham Percival, 09:47
  • Issue 981 in lilypond: input/regression/fermata-rest-position.ly, lilypond, 09:44
  • [regtests] hairpin-circled.ly: "failed to check" if there is one circle, Dmytro O. Redchuk, 07:08
  • Re: [regtests] fermata-rest-position.ly: \fermataMarkup positioned higher then \fermata, Trevor Daniels, 06:57
  • [regtests] fermata-rest-position.ly: \fermataMarkup positioned higher then \fermata, Dmytro O. Redchuk, 05:55
• January 18, 2010
  • Re: Issue 980 in lilypond: separate git repositories for lilypad and/or gub, lilypond, 18:29
  • Re: Issue 980 in lilypond: separate git repositories for lilypad and/or gub, lilypond, 18:19
  • Re: Issue 980 in lilypond: separate git repositories for lilypad and/or gub, lilypond, 17:45
  • Re: Issue 980 in lilypond: separate git repositories for lilypad and/or gub, lilypond, 14:24
  • Re: Issue 472 in lilypond: collision rest + (accidental/notehead) with beaming, lilypond, 10:05
  • Re: Issue 409 in lilypond: collision tie and time signature, lilypond, 10:01
  • Re: Issue 398 in lilypond: collision clef / stem with changing piano staff, lilypond, 09:57
  • Re: Issue 337 in lilypond: collision: \arpeggioUp should increase horizontal space of \arpeggio, lilypond, 09:54
  • Re: Issue 257 in lilypond: collision accent and tuplet bracket, lilypond, 09:49
  • Re: Issue 45 in lilypond: collision noteheads with four voices, lilypond, 09:45
  • Re: Issue 40 in lilypond: collision glissando accidental (includes workaround), lilypond, 09:41
  • Re: Issue 39 in lilypond: collision flag notehead with polyphony, lilypond, 09:37
  • Re: Issue 36 in lilypond: collision cresc and kneed beams, lilypond, 09:33
  • Re: Issue 36 in lilypond: collision cresc and kneed beams, lilypond, 09:29
  • Re: Issue 502 in lilypond: hairpins bound to spacer notes are aligned on lyrics, lilypond, 09:25
  • Re: Issue 405 in lilypond: tupletBracket not printed despite #'bracket-visibility=##t, lilypond, 09:21
  • Re: Issue 314 in lilypond: incorrect ancient \inclinatum spacing, lilypond, 09:17
  • Re: Issue 428 in lilypond: collision avoidance fails sometimes with simultaneous voices, lilypond, 09:13
  • Re: Issue 397 in lilypond: collision pitchedTrill and tie, lilypond, 09:09
  • Re: Issue 220 in lilypond: fingering too close to previous note, lilypond, 09:05
  • Issue 980 in lilypond: separate git repositories for lilypad and/or gub, lilypond, 09:01
  • Re: Issue 977 in lilypond: GUB build numbers, lilypond, 08:56
  • Re: Issue 954 in lilypond: GUB add temporary patch to lilypond, lilypond, 08:52
• January 17, 2010
  • Re: New articulation character for half-open hi-hats?, Werner LEMBERG, 01:29
• January 16, 2010
  • Re: Issue 189 in lilypond: \episem over a single note, lilypond, 13:32
  • Re: New articulation character for half-open hi-hats?, Reinhold Kainhofer, 13:02
  • Re: New articulation character for half-open hi-hats?, Neil Puttock, 12:15
  • Re: New articulation character for half-open hi-hats?, Mark Polesky, 12:03
  • Re: New articulation character for half-open hi-hats?, Graham Percival, 11:44
  • Re: New articulation character for half-open hi-hats?, Neil Puttock, 11:43
  • Re: New articulation character for half-open hi-hats?, Mark Polesky, 11:40
  • Re: Issue 699 in lilypond: unwanted character changes on Windows Vista, lilypond, 11:23
  • Re: Issue 940 in lilypond: unify announcement methods, lilypond, 07:38
• January 15, 2010
  • Re: New articulation character for half-open hi-hats?, Neil Puttock, 16:47
  • Re: Issue 919 in lilypond: resolve compiler warnings, lilypond, 16:29
  • Re: Issue 804 in lilypond: Code cleaning: checking types-conversion issues and other build warnings, lilypond, 16:25
  • Re: Issue 959 in lilypond: Enhancement Request: Easy shape-note heads with a scale degree, lilypond, 16:08
  • Re: Issue 804 in lilypond: Code cleaning: checking types-conversion issues, lilypond, 16:04
  • Re: Issue 919 in lilypond: resolve compiler warnings, lilypond, 16:00
  • Issue 979 in lilypond: waf build system, lilypond, 11:38
• January 14, 2010
  • Re: Issue 749 in lilypond: SpacingSpanner doesn't work when using gregorian.ly, lilypond, 15:47
  • Re: Issue 854 in lilypond: lilycontrib.tcl, lilypond, 12:12
  • Issue 978 in lilypond: docs for lily-git.tcl, lilypond, 12:08
  • Re: Issue 897 in lilypond: key signatures should be inherited by all Voices (no matter their accidental style), lilypond, 12:03
  • Re: Issue 864 in lilypond: Source files that don't produce a PDF should output a warning message, lilypond, 12:00
  • Re: Issue 878 in lilypond: Bowing indications need higher priority than fingerings, lilypond, 11:56
  • Re: Issue 879 in lilypond: RemoveEmptyStaffContext doesn't need to disable auto-knee-gap, lilypond, 11:53
  • Re: Issue 849 in lilypond: Rests should not keep staves alive, lilypond, 11:48
  • Re: Issue 779 in lilypond: fonts should be rebuilt upon modifications to mf/, lilypond, 11:44
  • Re: Issue 749 in lilypond: SpacingSpanner doesn't work when using gregorian.ly, lilypond, 11:40
  • Re: Issue 732 in lilypond: Alignment problems when vertically stacking horizontally centered stencils., lilypond, 11:37
  • 7 issues changed in lilypond, lilypond, 11:33
  • Issue 977 in lilypond: GUB build numbers, lilypond, 11:17
  • Re: Issue 887 in lilypond: PDF point-and-click URI links with special chars wrongly encoded depending on the OS, lilypond, 07:08
• January 13, 2010
  • Re: Page Spacer gets confused by next-space leading to unusable layout, Joe Neeman, 22:49
  • Re: Issue 887 in lilypond: PDF point-and-click URI links with special chars wrongly encoded depending on the OS, lilypond, 13:28
  • Re: Issue 887 in lilypond: PDF point-and-click URI links with special chars wrongly encoded depending on the OS, lilypond, 12:29
  • Re: Issue 610 in lilypond: tupletFullLength too short in a polyphonic situation, lilypond, 08:34
  • Re: Issue 333 in lilypond: lyrics delayed by one note with \partial and \override VerticalAxisGroup, lilypond, 08:30
  • Re: Issue 868 in lilypond: \parenthesize does not take dotted notes into account, lilypond, 08:26
  • Re: Issue 728 in lilypond: Fingerings collide with accidentals., lilypond, 08:22
  • Re: Issue 646 in lilypond: Collision note/clef due to translated markup, lilypond, 08:17
  • Re: Issue 586 in lilypond: Cross-staff slur causes a weird output, lilypond, 08:13
  • Re: Issue 538 in lilypond: almost-collision notehead and tuplet bracket+number, lilypond, 08:10
  • Re: Issue 400 in lilypond: collision clef and beam, lilypond, 08:06
  • Re: Issue 376 in lilypond: tremolo beams can collide with notes, lilypond, 08:02
  • Re: Issue 307 in lilypond: collision slur with tuplet bracket, lilypond, 07:58
  • Re: Issue 974 in lilypond: music overflows page, lilypond, 07:54
  • Re: Issue 887 in lilypond: PDF point-and-click URI links with special chars wrongly encoded depending on the OS, lilypond, 05:25
  • Re: Issue 887 in lilypond: PDF point-and-click URI links with special chars wrongly encoded depending on the OS, lilypond, 05:19
  • Issue 976 in lilypond: Difficulties with tablature angle brackets, lilypond, 03:28
  • Re: Bug: font caching on OS X w/ networked home folders, Patrick McCarty, 03:11
  • Issue 975 in lilypond: Font caching problem with networked home folders, lilypond, 03:08
  • Re: Issue 974 in lilypond: Copyright may be obscured by an overly-full page when all header fields are used, lilypond, 01:45
  • Re: Issue 974 in lilypond: Copyright may be obscured by an overly-full page when all header fields are used, lilypond, 00:32
• January 12, 2010
  • Re: Issue 887 in lilypond: PDF point-and-click URI links with special chars wrongly encoded depending on the OS, lilypond, 19:52
  • Re: Issue 974 in lilypond: Copyright may be obscured by an overly-full page when all header fields are used, lilypond, 19:28
  • Re: Page Spacer gets confused by next-space leading to unusable layout, Joe Neeman, 18:08
  • Re: Bug: font caching on OS X w/ networked home folders, Patrick McCarty, 16:56
  • Re: Issue 974 in lilypond: Copyright may be obscured by an overly-full page when all header fields are used, lilypond, 15:00
  • Issue 974 in lilypond: Copyright may be obscured by an overly-full page when all header fields are used, lilypond, 14:55
  • Re: Issue 969 in lilypond: find a tool to convert SVG->EPS, lilypond, 14:51
  • Re: Issue 969 in lilypond: find a tool to convert SVG->EPS, lilypond, 13:57
  • Re: Issue 968 in lilypond: SVG backend: implement an output-preview-framework, lilypond, 13:53
  • Re: Issue 969 in lilypond: find a tool to convert SVG->EPS, lilypond, 13:50
  • Re: Bug: font caching on OS X w/ networked home folders, Carl Sorensen, 13:41
  • Re: Issue 969 in lilypond: find a tool to convert SVG->EPS, lilypond, 13:22
  • Re: Issue 968 in lilypond: SVG backend: implement an output-preview-framework, lilypond, 13:18
  • Re: Issue 941 in lilypond: Enhancement: merging make-markup-command and make-builtin-markup-command, lilypond, 13:14
  • Re: Bug: font caching on OS X w/ networked home folders, Jacob Rundall, 12:38
  • Page Spacer gets confused by next-space leading to unusable layout, Boris Shingarov, 12:30
• January 11, 2010
  • Re: header may be covered unintentionally by music, James Bailey, 17:27
  • Re: header may be covered unintentionally by music, -Eluze, 17:15
  • header may be covered unintentionally by music, James Bailey, 13:23
  • Re: Issue 633 in lilypond: Regression: no more stems in TabStaff, lilypond, 12:08
  • Re: Issue 633 in lilypond: Regression: no more stems in TabStaff, lilypond, 12:04
  • Re: Issue 633 in lilypond: Regression: no more stems in TabStaff, Trevor Daniels, 06:24
  • Re: Issue 633 in lilypond: Regression: no more stems in TabStaff, lilypond, 05:57
• January 10, 2010
  • Re: Issue 682 in lilypond: annotate-spacing should produce horizontal info as well, lilypond, 17:43
  • Re: New articulation character for half-open hi-hats?, Carsten Steger, 09:38
  • Re: New articulation character for half-open hi-hats?, Carsten Steger, 09:38
  • Re: Issue 869 in lilypond: input/regression/ renaming to regression/, lilypond, 08:59
• January 09, 2010
  • Re: Issue 911 in lilypond: convert-ly rules for vertical spacing variables, lilypond, 22:03
  • Issue 973 in lilypond: SVG backend: add support for complete on-the-fly glyph conversion, lilypond, 21:42
  • Issue 972 in lilypond: SVG backend: related grobs should be grouped together with <g> tags, lilypond, 21:24
  • Re: Issue 964 in lilypond: check website accessibility, lilypond, 21:10
  • Issue 971 in lilypond: SVG backend: problem with memory usage and multi-page SVG output, lilypond, 21:00
  • Re: Issue 968 in lilypond: SVG backend: implement an output-preview-framework, lilypond, 20:32
  • Re: Issue 970 in lilypond: SVG backend: add program option to support <pageSet> and <page>, lilypond, 20:28
  • Issue 970 in lilypond: SVG backend: add program option to support <pageSet> and <page>, lilypond, 20:24
  • Issue 969 in lilypond: find a tool to convert SVG->EPS, lilypond, 20:10
  • Issue 968 in lilypond: SVG backend: implement an output-preview-framework, lilypond, 19:40
  • Issue 967 in lilypond: Add a --svg option to the LilyPond binary, lilypond, 19:34
  • Issue 966 in lilypond: SVG backend: all floating-point values should be rounded to 4 decimal places, lilypond, 19:28
  • Re: Issue 963 in lilypond: check dependency versions, lilypond, 18:51
  • Issue 965 in lilypond: making a score-following DVD with lilypond, lilypond, 16:21
  • Issue 964 in lilypond: check website accessibility, lilypond, 16:10
  • Issue 963 in lilypond: check dependency versions, lilypond, 16:07
  • Re: New articulation character for half-open hi-hats?, Werner LEMBERG, 13:56
  • Negative frets in fret diagrams, Carl Sorensen, 12:41
  • Negative frets in fret diagrams, Carl Sorensen, 12:40
  • Re: notation reference lyrics example issue?, Graham Percival, 11:40
  • Re: notation reference lyrics example issue?, Graham Percival, 10:32
  • notation reference lyrics example issue?, Philip Potter, 10:30
• January 08, 2010
  • Re: New articulation character for half-open hi-hats?, Werner LEMBERG, 12:40
  • Re: Issue 857 in lilypond: translations status html->texinfo, lilypond, 07:59
  • Re: Issue 857 in lilypond: translations status html->texinfo, lilypond, 07:54
  • Re: Issue 857 in lilypond: translations status html->texinfo, lilypond, 07:46
  • Re: Issue 857 in lilypond: translations status html->texinfo, lilypond, 07:42
• January 07, 2010
  • Re: Textual tempo markers in adjacent bars are stacked, Kieren MacMillan, 17:23
  • Re: Textual tempo markers in adjacent bars are stacked, Reinhold Kainhofer, 12:58
  • Re: Textual tempo markers in adjacent bars are stacked, Xavier Scheuer, 12:06
  • Re: Textual tempo markers in adjacent bars are stacked, Reinhold Kainhofer, 09:08
• January 06, 2010
  • Re: Issue 784 in lilypond: augmentation dots not shifted away from some chords, lilypond, 22:58
  • Re: Issue 883 in lilypond: stems may collide with noteheads in tightly-spaced music, lilypond, 22:54
  • Re: Issue 951 in lilypond: input/regression/system-overstrike.ly broken, lilypond, 22:50
  • Re: Wierd behaviour of \header in \bookpart in \version 2.12.2, Reinhold Kainhofer, 18:36
  • Re: Issue 904 in lilypond: Regression: partially-tied chords may look wrong when the tie flips, lilypond, 17:38
  • Re: Issue 962 in lilypond: Incorrect tie placement with partially-tied chords, lilypond, 16:04
  • Re: Issue 961 in lilypond: Þrows error upon using character combination !} in ðe closing p art of a lyrics block., lilypond, 15:41
  • Re: Issue 962 in lilypond: Incorrect tie placement with partially-tied chords, lilypond, 15:37
  • Re: Issue 962 in lilypond: Incorrect tie placement with partially-tied chords, lilypond, 15:29
  • Re: Incorrect tie placement with partially-tied chords, Patrick McCarty, 15:18
  • Issue 962 in lilypond: Incorrect tie placement with partially-tied chords, lilypond, 15:17
  • Re: Wierd behaviour of \header in \bookpart in \version 2.12.2, Nicolas Sceaux, 13:18
  • Incorrect tie placement with partially-tied chords, Chris Snyder, 10:15
  • Re: Issue 961 in lilypond: Þrows error upon using character combination !} in ðe closing part of a lyrics block., Ian Hulin, 08:19
  • #'header:title etc not defined outside \header and \paper blocks in \version 2.12.2, Bernard Hurley, 06:32
  • Issue 961 in lilypond: Þrows error upon using character combination !} in ðe closing part of a lyrics block., lilypond, 05:55
  • Wierd behaviour of \header in \bookpart in \version 2.12.2, Bernard Hurley, 05:08
• January 05, 2010
  • Re: convert-ly can't cope with accented filename, -Eluze, 16:46
  • Issue 960 in lilypond: Enhancement: FretNumbers alignment improvements (wrt dotted durations), lilypond, 08:17
  • Re: Strange page breaking issue in 2.13.10, Reinhold Kainhofer, 06:42
  • Re: convert-ly can't cope with accented filename, Bertalan Fodor (LilyPondTool), 05:26
  • Re: convert-ly can't cope with accented filename, John Mandereau, 02:37
• January 04, 2010
  • Re: Issue 885 in lilypond: Uninstallation issues, lilypond, 23:24
  • Fwd: Strange page breaking issue in 2.13.10, Reinhold Kainhofer, 23:06
  • Re: Issue 911 in lilypond: convert-ly rules for vertical spacing variables, lilypond, 12:50
  • Re: Issue 37 in lilypond: collision notehead and beams, lilypond, 12:46
  • 12 issues changed in lilypond, lilypond, 12:36
  • 11 issues changed in lilypond, lilypond, 12:32
  • Re: Issue 838 in lilypond: Inconsistency in tests output size, lilypond, 12:29
  • Re: Issue 922 in lilypond: file sizes jumped from 2.13.1 to 2.13.2, lilypond, 12:24
  • 13 issues changed in lilypond, lilypond, 12:20
  • Re: Issue 783 in lilypond: release list for 2.14, lilypond, 12:16
  • Re: Issue 959 in lilypond: Enhancement Request: Easy shape-note heads with a scale degree, lilypond, 12:14
  • Re: Issue 933 in lilypond: automatic, daily out-of-build tests, lilypond, 12:12
  • Re: Issue 908 in lilypond: ImageMagick `compare' commands need some investigating, lilypond, 12:08
  • Re: Issue 955 in lilypond: editing notes / tweaks in a separate file, lilypond, 06:14
  • Re: Issue 793 in lilypond: Win LilyPad editor "About" message needs to be fixed, lilypond, 06:07
  • Re: Issue 792 in lilypond: empty png files in the documentation, lilypond, 04:09
  • Re: Issue 792 in lilypond: empty png files in the documentation, lilypond, 03:31
  • Re: Issue 946 in lilypond: build tarballs of docs, lilypond, 03:21
  • Re: Issue 946 in lilypond: build tarballs of docs, lilypond, 03:14
  • Re: Issue 792 in lilypond: empty png files in the documentation, lilypond, 03:10
• January 03, 2010
  • Re: Issue 946 in lilypond: build tarballs of docs, lilypond, 20:46
  • Re: Issue 792 in lilypond: empty png files in the documentation, lilypond, 18:20
  • Issue 959 in lilypond: Enhancement Request: Easy shape-note heads with a scale degree, lilypond, 12:42
  • Re: Numeric note heads for singers, Carl Sorensen, 12:01
  • Re: Issue 814 in lilypond: warning-as-error should be enabled when compiling the regtests, lilypond, 08:25
  • Re: Issue 839 in lilypond: Enhancement: improving midi2ly conversion, lilypond, 08:21
  • Re: Issue 775 in lilypond: configure/autogen should detect doc requirements, lilypond, 08:17
  • Re: Issue 777 in lilypond: python script for indenting lilypond files, lilypond, 08:13
  • Re: Issue 788 in lilypond: simpler convert-ly rules, lilypond, 08:09
  • Re: Issue 834 in lilypond: midi2ly broken on Windows systems, lilypond, 08:05
  • Re: Issue 875 in lilypond: Generated lilypond-words files are not complete, lilypond, 08:01
  • Re: Issue 806 in lilypond: Musicxml2ly problem with tempo indications when a piece starts with MM rests., lilypond, 07:57
  • Re: Issue 805 in lilypond: Irrelevant configure message with autoconf and gettext test, lilypond, 07:52
  • Re: Issue 534 in lilypond: two problems with win32 notepad clone, lilypond, 07:48
  • Re: Issue 389 in lilypond: \t -> tab in LSR snippets, lilypond, 07:44
  • Re: Issue 894 in lilypond: lilypond-book fails from the command-line in OSX 10.4, lilypond, 05:43
  • Re: Issue 803 in lilypond: correction needed for the German translation of convert-ly, lilypond, 01:44
  • Re: Issue 856 in lilypond: links in Snippets appear to not work for snippets in multiple categories, lilypond, 01:40
  • Issue 958 in lilypond: clean up FIXMEs and TODOs in web/*.itexi, lilypond, 01:36
  • Issue 957 in lilypond: remove duplicate anchor generation in texi2html, lilypond, 01:32
  • Re: Issue 857 in lilypond: translations status html->texinfo, lilypond, 01:28
  • Re: Issue 708 in lilypond: convert-ly fails to convert keySignature, lilypond, 01:24
  • Re: Issue 825 in lilypond: enable keyboard-driven navigation in the docs, lilypond, 01:20
  • Re: Issue 946 in lilypond: build tarballs of docs, lilypond, 01:16
  • Re: Issue 746 in lilypond: Automatic code indentation improvement (and replacing tabs with spaces), lilypond, 01:12
  • Re: Issue 776 in lilypond: python script to get rid of extra whitespace and generate @menu in the docs, lilypond, 01:08
  • Re: Issue 793 in lilypond: Win LilyPad editor "About" message needs to be fixed, lilypond, 01:04
  • Issue 956 in lilypond: Win LilyPad editor "About" message could be improved, lilypond, 01:00
  • Re: Issue 837 in lilypond: Slow uninstallation on Windows, lilypond, 00:56
  • Re: Issue 847 in lilypond: python scripts should add an autogenerated marker, lilypond, 00:52
  • Re: Issue 848 in lilypond: news-front for general.itexi should be auto-geneated, lilypond, 00:48
  • Re: Issue 858 in lilypond: automatically update version numbers in general.texi, lilypond, 00:44
  • Re: Issue 934 in lilypond: GUB doesn't include Japanese fonts, lilypond, 00:40
  • Re: Issue 815 in lilypond: Enhancement: AJAX-powered search auto-completion for the online documentation, lilypond, 00:36
  • Re: Issue 852 in lilypond: stop google from indexing old docs, lilypond, 00:32
  • Re: Issue 844 in lilypond: clean up website maintenance, lilypond, 00:28
  • Re: Issue 954 in lilypond: GUB add temporary patch to lilypond, lilypond, 00:24
  • Re: Issue 792 in lilypond: empty png files in the documentation, lilypond, 00:20
  • Re: Issue 388 in lilypond: lilypond-book \betweenlilypondsystem does not apply to first system break if no header, lilypond, 00:16
  • Re: Issue 894 in lilypond: lilypond-book fails from the command-line in OSX 10.4, lilypond, 00:12
  • Re: Issue 894 in lilypond: lilypond-book fails from the command-line in OSX 10.4, lilypond, 00:08
  • Re: Issue 885 in lilypond: Uninstallation issues, lilypond, 00:04
• January 02, 2010
  • Re: Issue 644 in lilypond: Large files compilation fails on 32-bit GNU/Linux, lilypond, 23:59
  • Re: Issue 514 in lilypond: abc2ly grace notes, lilypond, 23:55
  • Re: Issue 844 in lilypond: clean up website maintenance, lilypond, 23:51
  • Re: Issue 947 in lilypond: Build failure on OS X on std-vector.hh, lilypond, 23:47
  • Issue 955 in lilypond: editing notes / tweaks in a separate file, lilypond, 20:36
  • Re: Issue 837 in lilypond: Slow uninstallation on Windows, lilypond, 20:15
  • Re: [tablatures] tie bug in 2.13.10?, Trevor Daniels, 18:25
  • Re: midi2ly calls mach-o binary on Mac OS X 10.6, Hans Aberg, 17:42
  • midi2ly calls mach-o binary on Mac OS X 10.6, Tom Dickson, 13:30
  • Re: [tablatures] tie bug in 2.13.10?, Trevor Daniels, 13:12
  • Re: Issue 837 in lilypond: Unnecessary empty dirs in Win32 builds, Trevor Daniels, 12:46
  • Re: New articulation character for half-open hi-hats?, Werner LEMBERG, 12:06
  • Re: [tablatures] tie bug in 2.13.10?, Carl Sorensen, 11:31
  • Re: Issue 837 in lilypond: Unnecessary empty dirs in Win32 builds, lilypond, 07:59
  • Re: Issue 898 in lilypond: Enhancement: rests should be taken into account when determining beaming intervals, David Kastrup, 07:11
  • Re: Issue 837 in lilypond: Unnecessary empty dirs in Win32 builds, lilypond, 07:04
  • Re: Issue 898 in lilypond: Enhancement: rests should be taken into account when determining beaming intervals, lilypond, 06:55
  • Re: New articulation character for half-open hi-hats?, Valentin Villenave, 06:38
  • Re: Issue 653 in lilypond: \override inconsistency with ties in a polyphonic situation, lilypond, 06:31
  • Re: Issue 904 in lilypond: Regression: partially-tied chords may look wrong when the tie flips, lilypond, 06:18
  • Re: Issue 945 in lilypond: warning about \version for short snippets, lilypond, 06:14
  • Re: Issue 885 in lilypond: Uninstallation issues, lilypond, 05:57
  • Re: Issue 901 in lilypond: gub: lilypad.exe has a 40% chance of being included, lilypond, 05:53
  • Re: Issue 901 in lilypond: gub: lilypad.exe has a 40% chance of being included, lilypond, 04:51
  • Re: Issue 755 in lilypond: SVG backend improvements, lilypond, 04:34
  • Re: Issue 885 in lilypond: Uninstallation issues, lilypond, 04:24
• January 01, 2010
  • Re: Issue 954 in lilypond: GUB add temporary patch to lilypond, lilypond, 18:16

---

[Prev Period]

[Next Period]

---

Mail converted by MHonArc