Re: Issue 1349 in lilypond: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used.

Updates: Labels: Patch-review Comment #15 on issue 1349 by ianhuli...@gmail.com: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used. http://code.google.com/p/lilypond/issues/detail?id=1349 Disentangled load order issues from other Guile V2 issues. Runnin

Re: Issue 1812 in lilypond: Many things in Chapter 5 of the NR need a complete rewrite

Comment #3 on issue 1812 by tdaniels...@googlemail.com: Many things in Chapter 5 of the NR need a complete rewrite http://code.google.com/p/lilypond/issues/detail?id=1812 Good point, Neil. This use of \accepts would be a useful example to go into the revised 5.1.7.

Re: Issue 1812 in lilypond: Many things in Chapter 5 of the NR need a complete rewrite

Comment #2 on issue 1812 by n.putt...@gmail.com: Many things in Chapter 5 of the NR need a complete rewrite http://code.google.com/p/lilypond/issues/detail?id=1812 \accepts can be useful without creating new contexts; for example see this thread from a few days ago where a user wanted to pl

Re: Issue 1812 in lilypond: Many things in Chapter 5 of the NR need a complete rewrite

Updates: Owner: pkx1...@gmail.com Labels: Patch-review Comment #1 on issue 1812 by pkx1...@gmail.com: Many things in Chapter 5 of the NR need a complete rewrite http://code.google.com/p/lilypond/issues/detail?id=1812 Removed 5.1.7 http://codereview.appspot.com/4839061 _

Re: Issue 1793 in lilypond: Doc: change how lyrics in PianoStaff is documented

Comment #4 on issue 1793 by pkx1...@gmail.com: Doc: change how lyrics in PianoStaff is documented http://code.google.com/p/lilypond/issues/detail?id=1793 created issue 1812 for the '...pretty well all of the existing 5.1.7 could just be deleted.' part of the last comment in case others migh

Issue 1812 in lilypond: Many things in Chapter 5 of the NR need a complete rewrite

Status: New Owner: Labels: Type-Documentation Priority-Low New issue 1812 by pkx1...@gmail.com: Many things in Chapter 5 of the NR need a complete rewrite http://code.google.com/p/lilypond/issues/detail?id=1812 From Trevor D (came out of issue 1793) --snip-- Many things in Chapter 5 of

Re: Issue 1811 in lilypond: Revise warning re cueDuring font size

Comment #3 on issue 1811 by pkx1...@gmail.com: Revise warning re cueDuring font size http://code.google.com/p/lilypond/issues/detail?id=1811 Second Draft up. james ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/l

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

Comment #10 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 I'm not getting this failure when I compile the example above. Sorry, I was testing the original snippet. _

Re: Issue 804 in lilypond: Code cleaning: checking types-conversion issues and other build warnings

Updates: Labels: -Patch-new Patch-review Comment #6 on issue 804 by pkx1...@gmail.com: Code cleaning: checking types-conversion issues and other build warnings http://code.google.com/p/lilypond/issues/detail?id=804 Passes make but there are some reg test differences - see attached At

Re: Issue 472 in lilypond: collision rest + (accidental/notehead) with beaming

Updates: Labels: -Patch-new Comment #4 on issue 472 by pkx1...@gmail.com: collision rest + (accidental/notehead) with beaming http://code.google.com/p/lilypond/issues/detail?id=472 Passes make and reg tests ___ bug-lilypond mailing list bu

Re: Issue 1808 in lilypond: [PATCH] Implement MusicXML files in lilypond-book

Updates: Owner: reinhold...@gmail.com Comment #1 on issue 1808 by reinhold...@gmail.com: [PATCH] Implement MusicXML files in lilypond-book http://code.google.com/p/lilypond/issues/detail?id=1808 (No comment was entered for this change.) __

Re: Issue 1328 in lilypond: Slurs collides with fermata

Updates: Labels: -Patch-new Comment #2 on issue 1328 by pkx1...@gmail.com: Slurs collides with fermata http://code.google.com/p/lilypond/issues/detail?id=1328 Passes make some reg test differences, nothing noticeable although interestingly there is a difference in input/regression/sl

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

Updates: Labels: -Patch-review Patch-needs_work Comment #28 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 Needs rebasing. ___ bug-lilypond mailing li

Re: Issue 472 in lilypond: collision rest + (accidental/notehead) with beaming

Updates: Labels: Patch-new Patch-review Comment #3 on issue 472 by mts...@gmail.com: collision rest + (accidental/notehead) with beaming http://code.google.com/p/lilypond/issues/detail?id=472 http://codereview.appspot.com/4860043 ___ bug-l

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

Comment #25 on issue 1691 by percival.music.ca: Ugly bars in PDF documents http://code.google.com/p/lilypond/issues/detail?id=1691 what happens if somebody wants to make a document with usletter ? ok, it's a totally stupid size of paper, but that's the only type I can buy in Canada in regul

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

Comment #24 on issue 1691 by philehol...@googlemail.com: Ugly bars in PDF documents http://code.google.com/p/lilypond/issues/detail?id=1691 I honestly think the simplest and best answer is just to hard code the 155mm value - it's just a magic figure that we happen to know works, so trying

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

Comment #22 on issue 1691 by philehol...@googlemail.com: Ugly bars in PDF documents http://code.google.com/p/lilypond/issues/detail?id=1691 I'll not be learning scheme just to fix this. If someone could explain it, it would be a help. I don't believe the line: override[LINE_WIDTH] = '5\

Re: Issue 1328 in lilypond: Slurs collides with fermata

Updates: Labels: Patch-new Patch-review Comment #1 on issue 1328 by mts...@gmail.com: Slurs collides with fermata http://code.google.com/p/lilypond/issues/detail?id=1328 http://codereview.appspot.com/4860042/ ___ bug-lilypond mailing list bug