Re: Accidental overlaying stem

On 25/08/10 02:36, Phil Holmes wrote: "Nick Payne" wrote in message news:4c72f469.4060...@internode.on.net... I think I have reported this before - a beamed note with an accidental on a ledger line above the stave has the accidental colliding with the stem of the previous note. For different no

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

Status: Accepted Owner: Labels: Type-Documentation Priority-Low Maintainability Frog New issue 1237 by percival.music.ca: not all doc files are @node @section compliant http://code.google.com/p/lilypond/issues/detail?id=1237 With few exceptions all .itely files should be untouched by run

Issue 1236 in lilypond: CG+scripts should use ~/lilypond-git/

Status: Accepted Owner: Labels: Type-Other Priority-Medium Maintainability Frog New issue 1236 by percival.music.ca: CG+scripts should use ~/lilypond-git/ http://code.google.com/p/lilypond/issues/detail?id=1236 lily-git.tcl creates a repository in ~/lilypond-git/ All scripts should be adju

Re: Issue 1162 in lilypond: website bibliography

Comment #14 on issue 1162 by percival.music.ca: website bibliography http://code.google.com/p/lilypond/issues/detail?id=1162 I see accents on the website. What else do you want? I think it's working. ___ bug-lilypond mailing list bug-lilypond@gnu.o

Re: Issue 989 in lilypond: ensure that no information about 2.12.3 features is only in the regtests

Comment #25 on issue 989 by percival.music.ca: ensure that no information about 2.12.3 features is only in the regtests http://code.google.com/p/lilypond/issues/detail?id=989 Sorry for the pronoun misuse. Apparently a snippet only makes it into our docs if it's tagged with "docs" and at le

Issue 1235 in lilypond: Accidental overlays stem

Status: Accepted Owner: Labels: Type-Collision Priority-Critical Regression New issue 1235 by PhilEHolmes: Accidental overlays stem http://code.google.com/p/lilypond/issues/detail?id=1235 Nick Payne reports: "A beamed note with an accidental on a ledger line above the stave has the accid

Re: Issue 989 in lilypond: ensure that no information about 2.12.3 features is only in the regtests

Comment #24 on issue 989 by bealingsplayfordnews: ensure that no information about 2.12.3 features is only in the regtests http://code.google.com/p/lilypond/issues/detail?id=989 http://lsr.dsi.unimi.it/LSR/Item?id=706 As stated a few times, it's not "them, it's "it". __

Re: Issue 989 in lilypond: ensure that no information about 2.12.3 features is only in the regtests

Comment #23 on issue 989 by percival.music.ca: ensure that no information about 2.12.3 features is only in the regtests http://code.google.com/p/lilypond/issues/detail?id=989 I just did a LSR update, but didn't see them. Were they tagged with "docs" and approved? ___

Re: Issue 1231 in lilypond: New clefs collide with compressed multimeasure rests

Comment #2 on issue 1231 by brownian.box: New clefs collide with compressed multimeasure rests http://code.google.com/p/lilypond/issues/detail?id=1231 eluze says in that thread (answer to original report, http://lists.gnu.org/archive/html/bug-lilypond/2010-08/msg00427.html): %-8<-

Re: [tablatures] tremolos in tablature

Carl Sorensen schrieb: On 8/23/10 3:28 PM, "Marc Hohl" wrote: Carl Sorensen schrieb: [...] It seems that we should use 0.48 times the *actual* staff space, rather than the default staff space. Um, after reading your answer twice - it should be the other w

Re: Issue 1203 in lilypond: Page_turn_engraver refuses to break at R1*12, crams notes and produces blank page in the middle of score.

Updates: Status: Verified Comment #8 on issue 1203 by percival.music.ca: Page_turn_engraver refuses to break at R1*12, crams notes and produces blank page in the middle of score. http://code.google.com/p/lilypond/issues/detail?id=1203 Reinhold reports that it works fine in his score

Re: Issue 1231 in lilypond: New clefs collide with compressed multimeasure rests

Comment #1 on issue 1231 by percival.music.ca: New clefs collide with compressed multimeasure rests http://code.google.com/p/lilypond/issues/detail?id=1231 When did this begin? Do we have any estimate on the last good version number? ___ bug-l

Re: Issue 1234 in lilypond: Fill-line should not use word space, but should use springs-and-rods

Updates: Labels: Type-Enhancement Priority-Low Comment #1 on issue 1234 by Carl.D.Sorensen: Fill-line should not use word space, but should use springs-and-rods http://code.google.com/p/lilypond/issues/detail?id=1234 From Alexander's comments on Rietveld issue 1689041: http://coderev

Issue 1234 in lilypond: Fill-line should not use word space, but should use springs-and-rods

Status: Accepted Owner: New issue 1234 by Carl.D.Sorensen: Fill-line should not use word space, but should use springs-and-rods http://code.google.com/p/lilypond/issues/detail?id=1234 Please DO NOT add issues directly to this tracker unless you are certain that they correspond to our pre

Re: Issue 382 in lilypond: misaligned nested \fill-lines

Updates: Status: Fixed Labels: fixed_2_13_31 Comment #3 on issue 382 by Carl.D.Sorensen: misaligned nested \fill-lines http://code.google.com/p/lilypond/issues/detail?id=382 Fixed by Alexander Kobel -- commit d3d40f3469eda2cb327bebbd392c1ce88b114394

Re: Issue 1116 in lilypond: Title not centered

Updates: Status: Fixed Labels: fixed_2_13_31 Comment #9 on issue 1116 by Carl.D.Sorensen: Title not centered http://code.google.com/p/lilypond/issues/detail?id=1116 Fixed by Alexander Kobel -- commit d3d40f3469eda2cb327bebbd392c1ce88b114394 _