Lilydev remix iso - where

The lilynet website still seems to be under construction. In particular the lilydev remix iso is not available from the link in the CG. (I guess this should be a critical bug under the proposed new classification scheme.) I'd actually like to obtain it, as I need to reinstall my ubuntu syst

Re: Issue 1792 in lilypond: dot-notehead collision

Comment #5 on issue 1792 by k-ohara5...@oco.net: dot-notehead collision http://code.google.com/p/lilypond/issues/detail?id=1792 With the fix above for this issue, the behavior matches the documentation. "prefer-dotted-right (boolean) : For note collisions, prefer to shift dotted up-note to t

Re: Issue 1691 in lilypond: Ugly bars in PDF documents

Comment #35 on issue 1691 by philehol...@googlemail.com: Ugly bars in PDF documents http://code.google.com/p/lilypond/issues/detail?id=1691 I know this very well. My example pointed it out to you. If you want to deliberately avoid the instructions in the CG, then you'll get crap output.

Re: Issue 1691 in lilypond: Ugly bars in PDF documents

Comment #34 on issue 1691 by percival.music.ca: Ugly bars in PDF documents http://code.google.com/p/lilypond/issues/detail?id=1691 The 2.05 is completely irrelevant -- it's not used at all in this example, which still has the overflow black bars. Without using any bar numbers or instrument

lilypond-book music runs off right side of the page

The below example demonstrates that lilypond-book cannot estimate the line width correctly; music runs off the right-hand side of the page. Please add as Type-script, Priority-high, and with a label:maintainability. Also note that this bug has NOTHING to do with the documentation. It's a perfectl

Re: Issue 1815 in lilypond: lilypond-book fails on Windows

Comment #1 on issue 1815 by uwestoeh...@gtempaccount.com: lilypond-book fails on Windows http://code.google.com/p/lilypond/issues/detail?id=1815 A colleague of mine working under Linux does not see the bug, so my guess that the (back)slash issue might trigger this can be the bug. ___

Issue 1815 in lilypond: lilypond-book fails on Windows

Status: New Owner: New issue 1815 by uwestoeh...@gtempaccount.com: lilypond-book fails on Windows http://code.google.com/p/lilypond/issues/detail?id=1815 I'm using LilyPond 2.14.2 and Python 2.7.2 in Windows XP. Attached is my lytex example file. If I execute the command D:\LyXSVN>pyth

Re: Issue 1393 in lilypond: HTML docs: @multitable uses too much space

Updates: Owner: reinhold...@gmail.com Comment #6 on issue 1393 by reinhold...@gmail.com: HTML docs: @multitable uses too much space http://code.google.com/p/lilypond/issues/detail?id=1393 (No comment was entered for this change.) ___ bug-l

Re: Issue 1393 in lilypond: HTML docs: @multitable uses too much space

Updates: Status: Started Labels: Patch-new Comment #5 on issue 1393 by reinhold...@gmail.com: HTML docs: @multitable uses too much space http://code.google.com/p/lilypond/issues/detail?id=1393 Patch is up for review at http://codereview.appspot.com/4891044/ _

Re: Issue 1767 in lilypond: Feta font - change breve vertical lines

Updates: Labels: fixed_2_15_9 Comment #16 on issue 1767 by n.putt...@gmail.com: Feta font - change breve vertical lines http://code.google.com/p/lilypond/issues/detail?id=1767 (No comment was entered for this change.) ___ bug-lilypond mail

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

Updates: Labels: -Patch-needs_work fixed_2_15_9 Comment #30 on issue 163 by n.putt...@gmail.com: huge (ugly) slur (both phrasing and normal) http://code.google.com/p/lilypond/issues/detail?id=163 (No comment was entered for this change.) _

Re: Issue 1585 in lilypond: LilyPond segfaults on beams with headless stencils

Updates: Labels: fixed_2_13_58 Comment #11 on issue 1585 by n.putt...@gmail.com: LilyPond segfaults on beams with headless stencils http://code.google.com/p/lilypond/issues/detail?id=1585 (No comment was entered for this change.) ___ bug-l

Re: Issue 1673 in lilypond: patch Allows glissandi to span multiple lines.

Updates: Labels: -Patch-review fixed_2_15_5 Comment #11 on issue 1673 by n.putt...@gmail.com: patch Allows glissandi to span multiple lines. http://code.google.com/p/lilypond/issues/detail?id=1673 (No comment was entered for this change.)

Re: Issue 1604 in lilypond: MultiMeasureRest staff position 0 is taken as staff position 2

Updates: Owner: mts...@gmail.com Labels: -Patch-review fixed_2_15_9 Comment #11 on issue 1604 by n.putt...@gmail.com: MultiMeasureRest staff position 0 is taken as staff position 2 http://code.google.com/p/lilypond/issues/detail?id=1604 (No comment was entered for this change.

Re: Issue 1792 in lilypond: dot-notehead collision

Comment #4 on issue 1792 by n.putt...@gmail.com: dot-notehead collision http://code.google.com/p/lilypond/issues/detail?id=1792 Did I miss the countdown for this? Why does the second beat still look bad even with prefer-dotted-right = #t? The lower voice's dot looks as if it's attached to th

Re: Issue 1214 in lilypond: Cue notes to music that creates a sub-voice does not work

Updates: Status: Fixed Labels: -Patch-review fixed_2_15_9 Comment #11 on issue 1214 by reinhold...@gmail.com: Cue notes to music that creates a sub-voice does not work http://code.google.com/p/lilypond/issues/detail?id=1214 Pushed with commit 1b11dc0cb1bec0e353773aac6b8afba903

Re: Issue 1691 in lilypond: Ugly bars in PDF documents

Comment #33 on issue 1691 by philehol...@googlemail.com: Ugly bars in PDF documents http://code.google.com/p/lilypond/issues/detail?id=1691 I can break the docs in a number of ways, including using incorrect syntax and by putting long unbreakable lines in. However, we tell people not to