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: Fri Sep 30 2011 23:56:54 -0400 Messages in reverse chronological order

[Next Period]

---

• September 30, 2011
  • Re: Issue 1326 in lilypond: Slur collides with note stem, lilypond, 23:56
  • Re: Add 6x9 Paper Size, Jay Anderson, 15:18
  • Re: Issue 1949 in lilypond: add to paper.scm 6 x 9 in, lilypond, 15:15
  • Re: Add 6x9 Paper Size, address@hidden, 13:47
  • Issue 1949 in lilypond: add to paper.scm 6 x 9 in, lilypond, 13:47
  • Re: Add 6x9 Paper Size, Peekay Ex, 13:43
  • Add 6x9 Paper Size, Jay Anderson, 13:39
  • Re: Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 13:14
  • Windows install clobbered system PATH, Luke Bakken, 13:10
  • Re: Issue 1743 in lilypond: lilypond-2.15.4-1.mingw.exe does not install PATH on Windows 7 SP1, lilypond, 13:09
  • Issue 1948 in lilypond: Windows install clobbered system PATH, lilypond, 13:04
  • Re: Issue 1321 in lilypond: Enhancement: add partcombineUp and partcombineDown functions, lilypond, 12:35
  • Re: Issue 1844 in lilypond: Changes variable names in include/beam-scoring-problem.hh and beam-quanting.cc, lilypond, 10:22
  • Re: Issue 1929 in lilypond: stem-tremolo-position.ly broken, lilypond, 09:35
  • Re: Issue 1929 in lilypond: stem-tremolo-position.ly broken, lilypond, 09:31
  • Re: Issue 1921 in lilypond: Creates convert-ly rules for flag syntax changes, lilypond, 09:27
  • Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding, lilypond, 09:23
  • Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse, lilypond, 09:19
  • Re: Issue 910 in lilypond: Non-allowed span-bars should not affect Lyrics, lilypond, 09:15
  • Re: Issue 1491 in lilypond: git-cl hangs when uploading patches due to bad mime-type, lilypond, 07:56
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 06:51
  • Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse, address@hidden, 02:50
  • Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse, lilypond, 02:24
  • Re: Issue 910 in lilypond: Non-allowed span-bars should not affect Lyrics, lilypond, 02:20
  • Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding, lilypond, 01:16
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 00:01
• September 29, 2011
  • Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse, lilypond, 21:26
  • Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding, lilypond, 19:57
  • Issue 1947 in lilypond: Stem Tremoli for double-stemmed notes are too short on the right side., lilypond, 19:24
  • Re: Issue 307 in lilypond: collision slur with tuplet bracket, lilypond, 17:30
  • Issue 1946 in lilypond: Problem with kerning (Ubuntu, external ttf/otf fonts), lilypond, 11:25
  • Re: Fwd: Problem with Kerning, Dmytro O. Redchuk, 11:22
  • Re: Issue 307 in lilypond: collision slur with tuplet bracket, lilypond, 11:02
  • Re: Issue 1941 in lilypond: Patch: Fixes to projecthosting_upload.py, lilypond, 10:33
  • Re: Issue 307 in lilypond: collision slur with tuplet bracket, lilypond, 10:03
  • Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 08:52
  • Re: Issue 1929 in lilypond: stem-tremolo-position.ly broken, lilypond, 08:23
  • Re: Issue 1897 in lilypond: Automatically set the eps backend in lilypond-book-preamble.ly, lilypond, 06:05
  • Re: Issue 1477 in lilypond: suppress output for expected warnings, lilypond, 06:01
  • Re: Issue 1921 in lilypond: Creates convert-ly rules for flag syntax changes, lilypond, 05:53
  • Re: Issue 1921 in lilypond: Creates convert-ly rules for flag syntax changes, address@hidden, 05:52
  • Re: Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc, lilypond, 03:38
  • Re: Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc, lilypond, 03:33
  • Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 03:29
  • Re: Issue 1938 in lilypond: MIDI volume can exceed maximum value (Rietveld 5134047), lilypond, 00:31
  • Re: Issue 1938 in lilypond: MIDI volume can exceed maximum value (Rietveld 5134047), lilypond, 00:27
  • Re: Issue 1925 in lilypond: fingering misplaced when avoiding slur, on some operating systems, lilypond, 00:23
  • Re: Issue 1913 in lilypond: musicxml2ly: <movement-title> not converted in the presence of a non-empty <work-title>, lilypond, 00:19
  • Re: Issue 509 in lilypond: collision nested tuplet numbers, lilypond, 00:14
  • Re: Issue 1844 in lilypond: Changes variable names in include/beam-scoring-problem.hh and beam-quanting.cc, lilypond, 00:01
• September 28, 2011
  • Re: Issue 307 in lilypond: collision slur with tuplet bracket, lilypond, 23:57
  • Re: Issue 1321 in lilypond: Enhancement: add partcombineUp and partcombineDown functions, lilypond, 23:53
  • Re: Issue 1477 in lilypond: suppress output for expected warnings, lilypond, 23:49
  • Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse, lilypond, 23:45
  • Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding, lilypond, 23:41
  • Re: Issue 1871 in lilypond: Several fixes for annotate-spacing, lilypond, 23:37
  • Re: Issue 1921 in lilypond: Creates convert-ly rules for flag syntax changes, lilypond, 23:33
  • Re: Issue 1929 in lilypond: stem-tremolo-position.ly broken, lilypond, 23:29
  • Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 19:17
  • Fwd: Problem with Kerning, Janek Warchoł, 17:58
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 08:02
  • Re: Issue 1008 in lilypond: Some warning/error messages are not prefixed with 'warning:'/'error:', lilypond, 07:22
  • Re: Issue 1008 in lilypond: Some warning/error messages are not prefixed with 'warning:'/'error:', lilypond, 07:13
  • Re: Issue 1008 in lilypond: Some warning/error messages are not prefixed with 'warning:'/'error:', lilypond, 05:52
  • Issue 1945 in lilypond: Patch: lily/bezier.cc: Safer use of floating point, lilypond, 03:23
  • Issue 1944 in lilypond: Patch: lily/bezier.cc: Avoid a floating point compare, lilypond, 02:46
  • Re: Issue 1931 in lilypond: Doc: Snippet in NR (LSR snippet 591) MMRs 'staff-position = #0 should be revised, lilypond, 00:53
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 00:48
• September 27, 2011
  • Re: Issue 1910 in lilypond: Implement define-event-function, lilypond, 23:58
  • Re: Issue 935 in lilypond: Enhancement: optional arguments in music functions, lilypond, 23:54
  • Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs, lilypond, 20:37
  • Re: Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc, Colin Campbell, 20:37
  • Re: Issue 1938 in lilypond: MIDI volume can exceed maximum value (Rietveld 5134047), lilypond, 17:28
  • Re: Issue 155 in lilypond: \parenthesize does not take accidentals into account, lilypond, 17:22
  • Re: Issue 1941 in lilypond: Patch: Fixes to projecthosting_upload.py, lilypond, 17:16
  • Re: Issue 1927 in lilypond: 2.15.2 doesn't build anymore on Mageia, lilypond, 10:25
  • Re: Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc, lilypond, 09:17
  • Re: Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc, lilypond, 09:13
  • Re: Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc, lilypond, 07:10
  • Re: Issue 1931 in lilypond: Doc: Snippet in NR (LSR snippet 591) MMRs 'staff-position = #0 should be revised, lilypond, 07:06
  • Re: Issue 1812 in lilypond: NR Context Layout Order rewrite (5.1.7), lilypond, 07:02
  • Re: Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc, lilypond, 06:57
  • Re: Issue 1941 in lilypond: Patch: Fixes to projecthosting_upload.py, lilypond, 05:47
  • Re: Issue 1942 in lilypond: Patch: Fixes to projecthosting_upload.py, lilypond, 05:43
  • Issue 1942 in lilypond: Patch: Fixes to projecthosting_upload.py, lilypond, 05:39
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 05:33
  • Re: Issue 1491 in lilypond: git-cl hangs when uploading patches due to bad mime-type, lilypond, 05:11
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 05:07
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 05:02
  • Re: Issue 1008 in lilypond: Some warning/error messages are not prefixed with 'warning:'/'error:', lilypond, 04:58
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 04:54
  • Re: Issue 1941 in lilypond: Patch: Fixes to projecthosting_upload.py, lilypond, 04:50
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 04:46
  • Re: Issue 1008 in lilypond: Some warning/error messages are not prefixed with 'warning:'/'error:', lilypond, 04:42
  • Re: Issue 1193 in lilypond: Enhancement: internal ledger lines, lilypond, 04:38
  • Re: Issue 1292 in lilypond: Enhancement: twelve-notation support, lilypond, 04:34
  • Re: Issue 1301 in lilypond: Strange collision of note and clef, lilypond, 04:29
  • Re: Issue 1529 in lilypond: filename changing should not trigger a regtests comparison, lilypond, 04:26
  • Re: Issue 1795 in lilypond: Improve handling of languages in doc and website build, lilypond, 04:21
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 04:17
  • Re: Issue 1868 in lilypond: Loglevels in our python scripts (lilypond-book, musicxml2ly, convert-ly), lilypond, 04:13
  • Re: Issue 1878 in lilypond: Add support for custom ledger positions, using two new staff-symbol properties, lilypond, 04:09
  • Re: Issue 1889 in lilypond: Lilypond-book: Improve options handling by processing everything in one place, lilypond, 04:05
  • Re: Issue 1891 in lilypond: New alist to replace special characters, lilypond, 04:01
  • Re: Issue 1893 in lilypond: Terminates outside_staff_callback early if a grob is outside a slur's X-extent, lilypond, 03:57
  • Re: Issue 1905 in lilypond: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure, lilypond, 03:53
  • Re: Issue 1909 in lilypond: Doc: add a note about \relative f to notation (Rietveld 5096046), lilypond, 03:49
  • Re: Issue 1914 in lilypond: Manual page break in a user defined variable, lilypond, 03:45
  • Re: Issue 1920 in lilypond: arguments in docs don't alway agree, lilypond, 03:41
  • Re: Issue 1932 in lilypond: error: need \paper for paper block, lilypond, 03:37
  • Issue 1941 in lilypond: Patch: Fixes to projecthosting_upload.py, lilypond, 03:32
  • Re: Issue 1937 in lilypond: Patch: Uses Stem::beam_end_corrective to get tremolo heights right, lilypond, 02:58
  • Re: Issue 1940 in lilypond: Patch: Creates convert-ly rules for flag syntax changes, lilypond, 02:54
  • Issue 1940 in lilypond: Patch: Creates convert-ly rules for flag syntax changes, lilypond, 02:50
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 02:45
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 02:30
  • Re: Issue 155 in lilypond: \parenthesize does not take accidentals into account, lilypond, 00:58
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 00:54
  • Re: Issue 1844 in lilypond: Changes variable names in include/beam-scoring-problem.hh and beam-quanting.cc, lilypond, 00:50
  • Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse, lilypond, 00:46
  • Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding, lilypond, 00:42
  • Re: Issue 1921 in lilypond: Creates convert-ly rules for flag syntax changes, lilypond, 00:38
  • Re: Issue 1871 in lilypond: Several fixes for annotate-spacing, lilypond, 00:34
  • Re: Issue 1812 in lilypond: NR Context Layout Order rewrite (5.1.7), lilypond, 00:30
  • Re: Issue 1477 in lilypond: suppress output for expected warnings, lilypond, 00:26
  • Re: Issue 1321 in lilypond: Enhancement: add partcombineUp and partcombineDown functions, lilypond, 00:22
  • Re: Issue 307 in lilypond: collision slur with tuplet bracket, lilypond, 00:18
  • Re: Issue 1929 in lilypond: stem-tremolo-position.ly broken, lilypond, 00:14
  • Re: Issue 1925 in lilypond: fingering misplaced when avoiding slur, on some operating systems, lilypond, 00:09
• September 26, 2011
  • Re: Issue 1922 in lilypond: Adds StemTremolo to the note column's element list., lilypond, 23:59
  • Re: Issue 1778 in lilypond: slashedGrace function (graces with slashed stems but no slur, e.g. when grace is tied) needs documenting, lilypond, 23:48
  • Re: Issue 11 in lilypond: beamlet on wrong side of tuplet sixteenth, lilypond, 23:40
  • Re: Issue 155 in lilypond: \parenthesize does not take accidentals into account, lilypond, 22:59
  • Re: Apparently bogus warning with 2.15.12, Colin Campbell, 21:39
  • Issue 1939 in lilypond: showLastLength with hidden tie error message, lilypond, 21:36
  • Re: Apparently bogus warning with 2.15.12, Reinhold Kainhofer, 19:40
  • Re: MIDI output: min/max MIDI volume levels, dynamics of polyphonic passages within a single Voice, Janek Warchoł, 18:41
  • Re: Issue 1938 in lilypond: MIDI volume can exceed maximum value (Rietveld 5134047), lilypond, 18:37
  • Issue 1938 in lilypond: MIDI volume can exceed maximum value, lilypond, 18:32
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 17:41
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 17:24
  • Re: Apparently bogus warning with 2.15.12, Nick Payne, 16:40
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 15:07
  • Re: Issue 34 in lilypond: Grace synchronization, Keith OHara, 15:05
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 14:59
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 14:48
  • Re: Issue 1931 in lilypond: Doc: Snippet in NR (LSR snippet 591) MMRs 'staff-position = #0 should be revised, lilypond, 08:40
  • Re: Issue 1931 in lilypond: Doc: Snippet in NR (LSR snippet 591) MMRs 'staff-position = #0 should be revised, lilypond, 08:35
  • Re: Issue 1934 in lilypond: HTML Manuals on website do not have vertical scroll on Mobile Versions of Safari Browser, lilypond, 08:29
  • Re: Issue 1874 in lilypond: some stems are no longer transparent in the docs, lilypond, 08:23
  • Re: Issue 1935 in lilypond: Doc: internal ledger lines need to be documented in NR and added to Changes, lilypond, 08:19
  • Re: Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc, lilypond, 07:58
  • Re: Issue 1909 in lilypond: Doc: add a note about \relative f to notation (Rietveld 5096046), lilypond, 06:34
  • Re: Issue 1266 in lilypond: Dots in chords can not be moved, lilypond, 06:30
  • Re: Issue 1937 in lilypond: Patch: Uses Stem::beam_end_corrective to get tremolo heights right, lilypond, 04:13
  • Re: Issue 34 in lilypond: Grace synchronization, David Kastrup, 03:32
  • Re: Issue 1932 in lilypond: error: need \paper for paper block, lilypond, 03:23
  • Issue 1937 in lilypond: Patch: Uses Stem::beam_end_corrective to get tremolo heights right, lilypond, 03:00
  • Re: Issue 34 in lilypond: Grace synchronization, address@hidden, 02:39
  • Re: Issue 34 in lilypond: Grace synchronization, lilypond, 02:32
  • Re: Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc, lilypond, 02:14
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 01:24
  • Re: Issue 1932 in lilypond: error: need \paper for paper block, lilypond, 01:20
• September 25, 2011
  • Re: Issue 1936 in lilypond: Patch: fix 123, lilypond, 21:28
  • Issue 1936 in lilypond: Patch: fix 123, lilypond, 21:24
  • Re: Some MIDI instruments don't work, Graham Percival, 19:02
  • Some MIDI instruments don't work, Mark Polesky, 18:47
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 17:49
  • Re: MIDI output: min/max MIDI volume levels, dynamics of polyphonic passages within a single Voice, Janek Warchoł, 17:33
  • Re: Issue 1911 in lilypond: dynamics on chords with notehead to left and right of stem are wrongly aligned, lilypond, 15:03
  • Re: Issue 1835 in lilypond: no learing manual pdf in dutch, lilypond, 14:45
  • Re: Issue 1929 in lilypond: stem-tremolo-position.ly broken, lilypond, 14:15
  • Re: Issue 1909 in lilypond: Doc: add a note about \relative f to notation (Rietveld 5096046), lilypond, 13:45
  • Re: Issue 1878 in lilypond: Add support for custom ledger positions, using two new staff-symbol properties, lilypond, 13:13
  • Re: Issue 1292 in lilypond: Enhancement: twelve-notation support, lilypond, 13:09
  • Re: Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc, lilypond, 11:48
  • Re: Issue 1292 in lilypond: Enhancement: twelve-notation support, lilypond, 11:10
  • Re: Issue 1292 in lilypond: Enhancement: twelve-notation support, lilypond, 10:46
  • Re: Issue 1193 in lilypond: Enhancement: internal ledger lines, lilypond, 10:42
  • Re: Issue 1935 in lilypond: Doc: internal ledger lines need to be documented in NR and added to Changes, lilypond, 10:13
  • Re: Images not showing on lilypond.org, Phil Holmes, 09:40
  • Re: Issue 1778 in lilypond: slashedGrace function (graces with slashed stems but no slur, e.g. when grace is tied) needs documenting, lilypond, 09:28
  • Re: Issue 1193 in lilypond: Enhancement: internal ledger lines, lilypond, 09:24
  • Re: Issue 1812 in lilypond: NR Context Layout Order rewrite (5.1.7), lilypond, 08:25
  • Re: Issue 1929 in lilypond: stem-tremolo-position.ly broken, lilypond, 08:21
  • Re: Issue 1929 in lilypond: stem-tremolo-position.ly broken, lilypond, 08:17
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 08:13
  • Re: Issue 1686 in lilypond: Compile scheme files to scm/out when using Guile V2.n. Also load and run .go files if available, lilypond, 08:09
  • Re: Issue 1826 in lilypond: Guile 2.0 compat: `conditional-circle-markup' definition needs to be relocated, lilypond, 08:05
  • Re: Issue 1686 in lilypond: Compile scheme files to scm/out when using Guile V2.n. Also load and run .go files if available, lilypond, 08:01
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 07:57
  • Re: Issue 1193 in lilypond: Enhancement: internal ledger lines, lilypond, 07:53
  • Issue 1935 in lilypond: Doc: internal ledger lines need to be documented in NR and added to Changes, lilypond, 07:49
  • Re: Issue 1929 in lilypond: stem-tremolo-position.ly broken, lilypond, 07:45
  • Re: Issue 1826 in lilypond: Guile 2.0 compat: `conditional-circle-markup' definition needs to be relocated, lilypond, 07:41
  • Re: Issue 1905 in lilypond: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure, lilypond, 07:37
  • Re: Issue 1193 in lilypond: Enhancement: internal ledger lines, lilypond, 07:33
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 07:27
  • Re: Issue 1932 in lilypond: error: need \paper for paper block, lilypond, 07:16
  • Re: Issue 804 in lilypond: Code cleaning: checking types-conversion issues and other build warnings, lilypond, 06:59
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 06:53
  • Re: Issue 804 in lilypond: Code cleaning: checking types-conversion issues and other build warnings, lilypond, 06:49
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 06:45
  • Re: Issue 1929 in lilypond: stem-tremolo-position.ly broken, lilypond, 06:41
  • Issue 1934 in lilypond: Mobile Safari web docs truncated, lilypond, 06:37
  • Re: Issue 1932 in lilypond: error: need \paper for paper block, lilypond, 06:33
  • Re: Issue 1008 in lilypond: Some warning/error messages are not prefixed with 'warning:'/'error:', lilypond, 06:29
  • Re: Issue 1135 in lilypond: music functions should use funindex instead of findex, lilypond, 06:25
  • Re: \book / \bookpart error with \layout {} outside of the \score, eluze, 06:21
  • Re: Issue 1584 in lilypond: removing parser DIGIT rule, lilypond, 06:21
  • Re: Issue 1930 in lilypond: convert-ly: No rule for MMRs 'staff-position = #0, lilypond, 06:17
  • Re: Mobile Safari web docs truncated, Dmytro O. Redchuk, 06:17
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 06:13
  • Re: Issue 1815 in lilypond: lilypond-book fails on Windows, lilypond, 06:08
  • Re: Issue 1822 in lilypond: New short and long lyric ties., lilypond, 06:04
  • Re: Issue 1845 in lilypond: Creates pure closures, lilypond, 06:00
  • Re: Issue 1913 in lilypond: musicxml2ly: <movement-title> not converted in the presence of a non-empty <work-title>, lilypond, 05:56
  • Re: Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 05:52
  • Re: Issue 1193 in lilypond: Enhancement: internal ledger lines, lilypond, 05:48
  • Re: lilypond-book needs msvcrt again, Phil Holmes, 05:45
  • Issue 1933 in lilypond: Lilypond-book requires msvcrt again, lilypond, 05:44
  • Re: Issue 1193 in lilypond: Enhancement: internal ledger lines, lilypond, 05:40
  • Re: \book / \bookpart error with \layout {} outside of the \score, Phil Holmes, 05:37
  • Issue 1932 in lilypond: error: need \paper for paper block, lilypond, 05:36
  • Re: Issue 1913 in lilypond: musicxml2ly: <movement-title> not converted in the presence of a non-empty <work-title>, lilypond, 05:26
  • \book / \bookpart error with \layout {} outside of the \score, -Eluze, 04:39
  • Re: Issue 1321 in lilypond: Enhancement: add partcombineUp and partcombineDown functions, lilypond, 04:25
  • lilypond-book needs msvcrt again, Trevor Daniels, 04:20
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 04:00
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 03:43
  • Re: Issue 1929 in lilypond: stem-tremolo-position.ly broken, lilypond, 03:11
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 02:20
  • Issue 1931 in lilypond: Doc: MMRs 'staff-position = #0 should be revised, lilypond, 01:49
  • Issue 1930 in lilypond: convert-ly: No rule for MMRs 'staff-position = #0, lilypond, 01:45
  • Issue 1929 in lilypond: stem-tremolo-position.ly broken, lilypond, 00:31
• September 24, 2011
  • Re: Issue 1329 in lilypond: \afterGrace placement/behaviour to be discussed, lilypond, 20:01
  • Re: Issue 1812 in lilypond: NR Context Layout Order rewrite (5.1.7), lilypond, 16:49
  • Re: Issue 1905 in lilypond: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure, lilypond, 16:33
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 16:29
  • Re: Issue 1321 in lilypond: Enhancement: add partcombineUp and partcombineDown functions, lilypond, 16:25
  • Re: Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc, lilypond, 16:21
  • Re: Issue 509 in lilypond: collision nested tuplet numbers, lilypond, 16:17
  • Re: Issue 307 in lilypond: collision slur with tuplet bracket, lilypond, 16:13
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 16:09
  • Re: Issue 1871 in lilypond: Several fixes for annotate-spacing, lilypond, 16:05
  • Re: Issue 1844 in lilypond: Changes variable names in include/beam-scoring-problem.hh and beam-quanting.cc, lilypond, 16:01
  • Re: Issue 1844 in lilypond: Changes variable names in include/beam-scoring-problem.hh and beam-quanting.cc, lilypond, 15:57
  • Re: Issue 1925 in lilypond: fingering misplaced when avoiding slur, on some operating systems, lilypond, 15:47
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 15:43
  • Re: Issue 1913 in lilypond: musicxml2ly: <movement-title> not converted in the presence of a non-empty <work-title>, lilypond, 15:39
  • Re: Issue 1924 in lilypond: Adds StemTremolo to the note column's element list (dupe of 1922), lilypond, 15:35
  • Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse, lilypond, 15:31
  • Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding, lilypond, 15:21
  • Re: Issue 1922 in lilypond: Adds StemTremolo to the note column's element list., lilypond, 15:14
  • Re: Issue 1921 in lilypond: Creates convert-ly rules for flag syntax changes, lilypond, 15:08
  • Re: Issue 1926 in lilypond: 2.15.12 processing speed problems, mike, 14:44
  • Re: Issue 1928 in lilypond: Incorrect alignment of lyrics on tied notes when using completion_heads_engraver, lilypond, 13:55
  • Re: Issue 1926 in lilypond: 2.15.12 processing speed problems, lilypond, 13:50
  • Re: Completion heads engraver lyrics revisited, Trevor Daniels, 13:07
  • Issue 1928 in lilypond: Incorrect alignment of lyrics on tied notes when using completion_heads_engraver, lilypond, 13:05
  • Re: Issue 1926 in lilypond: 2.15.12 processing speed problems, lilypond, 11:45
  • re: umlaut in title, Karim Haddad, 11:41
  • Re: umlaut doesn't work on o in title, Phil Holmes, 11:29
  • umlaut doesn't work on o in title, Karim Haddad, 11:22
  • Re: Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc, lilypond, 10:59
  • Re: Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc, lilypond, 10:44
  • Re: Issue 1927 in lilypond: 2.15.2 doesn't build anymore on Mageia, David Kastrup, 10:40
  • Re: bookOutputName does not work within book block in 2.15.12, David Kastrup, 10:34
  • Issue 1927 in lilypond: 2.15.2 doesn't build anymore on Mageia, lilypond, 10:30
  • bookOutputName does not work within book block in 2.15.12, Tony Towers, 10:19
  • Re: Issue 1293 in lilypond: lilypond-book should use "quote" environment of LaTeX (instead of "quotation"), lilypond, 09:48
  • Re: Issue 1293 in lilypond: lilypond-book should use "quote" environment of LaTeX (instead of "quotation"), lilypond, 09:30
  • Re: Issue 1894 in lilypond: Prunes stem::length down to the bare minimum, lilypond, 09:26
  • Re: Issue 1914 in lilypond: Manual page break in a user defined variable, lilypond, 09:22
  • Re: Issue 1910 in lilypond: Implement define-event-function, lilypond, 09:18
  • Re: Issue 1301 in lilypond: Strange collision of note and clef, lilypond, 09:14
  • Re: Issue 1926 in lilypond: 2.15.12 processing speed problems, David Kastrup, 08:32
  • Re: Issue 1926 in lilypond: 2.15.12 processing speed problems, address@hidden, 08:27
  • Re: Issue 1891 in lilypond: New alist to replace special characters, lilypond, 06:50
  • Issue 1926 in lilypond: 2.15.12 processing speed problems, lilypond, 06:43
  • Re: Issue 1321 in lilypond: Enhancement: add partcombineUp and partcombineDown functions, lilypond, 06:34
  • Re: Issue 509 in lilypond: collision nested tuplet numbers, lilypond, 06:30
  • Re: Issue 307 in lilypond: collision slur with tuplet bracket, lilypond, 06:26
  • Re: Issue 11 in lilypond: beamlet on wrong side of tuplet sixteenth, lilypond, 06:22
  • Re: Issue 1845 in lilypond: Creates pure closures, lilypond, 06:18
  • Re: Issue 1878 in lilypond: Add support for custom ledger positions, using two new staff-symbol properties, lilypond, 06:14
  • Completion heads engraver lyrics revisited, Arvid Grøtting, 06:13
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 06:10
  • Re: Issue 1871 in lilypond: Several fixes for annotate-spacing, lilypond, 06:07
  • Re: Issue 1845 in lilypond: Creates pure closures, lilypond, 06:02
  • Re: Issue 1923 in lilypond: Sketch for broken beams with consistent slopes, lilypond, 05:58
  • Re: Issue 1844 in lilypond: Changes variable names in include/beam-scoring-problem.hh and beam-quanting.cc, lilypond, 05:54
  • Re: Issue 1844 in lilypond: Changes variable names in include/beam-scoring-problem.hh and beam-quanting.cc, lilypond, 05:50
  • Issue 1925 in lilypond: fingering misplaced when avoiding slur, on some operating systems, lilypond, 03:08
  • Re: Issue 1477 in lilypond: suppress output for expected warnings, lilypond, 03:02
  • Re: Mobile Safari web docs truncated, Peekay Ex, 03:00
  • Re: Issue 1477 in lilypond: suppress output for expected warnings, lilypond, 02:31
  • Re: Issue 935 in lilypond: Enhancement: optional arguments in music functions, lilypond, 01:16
• September 23, 2011
  • Mobile Safari web docs truncated, Matt Puumala, 23:55
  • Re: Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc, lilypond, 23:37
  • Re: Issue 1477 in lilypond: suppress output for expected warnings, lilypond, 23:33
  • Re: Issue 1477 in lilypond: suppress output for expected warnings, lilypond, 23:29
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 23:00
  • Re: Issue 1913 in lilypond: musicxml2ly: <movement-title> not converted in the presence of a non-empty <work-title>, lilypond, 22:56
  • Issue 1924 in lilypond: Adds StemTremolo to the note column's element list, lilypond, 22:52
  • Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse, lilypond, 22:48
  • Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding, lilypond, 22:44
  • Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse, lilypond, 22:40
  • Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse, lilypond, 22:36
  • Issue 1923 in lilypond: Sketch for broken beams with consistent slopes, lilypond, 22:32
  • Issue 1922 in lilypond: Adds StemTremolo to the note column's element list., lilypond, 22:28
  • Issue 1921 in lilypond: Creates convert-ly rules for flag syntax changes, lilypond, 22:24
  • Re: Issue 1920 in lilypond: arguments in docs don't alway agree, lilypond, 22:21
  • Re: Issue 1801 in lilypond: Clarify "\repeat unfold" in the documentation, lilypond, 22:20
  • Re: Issue 935 in lilypond: Enhancement: optional arguments in music functions, lilypond, 22:16
  • Re: Issue 935 in lilypond: Enhancement: optional arguments in music functions, lilypond, 22:08
  • Re: Issue 1801 in lilypond: Clarify "\repeat unfold" in the documentation, lilypond, 21:39
  • Re: Issue 1891 in lilypond: New alist to replace special characters, lilypond, 21:35
  • Re: Issue 1897 in lilypond: Automatically set the eps backend in lilypond-book-preamble.ly, lilypond, 21:31
  • Re: Issue 1135 in lilypond: music functions should use funindex instead of findex, lilypond, 20:50
  • Re: Issue 1911 in lilypond: dynamics on chords with notehead to left and right of stem are wrongly aligned, lilypond, 19:23
  • Re: Issue 1477 in lilypond: suppress output for expected warnings, lilypond, 18:37
  • Re: Images not showing on lilypond.org, Phil Holmes, 15:46
  • Re: Build issue, Graham Percival, 15:09
  • Re: Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc, lilypond, 15:08
  • Re: Images not showing on lilypond.org, Graham Percival, 15:07
  • Re: Issue 1920 in lilypond: arguments in docs don't alway agree, lilypond, 12:57
  • Re: Build issue, Stan Sanderson, 10:38
  • Re: Issue 1868 in lilypond: Loglevels in our python scripts (lilypond-book, musicxml2ly, convert-ly), lilypond, 10:14
  • Re: Issue 1889 in lilypond: Lilypond-book: Improve options handling by processing everything in one place, lilypond, 10:10
  • Re: Issue 1193 in lilypond: Enhancement: internal ledger lines, lilypond, 08:00
  • Re: Issue 1193 in lilypond: Enhancement: internal ledger lines, lilypond, 06:16
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, Graham Percival, 05:56
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, Graham Percival, 05:55
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, Reinhold Kainhofer, 05:49
  • Re: Issue 1193 in lilypond: Enhancement: internal ledger lines, lilypond, 05:49
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, David Kastrup, 05:27
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, Reinhold Kainhofer, 05:22
  • Re: Issue 1920 in lilypond: arguments in docs don't alway agree, lilypond, 04:50
  • Re: Issue 935 in lilypond: Enhancement: optional arguments in music functions, lilypond, 04:46
  • Re: Issue 1920 in lilypond: arguments in docs don't alway agree, lilypond, 04:41
  • Issue 1920 in lilypond: arguments in docs don't alway agree, lilypond, 04:37
  • Re: Issue 935 in lilypond: Enhancement: optional arguments in music functions, lilypond, 04:33
  • Re: Issue 935 in lilypond: Enhancement: optional arguments in music functions, lilypond, 04:29
  • Re: Issue 1914 in lilypond: Manual page break in a user definedvariable, Phil Holmes, 04:17
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 03:50
  • Re: Build issue, Graham Percival, 03:46
  • Issue 1919 in lilypond: lilypond 2.15.12 fails on darwin-ppc, lilypond, 03:46
  • Re: Issue 1918 in lilypond: possible bad output in mensural-ligatures.ly, lilypond, 03:39
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 03:35
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 03:31
  • Re: Issue 380 in lilypond: Try to auto-detect cyclic references in header fields (was 'cycling markup reference segfaults'), lilypond, 03:03
  • Re: Issue 935 in lilypond: Enhancement: optional arguments in music functions, lilypond, 02:58
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 02:54
  • Re: possible bad output in mensural-ligatures.ly, Dmytro O. Redchuk, 02:11
  • Issue 1918 in lilypond: possible bad output in mensural-ligatures.ly, lilypond, 02:10
• September 22, 2011
  • Re: Images not showing on lilypond.org, Trevor Daniels, 19:15
  • Re: Images not showing on lilypond.org, Graham Percival, 19:00
  • Images not showing on lilypond.org, Trevor Daniels, 18:54
  • Re: Issue 935 in lilypond: Enhancement: optional arguments in music functions, lilypond, 17:50
  • Re: Issue 935 in lilypond: Enhancement: optional arguments in music functions, lilypond, 16:28
  • Re: Issue 1914 in lilypond: Manual page break in a user defined variable, lilypond, 16:09
  • Re: Issue 1914 in lilypond: Manual page break in a user defined variable, Peekay Ex, 15:46
  • Re: Issue 1914 in lilypond: Manual page break in a user defined variable, lilypond, 15:39
  • Re: Issue 1910 in lilypond: Implement define-event-function, lilypond, 15:35
  • Re: Issue 1914 in lilypond: Manual page break in a user defined variable, lilypond, 15:31
  • Re: Issue 1914 in lilypond: Manual page break in a user defined variable, lilypond, 15:25
  • Re: Issue 1914 in lilypond: Manual page break in a user defined variable, lilypond, 15:25
  • Re: Issue 1909 in lilypond: Doc: add a note about \relative f to notation (Rietveld 5096046), lilypond, 15:21
  • Re: Issue 1913 in lilypond: musicxml2ly: <movement-title> not converted in the presence of a non-empty <work-title>, lilypond, 15:17
  • Re: Issue 1910 in lilypond: Implement define-event-function, lilypond, 15:00
  • Re: possible bad output in mensural-ligatures.ly, Reinhold Kainhofer, 12:41
  • Re: possible bad output in mensural-ligatures.ly, Graham Percival, 12:32
  • Re: possible bad output in mensural-ligatures.ly, David Kastrup, 12:17
  • Re: possible bad output in mensural-ligatures.ly, Graham Percival, 11:58
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 10:50
  • Issue 1917 in lilypond: Hyperlinks in web-big-page.html do not work, lilypond, 10:46
  • Build issue, Stan Sanderson, 10:45
  • Re: Horizontal spacing depends on stem 'direction, Janek Warchoł, 09:59
  • Re: Issue 1584 in lilypond: removing parser DIGIT rule, lilypond, 09:58
  • Re: Issue 1914 in lilypond: Manual page break in a user defined variable, lilypond, 09:54
  • Re: Issue 1914 in lilypond: Manual page break in a user defined variable, lilypond, 09:50
  • Re: Issue 1839 in lilypond: Improves some parmesan noteheads., lilypond, 09:46
  • Re: Issue 456 in lilypond: \laissezVibrer in chords, lilypond, 09:42
  • Re: Issue 1822 in lilypond: New short and long lyric ties., lilypond, 09:38
  • Re: Issue 1584 in lilypond: removing parser DIGIT rule, lilypond, 09:34
  • Re: Horizontal spacing depends on stem 'direction, Reinhold Kainhofer, 09:32
  • Re: Issue 1598 in lilypond: Dynamics staff on lower piano staff shifts PianoStaff name, lilypond, 09:30
  • Re: Issue 1741 in lilypond: Tablature Bug when pitch is higher then beh in a quarter-tone string, lilypond, 09:26
  • Re: Issue 1743 in lilypond: lilypond-2.15.4-1.mingw.exe does not install PATH on Windows 7 SP1, lilypond, 09:22
  • Re: Issue 1775 in lilypond: LSR: add broken- and unbroken slur shaping function, lilypond, 09:18
  • Re: Issue 1839 in lilypond: Improves some parmesan noteheads., lilypond, 09:14
  • Issue 1916 in lilypond: lilypond should issue a warning regarding incorrect ligature, lilypond, 09:10
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 09:06
  • Re: Issue 1815 in lilypond: lilypond-book fails on Windows, lilypond, 09:02
  • Re: Issue 1822 in lilypond: New short and long lyric ties., lilypond, 08:57
  • Re: Issue 1839 in lilypond: Improves some parmesan noteheads., lilypond, 08:54
  • Re: Issue 1840 in lilypond: Fixes figuredBassCenterContinuations., lilypond, 08:50
  • Re: Issue 1854 in lilypond: Add some polyphonically directed grobs, lilypond, 08:45
  • Re: Issue 1866 in lilypond: Uses langdefs.py to create language list for create-weblinks-itexi.py, lilypond, 08:41
  • Re: Issue 1876 in lilypond: MusicXML: fix case when some elements have a staff number, while others don't, lilypond, 08:37
  • Re: Issue 1880 in lilypond: Presence of a bar number changes whole-measure rest width significantly, lilypond, 08:33
  • Re: Issue 1881 in lilypond: Multiple cyclic dependency errors for Beam/Stem, lilypond, 08:29
  • Re: possible bad output in mensural-ligatures.ly, Dmytro O. Redchuk, 08:26
  • Re: Issue 1882 in lilypond: parser.yy et al: turn \partial and \skip into music functions., lilypond, 08:25
  • Re: Issue 1888 in lilypond: Introduce a maximum depth for markup evaluation, lilypond, 08:21
  • Re: Issue 1840 in lilypond: Fixes figuredBassCenterContinuations., lilypond, 08:17
  • Re: Issue 1898 in lilypond: Unifies mensural ligatures with blot-diameter, lilypond, 08:13
  • Re: Issue 1894 in lilypond: Prunes stem::length down to the bare minimum, lilypond, 08:09
  • Re: possible bad output in mensural-ligatures.ly, Bertrand Bordage, 08:06
  • Re: Issue 1893 in lilypond: Terminates outside_staff_callback early if a grob is outside a slur's X-extent, lilypond, 08:05
  • Re: possible bad output in mensural-ligatures.ly, Dmytro O. Redchuk, 08:01
  • Re: Issue 1888 in lilypond: Introduce a maximum depth for markup evaluation, lilypond, 08:01
  • Re: Issue 1913 in lilypond: musicxml2ly: <movement-title> not converted in the presence of a non-empty <work-title>, lilypond, 07:57
  • Re: Issue 1910 in lilypond: Implement define-event-function, lilypond, 07:53
  • Re: Issue 1883 in lilypond: change longas similarly to how breves were changed, lilypond, 07:49
  • Re: Issue 1887 in lilypond: Doc: adding doc strings for \...DashPattern and \harmonicBy..., lilypond, 07:45
  • Re: Issue 1888 in lilypond: Introduce a maximum depth for markup evaluation, lilypond, 07:41
  • Re: Issue 1893 in lilypond: Terminates outside_staff_callback early if a grob is outside a slur's X-extent, lilypond, 07:37
  • Re: Issue 1894 in lilypond: Prunes stem::length down to the bare minimum, lilypond, 07:33
  • Re: Issue 1896 in lilypond: lost instrument names, lilypond, 07:29
  • Re: Issue 1898 in lilypond: Unifies mensural ligatures with blot-diameter, lilypond, 07:25
  • Re: Issue 1903 in lilypond: Page breaking does not work between different scores, lilypond, 07:20
  • Re: Issue 1914 in lilypond: Manual page break in a user defined variable, lilypond, 07:16
  • Re: possible bad output in mensural-ligatures.ly, Dmytro O. Redchuk, 07:12
  • Re: \fill-line, \column bug, Dmytro O. Redchuk, 07:09
  • Re: Issue 1912 in lilypond: Horizontal spacing depends on stem 'direction, lilypond, 07:02
  • Re: possible bad output in mensural-ligatures.ly, Janek Warchoł, 07:02
  • Re: Horizontal spacing depends on stem 'direction, Janek Warchoł, 06:56
  • Re: Issue 1914 in lilypond: Manual page break in a user defined variable, lilypond, 06:00
  • Re: Issue 1915 in lilypond: slurs don\'t avoid other voices, eluze, 05:41
  • Re: Issue 1405 in lilypond: Web: website Google search-bar should allow to search the website., lilypond, 05:41
  • Re: Issue 1894 in lilypond: Prunes stem::length down to the bare minimum, lilypond, 05:21
  • Re: Manual page break in a user defined variable, Eluze, 05:17
  • Re: Issue 1914 in lilypond: Manual page break in a user defined variable, lilypond, 05:14
  • Re: Issue 1914 in lilypond: Manual page break in a user defined variable, lilypond, 05:03
  • Re: Issue 1915 in lilypond: slurs don't avoid other voices, address@hidden, 04:42
  • Re: Issue 1898 in lilypond: Unifies mensural ligatures with blot-diameter, lilypond, 04:36
  • Re: \fill-line, \column bug, Alexander Kobel, 04:33
  • Issue 1915 in lilypond: slurs don't avoid other voices, lilypond, 04:31
  • Re: \fill-line, \column bug, Alexander Kobel, 04:31
  • Re: Issue 1894 in lilypond: Prunes stem::length down to the bare minimum, lilypond, 04:27
  • Re: Issue 1893 in lilypond: Terminates outside_staff_callback early if a grob is outside a slur's X-extent, lilypond, 04:23
  • Re: slurs don't avoid other voices, Dmytro O. Redchuk, 04:21
  • Re: Issue 1894 in lilypond: Prunes stem::length down to the bare minimum, lilypond, 04:19
  • Re: Issue 1301 in lilypond: Strange collision of note and clef, lilypond, 04:15
  • Issue 1914 in lilypond: Manual page break in a user defined variable, lilypond, 04:07
  • Re: Manual page break in a user defined variable, Dmytro O. Redchuk, 04:07
  • Re: Horizontal spacing depends on stem 'direction, David Kastrup, 04:05
  • Re: Horizontal spacing depends on stem 'direction, Dmytro O. Redchuk, 03:58
  • Re: musicxml2ly: <movement-title> not converted in the presence of a non-empty <work-title>, Dmytro O. Redchuk, 03:55
  • Re: Issue 1912 in lilypond: Horizontal spacing depends on stem 'direction, lilypond, 03:54
  • Issue 1913 in lilypond: musicxml2ly: <movement-title> not converted in the presence of a non-empty <work-title>, lilypond, 03:50
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 03:46
  • Re: Issue 1893 in lilypond: Terminates outside_staff_callback early if a grob is outside a slur's X-extent, lilypond, 03:42
  • Re: Horizontal spacing depends on stem 'direction, David Kastrup, 03:40
  • Re: \fill-line, \column bug, Dmytro O. Redchuk, 03:38
  • Re: Issue 1908 in lilypond: Causes lily to fail during regtests if binary is unoptimized, lilypond, 03:38
  • Re: Issue 1912 in lilypond: Horizontal spacing depends on stem 'direction, Dmytro O. Redchuk, 03:35
  • Re: possible bad output in mensural-ligatures.ly, Dmytro O. Redchuk, 03:33
  • Re: Issue 1912 in lilypond: Horizontal spacing depends on stem 'direction, address@hidden, 03:30
  • Re: Horizontal spacing depends on stem 'direction, Dmytro O. Redchuk, 03:26
  • Issue 1912 in lilypond: Horizontal spacing depends on stem 'direction, lilypond, 03:25
  • Re: packed-spacing works improperly with Mensural_ligature_engraver and Vaticana_ligature_engraver, Dmytro O. Redchuk, 03:21
  • Re: dynamics on chords with notehead to left and right of stem are wrongly aligned, Dmytro O. Redchuk, 03:17
  • Issue 1911 in lilypond: dynamics on chords with notehead to left and right of stem are wrongly aligned, lilypond, 03:16
  • Re: Issue 1891 in lilypond: New alist to replace special characters, lilypond, 00:58
  • Issue 1910 in lilypond: Implement define-event-function, lilypond, 00:54
  • Re: Issue 1891 in lilypond: New alist to replace special characters, lilypond, 00:50
  • Re: Issue 1905 in lilypond: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure, lilypond, 00:46
  • Re: Issue 1905 in lilypond: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure, lilypond, 00:42
  • Re: Issue 1897 in lilypond: Automatically set the eps backend in lilypond-book-preamble.ly, lilypond, 00:38
  • Re: Issue 1801 in lilypond: Clarify "\repeat unfold" in the documentation, lilypond, 00:34
  • Re: Issue 1477 in lilypond: suppress output for expected warnings, lilypond, 00:30
  • Re: Issue 935 in lilypond: Enhancement: optional arguments in music functions, lilypond, 00:26
  • Re: Issue 1292 in lilypond: Enhancement: twelve-notation support, lilypond, 00:22
  • Re: Issue 1898 in lilypond: Unifies mensural ligatures with blot-diameter, lilypond, 00:18
  • Re: Issue 1894 in lilypond: Prunes stem::length down to the bare minimum, lilypond, 00:14
  • Re: Issue 1893 in lilypond: Terminates outside_staff_callback early if a grob is outside a slur's X-extent, lilypond, 00:10
  • Re: Issue 1889 in lilypond: Lilypond-book: Improve options handling by processing everything in one place, lilypond, 00:06
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 00:02
• September 21, 2011
  • Re: Issue 1301 in lilypond: Strange collision of note and clef, lilypond, 23:58
  • Re: Issue 1193 in lilypond: Enhancement: internal ledger lines, lilypond, 23:53
  • Re: Issue 155 in lilypond: \parenthesize does not take accidentals into account, lilypond, 23:49
  • Re: Issue 1405 in lilypond: Web: website Google search-bar should allow to search the website., lilypond, 16:42
  • Re: Issue 1835 in lilypond: no learing manual pdf in dutch, lilypond, 16:37
  • Re: Issue 1835 in lilypond: no learing manual pdf in dutch, lilypond, 16:24
  • Re: Issue 1405 in lilypond: Web: website Google search-bar should allow to search the website., lilypond, 16:17
  • Manual page break in a user defined variable, Ed Gordijn, 14:57
  • Re: Issue 935 in lilypond: Enhancement: optional arguments in music functions, lilypond, 12:53
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 11:39
  • \fill-line, \column bug, arl, 09:36
  • Issue 1909 in lilypond: Doc: add a note about \relative f to notation (Rietveld 5096046), lilypond, 03:20
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 03:07
  • Re: Issue 1598 in lilypond: Dynamics staff on lower piano staff shifts PianoStaff name, lilypond, 02:43
  • Re: Issue 1801 in lilypond: Clarify "\repeat unfold" in the documentation, lilypond, 02:26
  • Issue 1908 in lilypond: Causes lily to fail during regtests if binary is unoptimized, lilypond, 01:57
  • Re: Issue 1905 in lilypond: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure, lilypond, 01:53
• September 20, 2011
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 21:07
  • Re: Incorrect voice combining when using PianoStaff and Staff changes, Colin Campbell, 21:05
  • Re: Issue 1893 in lilypond: Terminates outside_staff_callback early if a grob is outside a slur's X-extent, lilypond, 20:11
  • Re: Issue 1301 in lilypond: Strange collision of note and clef, lilypond, 20:07
  • Re: Issue 1193 in lilypond: Enhancement: internal ledger lines, lilypond, 20:03
  • Re: Issue 1477 in lilypond: suppress output for expected warnings, lilypond, 18:43
  • Incorrect voice combining when using PianoStaff and Staff changes, Thomas CHARDIN, 18:30
  • Issue 1907 in lilypond: accidentals in chordNames have diffferent vertical alignment depending on language, lilypond, 16:43
  • Re: Issue 1477 in lilypond: suppress output for expected warnings, lilypond, 16:09
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 13:51
  • Re: Issue 1477 in lilypond: suppress output for expected warnings, lilypond, 13:37
  • Issue 1906 in lilypond: Build fails on Fedora, lilypond, 13:12
  • Re: Issue 1900 in lilypond: Multiple fret-diagram-x markup commands and lilypond safe-mode, lilypond, 11:23
  • Re: Issue 1900 in lilypond: Multiple fret-diagram-x markup commands and lilypond safe-mode, lilypond, 11:19
  • Re: Windows PATH got cleared upon lilypond install, Peekay Ex, 10:43
  • Re: Issue 1675 in lilypond: lilypond as an html5 app, lilypond, 10:32
  • Re: Issue 935 in lilypond: Enhancement: optional arguments in music functions, lilypond, 09:11
  • Re: Issue 1890 in lilypond: Compiler warnings in make on 64-bit systems, lilypond, 09:07
  • Re: Issue 1477 in lilypond: suppress output for expected warnings, lilypond, 05:07
  • Re: Issue 1891 in lilypond: New alist to replace special characters, lilypond, 04:20
  • Re: Issue 1891 in lilypond: New alist to replace special characters, lilypond, 04:17
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 04:12
  • Re: Windows PATH got cleared upon lilypond install, Peekay Ex, 04:06
  • Re: Issue 1477 in lilypond: suppress output for expected warnings, lilypond, 04:01
  • Re: Issue 1897 in lilypond: Automatically set the eps backend in lilypond-book-preamble.ly, lilypond, 03:49
• September 19, 2011
  • Windows PATH got cleared upon lilypond install, Josh Vega, 23:40
  • Re: Issue 935 in lilypond: Enhancement: optional arguments in music functions, lilypond, 23:19
  • Re: Issue 1896 in lilypond: lost instrument names, lilypond, 22:42
  • Re: Issue 1868 in lilypond: Loglevels in our python scripts (lilypond-book, musicxml2ly, convert-ly), lilypond, 22:17
  • Re: Issue 1905 in lilypond: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure, Graham Percival, 13:42
  • Re: Issue 1905 in lilypond: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure, lilypond, 13:38
  • Re: Issue 1905 in lilypond: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure, David Kastrup, 12:28
  • Re: Issue 1905 in lilypond: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure, address@hidden, 11:52
  • Re: Issue 1905 in lilypond: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure, Neil Puttock, 11:22
  • Re: Issue 1905 in lilypond: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure, David Kastrup, 11:16
  • Re: Issue 1248 in lilypond: GUB produces a random "unbound open-file" in regtests, lilypond, 10:22
  • Re: Issue 1905 in lilypond: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure, Neil Puttock, 10:14
  • Re: Issue 1905 in lilypond: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure, address@hidden, 10:10
  • Re: Issue 1598 in lilypond: Dynamics staff on lower piano staff shifts PianoStaff name, lilypond, 10:07
  • Re: Issue 1905 in lilypond: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure, Neil Puttock, 10:04
  • Re: Issue 1248 in lilypond: GUB produces a random "unbound open-file" in regtests, lilypond, 09:32
  • Re: Issue 1905 in lilypond: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure, address@hidden, 08:06
  • Re: Issue 1905 in lilypond: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure, lilypond, 08:01
  • Re: Issue 1905 in lilypond: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure, lilypond, 07:52
  • Re: Issue 1248 in lilypond: GUB produces a random "unbound open-file" in regtests, lilypond, 06:56
  • Re: Issue 1888 in lilypond: Introduce a maximum depth for markup evaluation, lilypond, 06:52
  • Re: Issue 380 in lilypond: Try to auto-detect cyclic references in header fields (was 'cycling markup reference segfaults'), lilypond, 06:48
  • Issue 1905 in lilypond: Add note to CG 9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh or configure, lilypond, 06:42
  • Re: Issue 1883 in lilypond: change longas similarly to how breves were changed, lilypond, 03:55
  • Re: Issue 1887 in lilypond: Doc: adding doc strings for \...DashPattern and \harmonicBy..., lilypond, 03:51
  • Re: Issue 1822 in lilypond: New short and long lyric ties., lilypond, 03:46
  • Re: Issue 1854 in lilypond: Add some polyphonically directed grobs, lilypond, 03:42
  • Re: Issue 1822 in lilypond: New short and long lyric ties., lilypond, 03:35
• September 18, 2011
  • Re: Issue 1904 in lilypond: Patch: testing, ignore, lilypond, 22:28
  • Issue 1904 in lilypond: Patch: testing, ignore, lilypond, 22:24
  • Re: Issue 1741 in lilypond: Tablature Bug when pitch is higher then beh in a quarter-tone string, lilypond, 19:44
  • Re: Issue 1805 in lilypond: Ambitus engraver produces false warnings, lilypond, 19:37
  • Re: possible bad output in mensural-ligatures.ly, Bertrand Bordage, 18:01
  • possible bad output in mensural-ligatures.ly, Janek Warchoł, 17:55
  • Re: Issue 1898 in lilypond: Unifies mensural ligatures with blot-diameter, lilypond, 17:19
  • Re: Issue 1903 in lilypond: Page breaking does not work between different scores, lilypond, 16:54
  • Re: Issue 1903 in lilypond: Page breaking does not work between different scores, lilypond, 16:40
  • Re: Issue 1903 in lilypond: Page breaking does not work between different scores, lilypond, 12:59
  • Issue 1903 in lilypond: Page breaking does not work between different scores, lilypond, 12:37
  • Re: Manual page breaks, Phil Holmes, 12:37
  • Re: Issue 1899 in lilypond: test issue from python, lilypond, 12:22
  • Re: Manual page breaks, -Eluze, 10:44
  • Re: Issue 1901 in lilypond: Staves with StaffSymbol #'line-count = #1 produce "not a number"warnings and wrongly cropped images, lilypond, 09:56
  • Re: multiple fret-diagram-x markup commands and lilypond safe-mode, Julien Rioux, 08:51
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 08:48
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 08:41
  • Re: Manual page breaks, Phil Holmes, 06:38
  • Re: Issue 1584 in lilypond: removing parser DIGIT rule, lilypond, 06:14
  • Re: Issue 1248 in lilypond: GUB produces a random "unbound open-file" in regtests, lilypond, 06:10
  • Re: Issue 1584 in lilypond: removing parser DIGIT rule, lilypond, 06:05
  • Re: scheme engravers cause "Warnung: Attempting to remove nonexistinglistener.", Phil Holmes, 05:58
  • Issue 1902 in lilypond: scheme engravers cause "warning: Attempting to remove nonexisting listener.", lilypond, 05:57
  • Re: Staves with StaffSymbol #'line-count = #1 produce "not a number"warnings and wrongly cropped images, Phil Holmes, 05:53
  • Issue 1901 in lilypond: Staves with StaffSymbol #'line-count = #1 produce "not a number"warnings and wrongly cropped images, lilypond, 05:52
  • Issue 1900 in lilypond: Multiple fret-diagram-x markup commands and lilypond safe-mode, lilypond, 05:44
  • Re: multiple fret-diagram-x markup commands and lilypond safe-mode, Phil Holmes, 05:44
  • Re: Issue 1008 in lilypond: Some warning/error messages are not prefixed with 'warning:'/'error:', Reinhold Kainhofer, 05:02
  • Re: Issue 1008 in lilypond: Some warning/error messages are not prefixed with 'warning:'/'error:', address@hidden, 01:58
  • Re: Issue 1896 in lilypond: lost instrument names, lilypond, 01:52
  • Re: Failure of \RemoveEmptyStaves, Keith OHara, 01:23
  • Re: Issue 1899 in lilypond: test issue from python, lilypond, 00:02
• September 17, 2011
  • Issue 1899 in lilypond: test issue from python, lilypond, 23:58
  • Failure of \RemoveEmptyStaves, obscureed, 21:45
  • Re: Issue 1477 in lilypond: suppress output for expected warnings, lilypond, 21:09
  • Re: Issue 1008 in lilypond: Some warning/error messages are not prefixed with 'warning:'/'error:', lilypond, 20:08
  • Re: Issue 1892 in lilypond: lilypond.org can't build website, lilypond, 19:46
  • Re: Issue 1822 in lilypond: New short and long lyric ties., lilypond, 18:29
  • Re: Issue 1889 in lilypond: Lilypond-book: Improve options handling by processing everything in one place, lilypond, 18:24
  • Re: Issue 1887 in lilypond: Doc: adding doc strings for \...DashPattern and \harmonicBy..., lilypond, 17:44
  • Re: Issue 1898 in lilypond: Unifies mensural ligatures with blot-diameter, lilypond, 17:38
  • Re: Issue 1883 in lilypond: change longas similarly to how breves were changed, lilypond, 17:26
  • Issue 1898 in lilypond: Unifies mensural ligatures with blot-diameter, lilypond, 17:13
  • Issue 1897 in lilypond: Automatically set the eps backend in lilypond-book-preamble.ly, lilypond, 17:09
  • Re: Issue 1717 in lilypond: Possible incompatibility with Ghostscript 9 (was: Full notes and half notes are drawn filled), lilypond, 17:00
  • Re: Seting staff-staff-spacing in a \with block causes type check error, Neil Puttock, 14:57
  • Issue 1896 in lilypond: lost instrument names, lilypond, 14:48
  • Seting staff-staff-spacing in a \with block causes type check error, Reinhold Kainhofer, 14:45
  • Re: Setting Score.voltaSpannerDuration to shorten a volta bracket causes warning, Neil Puttock, 14:37
  • Setting Score.voltaSpannerDuration to shorten a volta bracket causes warning, Reinhold Kainhofer, 14:35
  • Issue 1895 in lilypond: GUB only has python 2.4, lilypond, 14:25
  • scheme engravers cause "Warnung: Attempting to remove nonexisting listener.", Reinhold Kainhofer, 14:17
  • Re: No pf dynamic marking in dynamic-scripts-init.ly, Janek Warchoł, 14:16
  • Re: Issue 1892 in lilypond: lilypond.org can't build website, lilypond, 12:54
  • Staves with StaffSymbol #'line-count = #1 produce "not a number" warnings and wrongly cropped images, Reinhold Kainhofer, 12:51
  • Re: Issue 155 in lilypond: \parenthesize does not take accidentals into account, lilypond, 12:50
  • Re: Issue 1839 in lilypond: Improves some parmesan noteheads., lilypond, 12:39
  • Re: multiple fret-diagram-x markup commands and lilypond safe-mode, Julien Rioux, 12:38
  • Re: multiple fret-diagram-x markup commands and lilypond safe-mode, Reinhold Kainhofer, 12:11
  • Re: multiple fret-diagram-x markup commands and lilypond safe-mode, Julien Rioux, 12:01
  • Re: multiple fret-diagram-x markup commands and lilypond safe-mode, Reinhold Kainhofer, 11:49
  • Re: multiple fret-diagram-x markup commands and lilypond safe-mode, Julien Rioux, 11:39
  • Re: Issue 1890 in lilypond: Compiler warnings in make on 64-bit systems, lilypond, 10:52
  • Re: multiple fret-diagram-x markup commands and lilypond safe-mode, Reinhold Kainhofer, 10:06
  • Re: No pf dynamic marking in dynamic-scripts-init.ly, Reinhold Kainhofer, 09:37
  • Re: No pf dynamic marking in dynamic-scripts-init.ly, Werner LEMBERG, 09:29
  • Re: No pf dynamic marking in dynamic-scripts-init.ly, Peekay Ex, 09:24
  • Re: Issue 1193 in lilypond: Enhancement: internal ledger lines, lilypond, 09:22
  • Re: Issue 1292 in lilypond: Enhancement: twelve-notation support, lilypond, 09:18
  • Re: Issue 1894 in lilypond: Prunes stem::length down to the bare minimum, lilypond, 09:10
  • Issue 1894 in lilypond: Prunes stem::length down to the bare minimum, lilypond, 09:05
  • Re: Issue 1893 in lilypond: Terminates outside_staff_callback early if a grob is outside a slur's X-extent, lilypond, 09:00
  • musicxml2ly: <movement-title> not converted in the presence of a non-empty <work-title>, Patrick Schmidt, 08:52
  • Re: Issue 1301 in lilypond: Strange collision of note and clef, lilypond, 08:50
  • Re: Issue 155 in lilypond: \parenthesize does not take accidentals into account, lilypond, 08:31
  • Re: Issue 1881 in lilypond: Multiple cyclic dependency errors for Beam/Stem, lilypond, 08:21
  • Re: Issue 1893 in lilypond: Terminates outside_staff_callback early if a grob is outside a slur's X-extent, lilypond, 07:56
  • Issue 1893 in lilypond: Terminates outside_staff_callback early if a grob is outside a slur's X-extent, lilypond, 07:14
  • Re: Issue 1301 in lilypond: Strange collision of note and clef, lilypond, 07:10
  • Re: Issue 155 in lilypond: \parenthesize does not take accidentals into account, lilypond, 04:32
  • Re: Issue 1598 in lilypond: Dynamics staff on lower piano staff shifts PianoStaff name, lilypond, 04:05
  • Re: Issue 1890 in lilypond: Compiler warnings in make, Keith OHara, 00:07
  • Re: Issue 1598 in lilypond: Dynamics staff on lower piano staff shifts PianoStaff name, lilypond, 00:02
• September 16, 2011
  • Re: Issue 155 in lilypond: \parenthesize does not take accidentals into account, lilypond, 23:31
  • Re: Issue 1839 in lilypond: Improves some parmesan noteheads., lilypond, 23:20
  • Re: Issue 1883 in lilypond: change longas similarly to how breves were changed, lilypond, 23:16
  • Re: Issue 1887 in lilypond: Doc: adding doc strings for \...DashPattern and \harmonicBy..., lilypond, 23:12
  • Re: Issue 1868 in lilypond: Loglevels in our python scripts (lilypond-book, musicxml2ly, convert-ly), lilypond, 18:22
  • Re: Issue 1854 in lilypond: Add some polyphonically directed grobs, lilypond, 17:59
  • Re: Issue 1854 in lilypond: Add some polyphonically directed grobs, lilypond, 17:55
  • Re: Issue 1891 in lilypond: New alist to replace special characters, lilypond, 17:49
  • Re: Issue 1891 in lilypond: New alist to replace special characters, lilypond, 17:35
  • Re: Issue 1891 in lilypond: New alist to replace special characters, lilypond, 17:31
  • Re: multiple fret-diagram-x markup commands and lilypond-book safe-mode, Julien Rioux, 17:06
  • Re: Issue 1881 in lilypond: Multiple cyclic dependency errors for Beam/Stem, address@hidden, 15:59
  • Issue 1892 in lilypond: lilypond.org can't build website, lilypond, 14:07
  • Re: Issue 448 in lilypond: KeyCancellation on a staff in a staff group causes ugly spacing problem, lilypond, 13:07
  • Re: Issue 186 in lilypond: tenuto-accent looks ugly (accent too big), lilypond, 13:03
  • Re: Issue 539 in lilypond: Accidentals not 'carried over' in an \alternative, lilypond, 12:59
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 12:55
  • Re: Issue 186 in lilypond: tenuto-accent looks ugly (accent too big), lilypond, 12:51
  • Re: Issue 141 in lilypond: Manual tuning of vertical ties required in some cases, lilypond, 12:47
  • Re: Issue 99 in lilypond: Make 'lyricsto' listen to barchecks, lilypond, 12:42
  • Re: Issue 1881 in lilypond: Multiple cyclic dependency errors for Beam/Stem, lilypond, 12:17
  • Re: Issue 127 in lilypond: 'Dead' contexts affect lyric placement for 'next' instance of musical expression, lilypond, 11:47
  • Re: Issue 707 in lilypond: Enhancement: Create an invisible Voice to assist Lyric alignment., lilypond, 11:35
  • Re: Issue 1890 in lilypond: Compiler warnings in make on 64-bit systems, lilypond, 11:27
  • Re: Issue 1890 in lilypond: Compiler warnings in make on 64-bit systems, lilypond, 10:00
  • Re: Issue 247 in lilypond: lyrics attached to Devnull are left-aligned instead of center-aligned, lilypond, 09:56
  • Re: Issue 315 in lilypond: Ancient porrectus should look like punctum, lilypond, 09:50
  • Re: Issue 461 in lilypond: LilyPond should accept a tie between notes which are enharmonically identical, lilypond, 09:39
  • Re: Issue 1890 in lilypond: Compiler warnings in make on 64-bit systems, lilypond, 08:30
  • Re: Issue 804 in lilypond: Code cleaning: checking types-conversion issues and other build warnings, lilypond, 08:26
  • Re: Issue 1890 in lilypond: Compiler warnings in make on 64-bit systems, lilypond, 08:22
  • Re: Issue 1890 in lilypond: Compiler warnings in make, lilypond, 08:18
  • Re: Issue 1868 in lilypond: Loglevels in our python scripts (lilypond-book, musicxml2ly, convert-ly), lilypond, 08:05
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 08:01
  • Issue 1891 in lilypond: New alist to replace special characters, lilypond, 07:57
  • Re: Issue 1890 in lilypond: Compiler warnings in make, lilypond, 07:53
  • Issue 1890 in lilypond: Compiler warnings in make, lilypond, 07:33
  • Re: Issue 1868 in lilypond: Loglevels in our python scripts (lilypond-book, musicxml2ly, convert-ly), lilypond, 04:51
• September 15, 2011
  • Re: Issue 1854 in lilypond: Add some polyphonically directed grobs, lilypond, 20:17
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 20:12
  • Issue 1889 in lilypond: Lilypond-book: Improve options handling by processing everything in one place, lilypond, 17:57
  • Re: Issue 1778 in lilypond: slashedGrace function (graces with slashed stems but no slur, e.g. when grace is tied) needs documenting, lilypond, 17:53
  • Re: Issue 1801 in lilypond: Clarify "\repeat unfold" in the documentation, lilypond, 17:43
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 17:26
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 17:15
  • Re: Issue 1839 in lilypond: Improves some parmesan noteheads., lilypond, 17:12
  • Re: Issue 1868 in lilypond: Loglevels in our python scripts (lilypond-book, musicxml2ly, convert-ly), lilypond, 17:02
  • Re: Issue 1822 in lilypond: New short and long lyric ties., lilypond, 16:57
  • Re: Issue 1868 in lilypond: Loglevels in our python scripts (lilypond-book, musicxml2ly, convert-ly), lilypond, 16:20
  • Re: Issue 380 in lilypond: Try to auto-detect cyclic references in header fields (was 'cycling markup reference segfaults'), lilypond, 16:13
  • Re: Issue 1888 in lilypond: Introduce a maximum depth for markup evaluation, lilypond, 16:08
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 15:52
  • Re: Issue 1839 in lilypond: Improves some parmesan noteheads., lilypond, 14:37
  • Re: Issue 1839 in lilypond: Improves some parmesan noteheads., lilypond, 13:13
  • Re: Issue 1731 in lilypond: LilyPond fails to install on Puppy Linux, lilypond, 13:07
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 12:24
  • Re: Issue 1529 in lilypond: filename changing should not trigger a regtests comparison, lilypond, 12:16
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 12:11
  • Re: Issue 1731 in lilypond: LilyPond fails to install on Puppy Linux, lilypond, 12:03
  • Re: Issue 1731 in lilypond: LilyPond fails to install on Puppy Linux, lilypond, 11:47
  • Re: Issue 380 in lilypond: Try to auto-detect cyclic references in header fields (was 'cycling markup reference segfaults'), lilypond, 10:53
  • Re: Issue 380 in lilypond: Try to auto-detect cyclic references in header fields (was 'cycling markup reference segfaults'), lilypond, 10:46
  • Issue 1888 in lilypond: Introduce a maximum depth for markup evaluation, lilypond, 10:42
  • Re: Issue 1292 in lilypond: Enhancement: twelve-notation support, lilypond, 10:01
  • Re: Issue 1743 in lilypond: lilypond-2.15.4-1.mingw.exe does not install PATH on Windows 7 SP1, lilypond, 09:41
  • Re: Issue 1866 in lilypond: Uses langdefs.py to create language list for create-weblinks-itexi.py, lilypond, 09:36
  • Re: Issue 1795 in lilypond: Improve handling of languages in doc and website build, lilypond, 09:28
  • Re: Issue 380 in lilypond: Try to auto-detect cyclic references in header fields (was 'cycling markup reference segfaults'), lilypond, 09:03
  • Re: Issue 456 in lilypond: \laissezVibrer in chords, lilypond, 06:32
  • Re: Issue 1876 in lilypond: MusicXML: fix case when some elements have a staff number, while others don't, lilypond, 06:29
  • Re: Issue 1529 in lilypond: filename changing should not trigger a regtests comparison, lilypond, 06:18
  • Re: Issue 1795 in lilypond: Improve handling of languages in doc and website build, lilypond, 05:57
  • Re: Issue 935 in lilypond: Enhancement: optional arguments in music functions, lilypond, 05:53
  • Re: Issue 1884 in lilypond: Warnings from simultaneous slurs with parallel music, lilypond, 05:45
  • Re: Issue 1884 in lilypond: Warnings from simultaneous slurs with parallel music, lilypond, 05:08
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 05:04
• September 14, 2011
  • Re: Issue 456 in lilypond: \laissezVibrer in chords, lilypond, 23:51
  • Re: Issue 1876 in lilypond: MusicXML: fix case when some elements have a staff number, while others don't, lilypond, 23:47
  • Re: Issue 1193 in lilypond: Enhancement: internal ledger lines, lilypond, 23:43
  • Re: Issue 1292 in lilypond: Enhancement: twelve-notation support, lilypond, 23:39
  • Re: Issue 1878 in lilypond: Add support for custom ledger positions, using two new staff-symbol properties, lilypond, 23:35
  • Re: Issue 1878 in lilypond: Add support for custom ledger positions, using two new staff-symbol properties, lilypond, 23:31
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 23:26
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 23:22
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 23:18
  • Re: Issue 1128 in lilypond: Text pedal mark not closed at music end, lilypond, 18:01
  • Re: Issue 1128 in lilypond: Text pedal mark not closed at music end, lilypond, 17:52
  • Re: Issue 1883 in lilypond: change longas similarly to how breves were changed, lilypond, 17:45
  • Re: Issue 1887 in lilypond: Doc: adding doc strings for \...DashPattern and \harmonicBy..., lilypond, 17:33
  • Re: Issue 1881 in lilypond: Multiple cyclic dependency errors for Beam/Stem, lilypond, 17:14
  • Re: Issue 1839 in lilypond: Improves some parmesan noteheads., lilypond, 17:09
  • Re: Issue 1884 in lilypond: Warnings from simultaneous slurs with parallel music, lilypond, 17:05
  • Re: Manual page breaks, Xavier Scheuer, 16:44
  • Re: Issue 1887 in lilypond: Doc: adding doc strings for \...DashPattern and \harmonicBy..., David Kastrup, 16:21
  • Re: Issue 1887 in lilypond: Doc: adding doc strings for \...DashPattern and \harmonicBy..., Neil Puttock, 15:57
  • Re: Issue 1887 in lilypond: Doc: adding doc strings for \...DashPattern and \harmonicBy..., Reinhold Kainhofer, 15:39
  • Re: Mac OS 10.5 ppc & Lilypond?, Stan Sanderson, 15:15
  • Issue 1887 in lilypond: Doc: adding doc strings for \...DashPattern and \harmonicBy..., lilypond, 14:42
  • Re: Issue 1128 in lilypond: Text pedal mark not closed at music end, lilypond, 14:27
  • Re: Issue 935 in lilypond: Enhancement: optional arguments in music functions, lilypond, 12:25
  • Re: Issue 380 in lilypond: Try to auto-detect cyclic references in header fields (was 'cycling markup reference segfaults'), lilypond, 12:01
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 10:20
  • Re: Issue 1886 in lilypond: Enhancement request: add a parameter/variable to control the spacing of lines in a score, Colin Campbell, 09:01
  • Re: Issue 1886 in lilypond: Enhancement request: add a parameter/variable to control the spacing of lines in a score, lilypond, 08:21
  • Re: Issue 1886 in lilypond: Enhancement request: add a parameter/variable to control the spacing of lines in a score, lilypond, 06:20
  • Re: Issue 1886 in lilypond: Enhancement request: add a parameter/variable to control the spacing of lines in a score, lilypond, 06:12
  • Re: Issue 1884 in lilypond: Warnings from simultaneous slurs with parallel music, lilypond, 06:08
  • Re: programming error: no solution found for Bezier intersection, Reinhold Kainhofer, 05:59
  • Re: Issue 1784 in lilypond: Adds epsilon to Bezier range calculations, lilypond, 05:34
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 03:30
  • Re: Issue 824 in lilypond: Enhancement: anchors in the music stream, lilypond, 03:15
  • No pf dynamic marking in dynamic-scripts-init.ly, Nick Payne, 02:18
  • Re: Issue 1886 in lilypond: Enhancement request: add a parameter/variable to control the spacing of lines in a score, lilypond, 00:57
  • Re: Mac OS 10.5 ppc & Lilypond?, Colin Campbell, 00:57
  • Issue 1886 in lilypond: Enhancement request: add a parameter/variable to control the spacing of lines in a score, lilypond, 00:53
  • Re: add a parameter/variable to control the spacing of lines in a score, Colin Campbell, 00:51
  • Issue 1885 in lilypond: Enhancement request: add a parameter/variable to control the spacing of lines in a score, lilypond, 00:49
  • Re: programming error: no solution found for Bezier intersection, Colin Campbell, 00:47
  • Re: partcombine regression? warns on slurs since 2.14.2, Colin Campbell, 00:43
  • Issue 1884 in lilypond: Warnings from simultaneous slurs in partcombine, lilypond, 00:40
• September 13, 2011
  • Re: programming error: no solution found for Bezier intersection, Nick Payne, 23:29
  • Re: Whole measure rest is too narrow (compared to whole measure note), Xavier Scheuer, 19:24
  • Re: add a parameter/variable to control the spacing of lines in a score, Xavier Scheuer, 18:12
  • Re: Issue 1882 in lilypond: parser.yy et al: turn \partial and \skip into music functions., lilypond, 18:07
  • Re: add a parameter/variable to control the spacing of lines in a score, Janek Warchoł, 17:54
  • add a parameter/variable to control the spacing of lines in a score, -Eluze, 17:38
  • partcombine regression? warns on slurs since 2.14.2, Jean-Baptiste Mazon, 17:35
  • Re: Mac OS 10.5 ppc & Lilypond?, Stan Sanderson, 12:30
  • Re: Mac OS 10.5 ppc & Lilypond?, Xavier Scheuer, 12:22
  • Re: Empty lyrics lead to inaccurate 'cannot find Voice' warning, Sietse Brouwer, 12:05
  • Re: Empty lyrics lead to inaccurate 'cannot find Voice' warning, Peekay Ex, 11:29
  • Re: Empty lyrics lead to inaccurate 'cannot find Voice' warning, Dmytro O. Redchuk, 11:00
  • Empty lyrics lead to inaccurate 'cannot find Voice' warning, Sietse Brouwer, 10:52
  • Re: Issue 1880 in lilypond: Presence of a bar number changes whole-measure rest width significantly, lilypond, 10:13
  • Re: Issue 1880 in lilypond: Presence of a bar number changes whole-measure rest width significantly, lilypond, 10:07
  • Re: Issue 1007 in lilypond: \fermataMarkup positioned too high (too low) if in \voice<X>, lilypond, 09:32
  • Re: Issue 1007 in lilypond: \fermataMarkup positioned too high (too low) if in \voice<X>, lilypond, 09:30
  • Re: Issue 1145 in lilypond: Enhancement: promote 'use-breve-rest from internal to user-settable, lilypond, 09:22
  • Re: Issue 1880 in lilypond: Presence of a bar number changes whole-measure rest width significantly, lilypond, 09:04
  • Re: Issue 1877 in lilypond: parser.yy et al: Turn \transpose into a music function, make other music functions use ly:pitch?, lilypond, 09:00
  • Re: Issue 1882 in lilypond: parser.yy et al: turn \partial and \skip into music functions., lilypond, 08:56
  • Re: Issue 1814 in lilypond: Breve with double-line "ears" can collide with accidentals and barlines, lilypond, 08:52
  • Re: Issue 1145 in lilypond: Enhancement: promote 'use-breve-rest from internal to user-settable, lilypond, 08:51
  • Re: Issue 1145 in lilypond: Enhancement: promote 'use-breve-rest from internal to user-settable, lilypond, 08:47
  • Re: Issue 1878 in lilypond: Add support for custom ledger positions, using two new staff-symbol properties, lilypond, 07:23
  • Re: Issue 1881 in lilypond: Multiple cyclic dependency errors for Beam/Stem, lilypond, 07:19
  • Re: Issue 1871 in lilypond: Several fixes for annotate-spacing, lilypond, 07:15
  • Re: Issue 1881 in lilypond: Multiple cyclic dependency errors for Beam/Stem, lilypond, 06:21
  • Re: Issue 1881 in lilypond: Multiple cyclic dependency errors for Beam/Stem, lilypond, 06:17
  • Re: Issue 1881 in lilypond: Multiple cyclic dependency errors for Beam/Stem, lilypond, 05:54
  • Re: Issue 1881 in lilypond: Multiple cyclic dependency errors for Beam/Stem, lilypond, 05:49
  • Re: Issue 1878 in lilypond: Add support for custom ledger positions, using two new staff-symbol properties, lilypond, 03:56
  • Re: Issue 1054 in lilypond: lilypond-book crashes trying to print localized help message (ubuntu), lilypond, 03:51
  • Re: Issue 1054 in lilypond: lilypond-book crashes trying to print localized help message (ubuntu), lilypond, 03:42
• September 12, 2011
  • Re: Issue 1871 in lilypond: Several fixes for annotate-spacing, lilypond, 23:32
  • Issue 1883 in lilypond: change longas similarly to how breves were changed, lilypond, 20:35
  • Re: accidentals in chordNames have diffferent vertical alignment depending on language - is this intentional?, Janek Warchoł, 20:20
  • Re: accidentals in chordNames have diffferent vertical alignment depending on language - is this intentional?, David Kastrup, 19:51
  • Re: accidentals in chordNames have diffferent vertical alignment depending on language - is this intentional?, Janek Warchoł, 19:48
  • Re: accidentals in chordNames have diffferent vertical alignment depending on language - is this intentional?, David Kastrup, 19:45
  • accidentals in chordNames have diffferent vertical alignment depending on language - is this intentional?, Janek Warchoł, 19:35
  • Re: Issue 1814 in lilypond: Breve with double-line "ears" can collide with accidentals and barlines, lilypond, 19:06
  • Re: Issue 1814 in lilypond: Breve with double-line "ears" can collide with accidentals and barlines, lilypond, 18:55
  • Re: Issue 1839 in lilypond: Improves some parmesan noteheads., lilypond, 18:51
  • Re: Issue 1854 in lilypond: Add some polyphonically directed grobs, lilypond, 18:46
  • Re: Issue 1603 in lilypond: Add some polyphonically directed grobs, lilypond, 18:42
  • Re: Issue 1603 in lilypond: Add some polyphonically directed grobs, lilypond, 18:32
  • Re: Issue 1786 in lilypond: New engraver for braces, lilypond, 18:27
  • Re: Issue 1839 in lilypond: Improves some parmesan noteheads., lilypond, 18:23
  • Re: Issue 1877 in lilypond: parser.yy et al: Turn \transpose into a music function, make other music functions use ly:pitch?, lilypond, 16:10
  • Re: Issue 1882 in lilypond: parser.yy et al: turn \partial and \skip into music functions., lilypond, 16:06
  • Re: Issue 146 in lilypond: bar counters for normal bars, lilypond, 15:46
  • Re: Issue 302 in lilypond: bad shape for tied notes in different clefs, lilypond, 13:37
  • Re: Issue 340 in lilypond: \harmonic only works inside chords, lilypond, 13:18
  • Re: Issue 239 in lilypond: Lyric does not have a hyphen if it is repeated in an alternate ending, lilypond, 13:11
  • Re: Issue 1825 in lilypond: convert-ly produces no output having run on up-to-date source, lilypond, 12:16
  • Re: Issue 1741 in lilypond: Tablature Bug when pitch is higher then beh in a quarter-tone string, lilypond, 12:16
  • Re: Issue 1787 in lilypond: Hide ends of barlines inside staff lines., lilypond, 12:08
  • Re: Issue 1816 in lilypond: Lilypond-book music runs off right side of the page, lilypond, 12:03
  • Re: Issue 1293 in lilypond: lilypond-book should use "quote" environment of LaTeX (instead of "quotation"), lilypond, 11:59
  • Issue 1882 in lilypond: parser.yy et al: turn \partial and \skip into music functions., lilypond, 11:39
  • Re: Issue 1839 in lilypond: Improves some parmesan noteheads., lilypond, 11:18
  • Re: Issue 1880 in lilypond: Presence of a bar number changes whole-measure rest width significantly, lilypond, 04:11
• September 11, 2011
  • Re: Issue 1843 in lilypond: Creates a Flag grob, lilypond, 17:40
  • Re: Issue 1881 in lilypond: Multiple cyclic dependency errors for Beam/Stem, lilypond, 17:34
  • Issue 1881 in lilypond: Multiple cyclic dependency errors for Beam/Stem, lilypond, 17:30
  • Re: Zeichenkodierung für Lilypond, Urs Liska, 17:21
  • Zeichenkodierung für Lilypond, Thomas, 17:00
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 13:20
  • Re: Issue 1741 in lilypond: Tablature Bug when pitch is higher then beh in a quarter-tone string, lilypond, 12:07
  • Re: Issue 1880 in lilypond: Presence of a bar number changes whole-measure rest width significantly, lilypond, 11:56
  • Re: Issue 1848 in lilypond: Lilypond-book: Give images 1mm less linewidth, lilypond, 11:46
  • Re: Issue 1849 in lilypond: Fix memleak: temporary skyline objects for systems were never deleted, lilypond, 11:42
  • Re: Issue 1584 in lilypond: removing parser DIGIT rule, lilypond, 11:38
  • Re: Issue 1584 in lilypond: removing parser DIGIT rule, lilypond, 11:32
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 10:57
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, Reinhold Kainhofer, 10:36
  • Re: Issue 1880 in lilypond: Presence of a bar number changes whole-measure rest width significantly, lilypond, 10:28
  • Re: Issue 1584 in lilypond: removing parser DIGIT rule, lilypond, 08:19
  • Re: Issue 1805 in lilypond: Ambitus engraver produces false warnings, lilypond, 07:30
  • Re: Issue 1805 in lilypond: Ambitus engraver produces false warnings, lilypond, 06:43
  • Re: Issue 905 in lilypond: LilyPond should accept UTF-8 BOM signatures even if preceded with other chars, lilypond, 06:36
  • Re: Issue 724 in lilypond: Staves that begin with an accidental should have more space before their first note., lilypond, 06:18
  • Issue 1880 in lilypond: Presence of a bar number changes whole-measure rest width significantly, lilypond, 06:14
  • Re: Presence of a bar number changes whole-measure rest widthsignificantly, Phil Holmes, 06:12
  • Issue 1879 in lilypond: Packed-spacing works improperly with Mensural_ligature_engraver and Vaticana_ligature_engraver, lilypond, 06:10
  • Re: Issue 723 in lilypond: wrong horizontal alignement of pedal brackets with a second inside a chord, lilypond, 06:06
  • Re: Issue 1529 in lilypond: filename changing should not trigger a regtests comparison, lilypond, 06:00
  • Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax, lilypond, 04:09
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 04:05
  • Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display, lilypond, 03:21
  • Re: Issue 1572 in lilypond: Change chord name separator and inversion separator, separately, lilypond, 03:16
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 03:08
• September 10, 2011
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 17:48
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 17:44
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 17:31
  • Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display, lilypond, 17:06
  • Re: Issue 1572 in lilypond: Change chord name separator and inversion separator, separately, lilypond, 17:02
  • Re: Issue 1193 in lilypond: Enhancement: internal ledger lines, lilypond, 16:46
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 16:12
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 15:22
  • Re: Issue 1193 in lilypond: Enhancement: internal ledger lines, lilypond, 15:04
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 15:00
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 14:56
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 14:48
  • Re: Issue 1193 in lilypond: Enhancement: internal ledger lines, lilypond, 14:21
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 14:16
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 14:07
  • Re: Issue 1193 in lilypond: Enhancement: internal ledger lines, lilypond, 11:58
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 11:35
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 11:20
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 10:32
  • Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2, lilypond, 10:04
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 09:56
  • Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display, lilypond, 09:52
  • Re: Issue 1228 in lilypond: \override RestCollision #'positioning-done = #merge-rests-on-positioning, lilypond, 09:48
  • Re: Issue 1572 in lilypond: Change chord name separator and inversion separator, separately, lilypond, 09:43
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 09:16
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 09:01
  • Re: Issue 1572 in lilypond: Change chord name separator and inversion separator, separately, lilypond, 08:49
  • Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display, lilypond, 08:45
  • Re: Issue 1741 in lilypond: Tablature Bug when pitch is higher then beh in a quarter-tone string, lilypond, 06:47
  • Re: Issue 380 in lilypond: cycling markup reference segfaults, lilypond, 06:43
  • Re: Issue 1193 in lilypond: Enhancement: internal ledger lines, lilypond, 06:39
  • Re: Issue 1878 in lilypond: Add support for custom ledger positions, using two new staff-symbol properties, lilypond, 06:35
  • Re: Issue 380 in lilypond: cycling markup reference segfaults, lilypond, 06:31
  • Re: Issue 1292 in lilypond: Enhancement: twelve-notation support, lilypond, 06:27
  • Re: Issue 1741 in lilypond: Tablature Bug when pitch is higher then beh in a quarter-tone string, lilypond, 06:23
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 06:19
  • Re: Issue 1876 in lilypond: MusicXML: fix case when some elements have a staff number, while others don't, lilypond, 06:15
  • Re: Issue 1877 in lilypond: parser.yy et al: Turn \transpose into a music function, make other music functions use ly:pitch?, lilypond, 06:11
  • Re: Issue 380 in lilypond: cycling markup reference segfaults, lilypond, 06:04
  • Re: Issue 456 in lilypond: \laissezVibrer in chords, lilypond, 05:56
  • Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 05:51
  • Re: Issue 1248 in lilypond: GUB produces a random "unbound open-file" in regtests, lilypond, 05:27
  • Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 05:22
• September 09, 2011
  • Re: Issue 1248 in lilypond: GUB produces a random "unbound open-file" in regtests, lilypond, 23:15
  • Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display, lilypond, 20:32
  • Re: Horizontal spacing depends on stem 'direction, Trevor Daniels, 17:52
  • Re: Issue 1875 in lilypond: tests for flower appear to miss instantiations of classes, lilypond, 17:07
  • Re: Issue 1691 in lilypond: Ugly bars in PDF documents, lilypond, 17:00
  • Re: musicxml2ly does not recognize clef elements containing number attributes, Patrick Schmidt, 16:22
  • Re: musicxml2ly does not recognize clef elements containing number attributes, Reinhold Kainhofer, 15:43
  • Re: Horizontal spacing depends on stem 'direction, Keith OHara, 15:33
  • musicxml2ly does not recognize clef elements containing number attributes, Patrick Schmidt, 15:31
  • Re: Issue 1815 in lilypond: lilypond-book fails on Windows, lilypond, 14:36
  • Re: Issue 1815 in lilypond: lilypond-book fails on Windows, lilypond, 14:16
  • Re: Issue 1007 in lilypond: \fermataMarkup positioned too high (too low) if in \voice<X>, lilypond, 14:12
  • Re: Issue 1054 in lilypond: lilypond-book crashes trying to print localized help message (ubuntu), lilypond, 14:08
  • Issue 1878 in lilypond: Add support for custom ledger positions, using two new staff-symbol properties, lilypond, 13:48
  • Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse, lilypond, 13:15
  • Re: Issue 1292 in lilypond: Enhancement: twelve-notation support, lilypond, 12:55
  • Re: Issue 380 in lilypond: cycling markup reference segfaults, lilypond, 12:51
  • Re: Issue 1292 in lilypond: Enhancement: twelve-notation support, lilypond, 12:28
  • Re: Issue 388 in lilypond: lilypond-book \betweenlilypondsystem does not apply to first system break if no header, lilypond, 11:56
  • Re: Issue 456 in lilypond: \laissezVibrer in chords, lilypond, 11:34
  • Issue 1877 in lilypond: parser.yy et al: Turn \transpose into a music function, make other music functions use ly:pitch?, lilypond, 10:19
  • Re: Issue 1798 in lilypond: Full measure rests take too little horizontal space compared to notes, lilypond, 09:53
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 08:48
  • Re: Issue 1815 in lilypond: lilypond-book fails on Windows, lilypond, 08:32
  • Re: Issue 1815 in lilypond: lilypond-book fails on Windows, lilypond, 08:14
  • Re: Issue 1815 in lilypond: lilypond-book fails on Windows, lilypond, 08:05
  • Re: Horizontal spacing depends on stem 'direction, Trevor Daniels, 04:34
  • Re: Horizontal spacing depends on stem 'direction, Janek Warchoł, 02:21
  • Re: Horizontal spacing depends on stem 'direction, Keith OHara, 00:37
• September 08, 2011
  • Re: Issue 1741 in lilypond: Tablature Bug when pitch is higher then beh in a quarter-tone string, lilypond, 20:37
  • Re: Horizontal spacing depends on stem 'direction, Graham Percival, 19:21
  • Horizontal spacing depends on stem 'direction, Trevor Daniels, 18:58
  • Re: Issue 1871 in lilypond: Several fixes for annotate-spacing, lilypond, 18:30
  • Re: Issue 1741 in lilypond: Tablature Bug when pitch is higher then beh in a quarter-tone string, lilypond, 18:17
  • Re: Issue 1798 in lilypond: Full measure rests do not occupy correct horizontal space., lilypond, 18:13
  • Issue 1876 in lilypond: MusicXML: fix case when some elements have a staff number, while others don't, lilypond, 18:09
  • Presence of a bar number changes whole-measure rest width significantly, Reinhold Kainhofer, 17:44
  • Re: Whole measure rest is too narrow (compared to whole measure note), Janek Warchoł, 17:20
  • Whole measure rest is too narrow (compared to whole measure note), Reinhold Kainhofer, 17:10
  • Re: Issue 1741 in lilypond: Tablature Bug when pitch is higher then beh in a quarter-tone string, lilypond, 16:00
  • Re: musicxml2ly does not recognize clef elements containing number attributes, Reinhold Kainhofer, 13:17
  • musicxml2ly does not recognize clef elements containing number attributes, Patrick Schmidt, 12:29
  • Re: Issue 1248 in lilypond: GUB produces a random "unbound open-file" in regtests, lilypond, 11:41
  • Re: Issue 1805 in lilypond: Ambitus engraver produces false warnings, lilypond, 11:37
  • Re: tests for flower appear to miss instantiations of classes, David Kastrup, 10:16
  • Re: tests for flower appear to miss instantiations of classes, Dmytro O. Redchuk, 08:56
  • Issue 1875 in lilypond: tests for flower appear to miss instantiations of classes, lilypond, 08:55
  • Re: tests for flower appear to miss instantiations of classes, David Kastrup, 08:45
  • Re: tests for flower appear to miss instantiations of classes, Reinhold Kainhofer, 08:42
  • tests for flower appear to miss instantiations of classes, David Kastrup, 08:13
  • Issue 1874 in lilypond: some stems are no longer transparent in the docs, lilypond, 04:50
  • Re: Issue 1833 in lilypond: Deprecate \fermataMarkup for full-bar rests., lilypond, 04:46
  • Re: Issue 1838 in lilypond: Make accidental styles available as context mods, lilypond, 04:42
  • Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding, lilypond, 04:38
  • Issue 1873 in lilypond: Added glyphs for Kievan Notation, lilypond, 03:09
  • Re: Issue 1871 in lilypond: Several fixes for annotate-spacing, lilypond, 03:02
• September 07, 2011
  • Re: Issue 1805 in lilypond: Ambitus engraver produces false warnings, lilypond, 23:22
  • Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse, lilypond, 23:18
  • Re: Issue 1866 in lilypond: Uses langdefs.py to create language list for create-weblinks-itexi.py, lilypond, 23:14
  • Re: Issue 1871 in lilypond: Several fixes for annotate-spacing, lilypond, 20:44
  • packed-spacing works improperly with Mensural_ligature_engraver and Vaticana_ligature_engraver, Marek Klein, 13:30
  • Re: Issue 1839 in lilypond: Improves some parmesan noteheads., lilypond, 12:35
  • Re: Issue 1839 in lilypond: Improves some parmesan noteheads., lilypond, 11:31
  • Re: Issue 1839 in lilypond: Improves some parmesan noteheads., lilypond, 11:14
  • Re: Issue 1236 in lilypond: CG+scripts should use $LILYPOND_GIT, lilypond, 07:52
  • Re: Issue 1821 in lilypond: GUB argument list too long, lilypond, 07:38
  • Re: Issue 1856 in lilypond: lots of extra space at beginning of bar, lilypond, 07:26
  • Re: Issue 1857 in lilypond: not robust solution in spacing-loose-grace-error.ly, lilypond, 07:22
  • Re: Issue 1859 in lilypond: let \contextStringTunings affect only current context., lilypond, 07:18
  • Re: Issue 1872 in lilypond: update the address of git-cl source files, lilypond, 07:14
  • Re: Issue 1864 in lilypond: lilypond.org does not use lilypond-git for source, lilypond, 06:17
  • Re: Issue 1858 in lilypond: unexplained increase in profile reports, lilypond, 06:12
• September 06, 2011
  • Re: Issue 1839 in lilypond: Improves some parmesan noteheads., lilypond, 13:44
  • Re: Issue 1854 in lilypond: Add some polyphonically directed grobs, lilypond, 13:40
  • Re: Issue 1854 in lilypond: Add some polyphonically directed grobs, lilypond, 13:10
  • Re: Issue 1854 in lilypond: Add some polyphonically directed grobs, lilypond, 13:06
  • Re: Issue 1841 in lilypond: Add some polyphonically directed grobs, lilypond, 12:31
  • Re: dynamics on chords with notehead to left and right of stem arewrongly aligned, Werner LEMBERG, 11:08
  • Re: Issue 1851 in lilypond: Do not issue rectstroke if blot diameter is 0.0, lilypond, 10:41
  • Re: Issue 509 in lilypond: collision nested tuplet numbers, lilypond, 09:11
  • Re: Issue 1814 in lilypond: Breve with double-line "ears" can collide with accidentals and barlines, lilypond, 08:21
  • Re: Issue 298 in lilypond: Ties do not appear when shortened because of an accidental, lilypond, 06:06
  • Re: Issue 1869 in lilypond: Parser.yy: rearrange to allow more lenient use of music arguments for music functions, lilypond, 04:42
  • Re: Issue 1814 in lilypond: Breve with double-line "ears" can collide with accidentals and barlines, lilypond, 04:35
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 04:31
  • Re: Issue 1869 in lilypond: Parser.yy: rearrange to allow more lenient use of music arguments for music functions, lilypond, 04:17
  • Re: Issue 723 in lilypond: wrong horizontal alignement of pedal brackets with a second inside a chord, lilypond, 04:08
  • Re: Issue 840 in lilypond: broken ties too short when time signature changes, lilypond, 04:04
  • Re: Issue 1785 in lilypond: Compressible space before the first note of a line ?, lilypond, 04:00
  • Re: Issue 724 in lilypond: Staves that begin with an accidental should have more space before their first note., lilypond, 03:56
  • Re: Issue 1742 in lilypond: print transposed guitar chords on piano sheets, lilypond, 03:52
  • Re: Issue 1872 in lilypond: update the address of git-cl source files, lilypond, 02:33
  • Re: Issue 1787 in lilypond: Hide ends of barlines inside staff lines., lilypond, 02:29
• September 05, 2011
  • Re: doubled accidental, Keith OHara, 23:43
  • Re: Issue 1833 in lilypond: Deprecate \fermataMarkup for full-bar rests., lilypond, 22:53
  • Re: Issue 1835 in lilypond: no learing manual pdf in dutch, lilypond, 22:52
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 17:11
  • Re: Issue 1867 in lilypond: Flush all ports after each file, flush stdout after displaying all options, lilypond, 17:10
  • Re: Issue 1248 in lilypond: GUB produces a random "unbound open-file" in regtests, lilypond, 17:07
  • Re: Issue 1248 in lilypond: GUB produces a random "unbound open-file" in regtests, lilypond, 17:06
  • Re: Issue 1248 in lilypond: GUB produces a random "unbound open-file" in regtests, lilypond, 16:55
  • Issue 1872 in lilypond: update the address of git-cl source files, lilypond, 16:51
  • Re: Issue 1742 in lilypond: print transposed guitar chords on piano sheets, lilypond, 16:47
  • Re: Issue 1869 in lilypond: Parser.yy: rearrange to allow more lenient use of music arguments for music functions, lilypond, 16:43
  • Re: Issue 1871 in lilypond: Several fixes for annotate-spacing, lilypond, 16:39
  • Re: Issue 1871 in lilypond: Several fixes for annotate-spacing, lilypond, 16:35
  • Issue 1871 in lilypond: Several fixes for annotate-spacing, lilypond, 16:31
  • Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond 2.14.x, lilypond, 16:27
  • Re: Issue 1742 in lilypond: print transposed guitar chords on piano sheets, lilypond, 16:23
  • Re: Issue 1248 in lilypond: GUB produces a random "unbound open-file" in regtests, lilypond, 16:19
  • Re: Issue 1867 in lilypond: Flush all ports after each file, flush stdout after displaying all options, lilypond, 16:15
  • Issue 1870 in lilypond: replace DIGIT token class with UNSIGNED, lilypond, 16:11
  • Re: Issue 1868 in lilypond: Loglevels in our python scripts (lilypond-book, musicxml2ly, convert-ly), lilypond, 16:07
  • Re: doubled accidental, David Bobroff, 16:05
  • Issue 1869 in lilypond: Parser.yy: rearrange to allow more lenient use of music arguments for music functions, lilypond, 16:03
  • doubled accidental, Maxim Gawrilow, 16:00
  • Re: Issue 1867 in lilypond: Flush all ports after each file, flush stdout after displaying all options, lilypond, 15:59
  • Re: Issue 1867 in lilypond: Flush all ports after each file, flush stdout after displaying all options, lilypond, 15:55
  • Issue 1868 in lilypond: Loglevels in our python scripts (lilypond-book, musicxml2ly, convert-ly), lilypond, 15:51
  • Re: Issue 1193 in lilypond: [PATCH] Enhancement: internal ledger lines, lilypond, 15:47
  • Re: Issue 1833 in lilypond: Deprecate \fermataMarkup for full-bar rests., lilypond, 15:45
  • Re: Issue 1833 in lilypond: Deprecate \fermataMarkup for full-bar rests., lilypond, 15:43
  • Issue 1867 in lilypond: Flush all ports after each file, flush stdout after displaying all options, lilypond, 15:39
  • Re: Issue 1193 in lilypond: [PATCH] Enhancement: internal ledger lines, lilypond, 15:35
  • Re: Issue 1838 in lilypond: Make accidental styles available as context mods, lilypond, 15:27
  • Re: Issue 1405 in lilypond: Web: website Google search-bar should allow to search the website., lilypond, 15:23
  • Re: Issue 1663 in lilypond: Images missing on web site, lilypond, 15:19
  • Issue 1866 in lilypond: Uses langdefs.py to create language list for create-weblinks-itexi.py, lilypond, 15:15
  • Re: Issue 1775 in lilypond: LSR: add broken- and unbroken slur shaping function, lilypond, 15:02
  • Re: Issue 1742 in lilypond: print transposed guitar chords on piano sheets, lilypond, 14:40
  • Re: Issue 1864 in lilypond: lilypond.org does not use lilypond-git for source, lilypond, 14:30
  • Re: Issue 1859 in lilypond: let \contextStringTunings affect only current context., Carl Sorensen, 14:01
  • Re: Issue 1864 in lilypond: lilypond.org does not use lilypond-git for source, lilypond, 13:56
  • Re: Issue 1775 in lilypond: LSR: add broken- and unbroken slur shaping function, lilypond, 12:30
  • Re: Issue 1742 in lilypond: print transposed guitar chords on piano sheets, lilypond, 11:42
  • Re: Issue 1742 in lilypond: print transposed guitar chords on piano sheets, lilypond, 11:23
  • Re: dynamics on chords with notehead to left and right of stem arewrongly aligned, Trevor Daniels, 08:24
  • Re: \tempo indication not printed, Dmytro O. Redchuk, 04:34
  • Issue 1865 in lilypond: tempo indication can not be attached to spacers, lilypond, 04:33
  • Re: \tempo indication not printed, Reinhold Kainhofer, 04:02
  • Re: \tempo indication not printed, Dmytro O. Redchuk, 03:42
• September 04, 2011
  • dynamics on chords with notehead to left and right of stem are wrongly aligned, Reinhold Kainhofer, 19:45
  • Re: Issue 1856 in lilypond: lots of extra space at beginning of bar, lilypond, 15:38
  • Re: Issue 1826 in lilypond: Guile 2.0 compat: `conditional-circle-markup' definition needs to be relocated, lilypond, 12:45
  • Re: Explicit fingering direction (^3) has no effect if Fingering#'direction is set, -Eluze, 11:58
  • Re: Explicit fingering direction (^3) has no effect if Fingering #'direction is set, David Kastrup, 11:09
  • Re: Explicit fingering direction (^3) has no effect if Fingering#'direction is set, -Eluze, 11:09
  • Re: Issue 1775 in lilypond: LSR: add broken- and unbroken slur shaping function, lilypond, 11:06
  • Re: Issue 1859 in lilypond: let \contextStringTunings affect only current context., David Kastrup, 11:04
  • Issue 1864 in lilypond: lilypond.org does not use lilypond-git for source, lilypond, 10:53
  • Re: Issue 1775 in lilypond: LSR: add broken- and unbroken slur shaping function, lilypond, 10:28
  • Re: Explicit fingering direction (^3) has no effect if Fingering#'direction is set, Phil Holmes, 06:15
  • Issue 1863 in lilypond: Explicit fingering direction (^3) has no effect if Fingering#'direction is set, lilypond, 06:10
  • Re: Misleading clef placement at the end of a volta., Phil Holmes, 06:05
  • Issue 1862 in lilypond: Misleading clef placement at the end of a volta, lilypond, 06:02
  • Issue 1861 in lilypond: DynamicText attached to spacer rest not correctly aligned, lilypond, 05:57
  • Re: Lyrics alignment to notes, Phil Holmes, 05:51
  • Re: Issue 333 in lilypond: Lyrics delayed by one note, lilypond, 05:51
  • Re: Issue 1775 in lilypond: LSR: add broken- and unbroken slur shaping function, lilypond, 05:40
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 05:33
  • Re: Explicit fingering direction (^3) has no effect if Fingering #'direction is set, Reinhold Kainhofer, 03:07
  • Re: Explicit fingering direction (^3) has no effect if Fingering #'direction is set, -Eluze, 02:50
• September 03, 2011
  • Re: Issue 1805 in lilypond: Ambitus engraver produces false warnings, lilypond, 20:10
  • Re: Install problem Lilypond 2.12.3 on Linux Ubuntu 11.04, Peekay Ex, 18:39
  • Explicit fingering direction (^3) has no effect if Fingering #'direction is set, Reinhold Kainhofer, 18:11
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 17:10
  • Re: Issue 1295 in lilypond: Support for Mac OSX 10.3.9 "Panther" is broken, Reinhold Kainhofer, 16:42
  • Re: Issue 1858 in lilypond: unexplained increase in profile reports, Han-Wen Nienhuys, 16:39
  • Re: Install problem Lilypond 2.12.3 on Linux Ubuntu 11.04, Graham Percival, 13:54
  • Re: Issue 1295 in lilypond: Support for Mac OSX 10.3.9 "Panther" is broken, Dmytro O. Redchuk, 13:28
  • Install problem Lilypond 2.12.3 on Linux Ubuntu 11.04, Mark Chapman, 12:26
  • Re: Issue 1858 in lilypond: unexplained increase in profile reports, lilypond, 11:05
  • Re: Issue 1858 in lilypond: unexplained increase in profile reports, lilypond, 10:49
  • Re: Issue 1595 in lilypond: lilypond-book papersize gives margin warnings, lilypond, 10:00
  • Re: Issue 1805 in lilypond: Ambitus engraver produces false warnings, lilypond, 08:05
  • Re: Issue 1638 in lilypond: lilypond-book [quote] hard-codes 5\in, lilypond, 06:58
  • Re: Issue 1293 in lilypond: lilypond-book should use "quote" environment of LaTeX (instead of "quotation"), lilypond, 06:54
  • Re: Issue 1825 in lilypond: convert-ly produces no output having run on up-to-date source, lilypond, 06:47
  • Re: Issue 1595 in lilypond: lilypond-book papersize gives margin warnings, lilypond, 06:21
  • Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding, lilypond, 06:11
  • Re: Issue 1858 in lilypond: unexplained increase in profile reports, lilypond, 05:56
  • Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding, lilypond, 05:12
  • Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding, lilypond, 02:59
• September 02, 2011
  • Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding, lilypond, 19:00
  • Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding, lilypond, 18:55
  • Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse, lilypond, 18:51
  • Re: Issue 1856 in lilypond: lots of extra space at beginning of bar, lilypond, 18:42
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 17:50
  • Re: Issue 1295 in lilypond: Support for Mac OSX 10.3.9 "Panther" is broken, lilypond, 17:42
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 15:44
  • Re: Issue 1852 in lilypond: manuals needs more explicit dependencies, lilypond, 15:40
  • Re: Issue 1635 in lilypond: clean up misleading warnings inwebsitebuild, Trevor Daniels, 14:39
  • Re: Issue 1859 in lilypond: let \contextStringTunings affect only current context., lilypond, 14:05
  • Misleading clef placement at the end of a volta., Bertrand Bordage, 13:59
  • Re: Issue 1859 in lilypond: let \contextStringTunings affect only current context., lilypond, 13:58
  • Re: Issue 1858 in lilypond: unexplained increase in profile reports, lilypond, 13:48
  • Re: Issue 1844 in lilypond: Changes variable names in include/beam-scoring-problem.hh and beam-quanting.cc, lilypond, 13:31
  • Re: Issue 1635 in lilypond: clean up misleading warnings in websitebuild, Trevor Daniels, 11:25
  • Re: Issue 1295 in lilypond: Support for Mac OSX 10.3.9 "Panther" is broken, lilypond, 09:48
  • Re: Issue 1775 in lilypond: LSR: add broken- and unbroken slur shaping function, lilypond, 08:04
  • Re: Issue 1858 in lilypond: unexplained increase in profile reports, lilypond, 07:24
• September 01, 2011
  • Re: Issue 1775 in lilypond: LSR: add broken- and unbroken slur shaping function, lilypond, 23:46
  • Re: Issue 1838 in lilypond: Make accidental styles available as context mods, lilypond, 23:05
  • Re: Issue 1833 in lilypond: Deprecate \fermataMarkup for full-bar rests., lilypond, 23:01
  • Re: Issue 1814 in lilypond: Breve with double-line "ears" can collide with accidentals and barlines, lilypond, 22:57
  • Re: Issue 1787 in lilypond: Hide ends of barlines inside staff lines., lilypond, 22:53
  • Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented, lilypond, 22:48
  • Re: Issue 1742 in lilypond: print transposed guitar chords on piano sheets, lilypond, 22:44
  • Re: Issue 1854 in lilypond: Add some polyphonically directed grobs, lilypond, 18:21
  • Re: Issue 1293 in lilypond: lilypond-book should use "quote" environment of LaTeX (instead of "quotation"), lilypond, 17:01
  • Re: Issue 1821 in lilypond: GUB argument list too long, lilypond, 12:31
  • Re: \tempo indication not printed, Valentin Villenave, 11:19
  • Re: Issue 1293 in lilypond: lilypond-book should use "quote" environment of LaTeX (instead of "quotation"), lilypond, 10:59
  • Re: \tempo indication not printed, Reinhold Kainhofer, 10:06
  • DynamicText attached to spacer rest not correctly aligned, Xavier Scheuer, 09:32
  • Re: Issue 1849 in lilypond: Fix memleak: temporary skyline objects for systems were never deleted, lilypond, 09:25
  • Re: Issue 1529 in lilypond: filename changing should not trigger a regtests comparison, lilypond, 09:23
  • Re: Issue 1849 in lilypond: Fix memleak: temporary skyline objects for systems were never deleted, lilypond, 09:14
  • Re: Issue 1529 in lilypond: filename changing should not trigger a regtests comparison, lilypond, 09:10
  • Re: Issue 1295 in lilypond: Support for Mac OSX 10.3.9 "Panther" is broken, lilypond, 08:55
  • Re: \tempo indication not printed, Valentin Villenave, 08:45
  • Re: \tempo indication not printed, Neil Puttock, 08:26
  • Re: \tempo indication not printed, Francisco Vila, 08:22
  • Re: Issue 40 in lilypond: collision glissando accidental (includes workaround), lilypond, 08:20
  • Issue 1860 in lilypond: Invisible glissando before accented note (see issue 40), lilypond, 08:16
  • Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal), lilypond, 08:11
  • Re: Issue 905 in lilypond: LilyPond should accept UTF-8 BOM signatures even if preceded with other chars, lilypond, 08:07
  • \tempo indication not printed, Valentin Villenave, 08:07
  • Re: Issue 472 in lilypond: collision rest + (accidental/notehead) with beaming, lilypond, 08:03
  • Re: Issue 905 in lilypond: LilyPond should accept UTF-8 BOM signatures even if preceded with other chars, lilypond, 08:02
  • Re: Issue 620 in lilypond: It should be possible to specify more specific spanner bounds., lilypond, 08:01
  • Re: Issue 770 in lilypond: Lyrics behave differently when associated to a Voice-derived context, lilypond, 08:01
  • Re: Issue 589 in lilypond: Odd spacing with polyphonic dotted notes, lilypond, 08:01
  • Re: Issue 982 in lilypond: web big-html and pdf look bad, lilypond, 07:43
  • Re: Issue 1859 in lilypond: let \contextStringTunings affect only current context., lilypond, 07:39
  • Re: Issue 1840 in lilypond: Fixes figuredBassCenterContinuations., lilypond, 06:47
  • Re: Issue 1074 in lilypond: -q quiet mode for lilypond, lilypond, 06:31
  • Re: Issue 1848 in lilypond: Lilypond-book: Give images 1mm less linewidth, lilypond, 05:43
  • Re: Issue 1114 in lilypond: A later note's stem can be to the left of an earlier note's stem, lilypond, 05:37
  • Re: Issue 1174 in lilypond: in crossed voices dot may collide with notehead, lilypond, 05:33
  • Re: Issue 1214 in lilypond: Cue notes to music that creates a sub-voice does not work, lilypond, 05:29
  • Re: Issue 1235 in lilypond: Accidental overlays stem, lilypond, 05:25
  • Re: Issue 1286 in lilypond: Page-breaking doesn't work properly when the last bar is incomplete, lilypond, 05:21
  • Re: Issue 1300 in lilypond: Badly placed cross-staff beam, similar to Issue 506, lilypond, 05:17
  • Re: Issue 1765 in lilypond: Clean up regtest mozart-hrn-3, lilypond, 05:13
  • Re: Issue 1328 in lilypond: Slurs collides with fermata, lilypond, 05:09
  • Re: Issue 1393 in lilypond: HTML docs: @multitable uses too much space, lilypond, 05:05
  • Re: Issue 1480 in lilypond: optical spacing is removed in tightly packed music, lilypond, 05:01
  • Re: Issue 1554 in lilypond: update midi2ly version number, lilypond, 04:57
  • Re: Issue 1765 in lilypond: Clean up regtest mozart-hrn-3, lilypond, 04:53
  • Re: Issue 1604 in lilypond: MultiMeasureRest staff position 0 is taken as staff position 2, lilypond, 04:53
  • Re: Issue 1628 in lilypond: Fingerings collide with slurs when used in <>, lilypond, 04:49
  • Re: Issue 1857 in lilypond: not robust solution in spacing-loose-grace-error.ly, lilypond, 03:58
  • Re: Issue 1699 in lilypond: Automated numbering for footnotes, lilypond, 03:56
  • Re: Issue 1688 in lilypond: New half-closed hihat symbol for drum mode, lilypond, 03:55
  • Issue 1859 in lilypond: let \contextStringTunings affect only current context., lilypond, 03:55
  • Re: Issue 1644 in lilypond: get_working_directory () issue?, lilypond, 03:55
  • Re: Issue 1752 in lilypond: redesigning G clef in our Feta font, lilypond, 03:36
  • Re: Issue 1765 in lilypond: Clean up regtest mozart-hrn-3, lilypond, 03:32
  • Re: Issue 1785 in lilypond: Compressible space before the first note of a line ?, lilypond, 03:28
  • Re: Issue 1804 in lilypond: LSR: description of tie-configuration in engraving-ties-manually.ly is wrong, lilypond, 03:24
  • Re: Issue 1847 in lilypond: Lilypond-book: Get rid of lilyquote option, use quote instead, lilypond, 03:20
  • Re: Issue 1848 in lilypond: Lilypond-book: Give images 1mm less linewidth, lilypond, 03:16
  • Re: Issue 1848 in lilypond: Lilypond-book: Give images 1mm less linewidth, lilypond, 02:05
  • Re: Issue 1857 in lilypond: not robust solution in spacing-loose-grace-error.ly, lilypond, 01:44

---

[Prev Period]

[Next Period]

---

Mail converted by MHonArc