Re: beam of grace notes overlap with beam of side notes

Am 03.09.2010 05:17, schrieb Antheo: Hi, I have 2 16th graces notes which beam overlap with the 8th notes in between. \version 2.12.3 { \relative c'' { g8[ \grace {b16 [a16]} b8] } } http://old.nabble.com/file/p29610891/Screen%2Bshot%2B2010-09-02%2Bat%2B11.11.04%2BPM.png I know i could use

Issue 1247 in lilypond: Use new modules provided by Guile V2 - Part 1 (ice-9 curried-definitions)

Status: Accepted Owner: ianhuli...@gmail.com CC: hanwenn, pnorcks, n.puttock, Carl.D.Sorensen Labels: Type-Enhancement Priority-High Maintainability New issue 1247 by ianhuli...@gmail.com: Use new modules provided by Guile V2 - Part 1 (ice-9 curried-definitions)

Re: Issue 1206 in lilypond: all regtests should have a description

Comment #1 on issue 1206 by percival.music.ca: all regtests should have a description http://code.google.com/p/lilypond/issues/detail?id=1206 Fixed in b95627d243f33f9c580a32ffa99cca297b631e0f and 36ceb05d8e5888b8d50888acbdd2dc341215d9fc ___

Re: Issue 1206 in lilypond: all regtests should have a description

Updates: Labels: fixed_2_13_32 Comment #2 on issue 1206 by percival.music.ca: all regtests should have a description http://code.google.com/p/lilypond/issues/detail?id=1206 to verify, run the grep on input/regression. ___ bug-lilypond

Re: Issue 1044 in lilypond: Update lilybuntu and lily-git (whitespace correction etc.)

Updates: Status: Verified Mergedinto: -1051 Comment #11 on issue 1044 by PhilEHolmes: Update lilybuntu and lily-git (whitespace correction etc.) http://code.google.com/p/lilypond/issues/detail?id=1044 (No comment was entered for this change.)

Re: Issue 1125 in lilypond: implement a \path markup command

Updates: Status: Verified Comment #4 on issue 1125 by PhilEHolmes: implement a \path markup command http://code.google.com/p/lilypond/issues/detail?id=1125 Note that the syntax above is not what was implemented - it's shown in the NR as \path thickness (number) commands (list) and

Re: Issue 1237 in lilypond: not all doc files are @node @section compliant

Updates: Status: Invalid Comment #1 on issue 1237 by percival.music.ca: not all doc files are @node @section compliant http://code.google.com/p/lilypond/issues/detail?id=1237 False alarm; a bug in node-menuify.py didn't work on some files which turned out to be good. Sorry for the

Re: Issue 1237 in lilypond: not all doc files are @node @section compliant

Updates: Status: Verified Comment #2 on issue 1237 by percival.music.ca: not all doc files are @node @section compliant http://code.google.com/p/lilypond/issues/detail?id=1237 (No comment was entered for this change.) ___ bug-lilypond