Re: Issue 1005 in lilypond: syntax highlighting in the docs

Updates: Owner: v.villenave Comment #1 on issue 1005 by v.villenave: syntax highlighting in the docs http://code.google.com/p/lilypond/issues/detail?id=1005 I'm starting #1. Will post my language file here before submitting it upstream. -- You received this message because you are li

Re: checking CG 7. issues

On 06.02.2010, at 21:34, Graham Percival wrote: Hi guys, Could you check over CG 7. Issues ? http://lilypond.org/doc/v2.13/Documentation/contributor/issues In particular, is there any info that I've told you (privately or on the mailing list) that isn't in there? Is there anything that you k

Doc -- \shiftDurations is undocumented.

Mike O'Donnell found that \shiftDurations is not in the index of music functions. I haven't checked to see if it occurs anywhere in the docs or not, but clearly at least an index should be included. Thanks, Carl ___ bug-lilypond mailing list bug-li

checking CG 7. issues

Hi guys, Could you check over CG 7. Issues ? http://lilypond.org/doc/v2.13/Documentation/contributor/issues In particular, is there any info that I've told you (privately or on the mailing list) that isn't in there? Is there anything that you know now, that you didn't know before you started bei

\fermataMarkup positioned higher then \fermata... in some specific cases

Hi. Can you remember?-) -- ‘fermata-rest-position.ly’: "Fermatas over multimeasure rests are positioned as over normal rests." (http://code.google.com/p/lilypond/issues/detail?id=981) I am not sure that this is an issue --- \fermata always positioned as close to rest as possible (in any voice),

Issue 1005 in lilypond: syntax highlighting in the docs

Status: Accepted Owner: Labels: Type-Build Priority-Postponed Frog New issue 1005 by percival.music.ca: syntax highlighting in the docs http://code.google.com/p/lilypond/issues/detail?id=1005 It would be cool if we added syntax highlighting to the docs with source-highlight: http://www.gn

Re: [Q] Issue 999: Enhancement: Dynamics could switch from one staff to another

У сб, 2010-02-06 у 13:12 +, Neil Puttock пише: > Now I've looked at this issue in a bit more detail, I think I was a > bit hasty in marking it as a duplicate. I'll change it back and > explain why on the tracker. Thank You. I hardly could decide/agree that they are duplicates. > > Cheers, >

Re: Issue 942 in lilypond: out-www/web/ has upper-case and lower-case filenames

Updates: Status: Accepted Owner: --- Labels: -Type-Other -fixed_2_13_10 Type-Build Comment #8 on issue 942 by percival.music.ca: out-www/web/ has upper-case and lower-case filenames http://code.google.com/p/lilypond/issues/detail?id=942 It's not breaking the docs or we

Re: Issue 957 in lilypond: remove duplicate anchor generation in texi2html

Updates: Status: Verified Comment #6 on issue 957 by percival.music.ca: remove duplicate anchor generation in texi2html http://code.google.com/p/lilypond/issues/detail?id=957 (No comment was entered for this change.) -- You received this message because you are listed in the owner or

Re: Issue 954 in lilypond: GUB add temporary patch to lilypond

Updates: Status: Verified Labels: fixed_2_13_11 Comment #7 on issue 954 by percival.music.ca: GUB add temporary patch to lilypond http://code.google.com/p/lilypond/issues/detail?id=954 CG instructions have worked for two releases, so verified. -- You received this message bec

Re: Issue 939 in lilypond: shared location for included docs

Updates: Status: Verified Comment #4 on issue 939 by percival.music.ca: shared location for included docs http://code.google.com/p/lilypond/issues/detail?id=939 (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC fields of

Re: Issue 845 in lilypond: AUTHORS / THANKS should be integrated into new website

Updates: Status: Verified Comment #4 on issue 845 by percival.music.ca: AUTHORS / THANKS should be integrated into new website http://code.google.com/p/lilypond/issues/detail?id=845 (No comment was entered for this change.) -- You received this message because you are listed in the o

Re: Issue 842 in lilypond: bibliography not built

Updates: Status: Verified Comment #7 on issue 842 by percival.music.ca: bibliography not built http://code.google.com/p/lilypond/issues/detail?id=842 (No comment was entered for this change.) -- You received this message because you are listed in the owner or CC fields of this issue, or

Re: Issue 538 in lilypond: almost-collision notehead and tuplet bracket+number

Updates: Status: Verified Comment #2 on issue 538 by percival.music.ca: almost-collision notehead and tuplet bracket+number http://code.google.com/p/lilypond/issues/detail?id=538 (No comment was entered for this change.) -- You received this message because you are listed in the owne

Re: Issue 305 in lilypond: positioning of hairpins and dynamics

Updates: Labels: Patch Comment #10 on issue 305 by n.puttock: positioning of hairpins and dynamics http://code.google.com/p/lilypond/issues/detail?id=305 Patch: http://codereview.appspot.com/129073 -- You received this message because you are listed in the owner or CC fields of this iss

Re: Issue 999 in lilypond: Enhancement: Dynamics could switch from one staff to another

Updates: Status: Accepted Owner: --- Mergedinto: -305 Comment #2 on issue 999 by n.puttock: Enhancement: Dynamics could switch from one staff to another http://code.google.com/p/lilypond/issues/detail?id=999 I've reopened this since it's slightly different from issue 3

Re: Issue 943 in lilypond: input/regression/slur-broken-trend.ly broken

Updates: Labels: Patch Comment #16 on issue 943 by n.puttock: input/regression/slur-broken-trend.ly broken http://code.google.com/p/lilypond/issues/detail?id=943 Patch uploaded: http://codereview.appspot.com/203054 -- You received this message because you are listed in the owner or C

Re: [Q] Issue 999: Enhancement: Dynamics could switch from one staff to another

On Sat, Feb 06, 2010 at 01:12:07PM +, Neil Puttock wrote: > On 6 February 2010 09:19, Dmytro O. Redchuk wrote: > > > So, "just for tracking": since both issues marked as "Enhancement", i > > believe it's quite safe to leave 999 unverified until 305 be closed. > > I might be wrong, but I thin

Re: Issue 943 in lilypond: input/regression/slur-broken-trend.ly broken

Comment #15 on issue 943 by n.puttock: input/regression/slur-broken-trend.ly broken http://code.google.com/p/lilypond/issues/detail?id=943 I'll put it up on Rietveld shortly. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred t

Re: [Q] Issue 999: Enhancement: Dynamics could switch from one staff to another

On Sat, Feb 06, 2010 at 11:19:11AM +0200, Dmytro O. Redchuk wrote: > У ср, 2010-02-03 у 13:59 +0200, Dmytro O. Redchuk пише: > > A question: issue 999 has been merged into 305 --- does this mean that > > fixing 305 will automatically fix 999? > > So, "just for tracking": since both issues marked

Re: [Q] Issue 999: Enhancement: Dynamics could switch from one staff to another

On 6 February 2010 09:19, Dmytro O. Redchuk wrote: > So, "just for tracking": since both issues marked as "Enhancement", i > believe it's quite safe to leave 999 unverified until 305 be closed. I might be wrong, but I think you're supposed to mark duplicates as verified if you agree they're dupl

Re: [Q] Issue 999: Enhancement: Dynamics could switch from one staff to another

У ср, 2010-02-03 у 13:59 +0200, Dmytro O. Redchuk пише: > Hi. > > A question: issue 999 has been merged into 305 --- does this mean that > fixing 305 will automatically fix 999? > > I believe, 999 should be marked as "Verified" only if a solution for > 305 fixes 999 too, that's why i'm asking