fails make doc
https://codereview.appspot.com/13300048/diff/1/Documentation/changes.tely
File Documentation/changes.tely (right):
https://codereview.appspot.com/13300048/diff/1/Documentation/changes.tely#newcode92
Documentation/changes.tely:92: @end lilypond
This @lilypond breaks make doc.
Did
typo
LGTM
https://codereview.appspot.com/13300048/diff/1/Documentation/changes.tely
File Documentation/changes.tely (right):
https://codereview.appspot.com/13300048/diff/1/Documentation/changes.tely#newcode66
Documentation/changes.tely:66: the allowance of horizontal sapce for
tempo and rehears
https://codereview.appspot.com/13400046/diff/1/Documentation/contributor/feta-font.itexi
File Documentation/contributor/feta-font.itexi (right):
https://codereview.appspot.com/13400046/diff/1/Documentation/contributor/feta-font.itexi#newcode133
Documentation/contributor/feta-font.itexi:133: --->
- Original Message -
From: "Mark Polesky"
To: "Phil Holmes" ; "David Kastrup"
Cc:
Sent: Tuesday, September 10, 2013 5:34 PM
Subject: Re: Documentation: punctuation in menus
Phil Holmes wrote:
> I understand the issue with colons in node names. That
> was why I asked this question. I
Phil Holmes wrote:
> I understand the issue with colons in node names. That
> was why I asked this question. I'll ask it again should
> there be a documentation writer who has had this to deal
> with before: what do we use for node names when there is
> punctuation (specifically a colon) in a sec
"Phil Holmes" writes:
> - Original Message -
> From: "David Kastrup"
> To:
> Sent: Tuesday, September 10, 2013 3:37 PM
> Subject: Re: Documentation: punctuation in menus
>
>
>> "Phil Holmes" writes:
>>
>>> I'm having a go at
>>> http://code.google.com/p/lilypond/issues/detail?id=3495.
"Phil Holmes" writes:
> - Original Message -
> From: "David Kastrup"
> To: "Phil Holmes"
>>
>> When a policy makes things go from bad to worse, it makes sense to first
>> change things manually to good before trying to apply policy. That's a
>> stupid section title.
>
> I understand t
- Original Message -
From: "David Kastrup"
To:
Sent: Tuesday, September 10, 2013 3:37 PM
Subject: Re: Documentation: punctuation in menus
"Phil Holmes" writes:
I'm having a go at
http://code.google.com/p/lilypond/issues/detail?id=3495. Some of the
subsection headings contain punct
- Original Message -
From: "David Kastrup"
To: "Phil Holmes"
Cc:
Sent: Tuesday, September 10, 2013 3:58 PM
Subject: Re: Documentation: punctuation in menus
"Phil Holmes" writes:
- Original Message -
From: "David Kastrup"
To:
Sent: Tuesday, September 10, 2013 3:37 PM
Su
- Original Message -
From: "David Kastrup"
To: "Phil Holmes"
Cc:
Sent: Tuesday, September 10, 2013 4:09 PM
Subject: Re: Documentation: punctuation in menus
"Phil Holmes" writes:
- Original Message -
From: "David Kastrup"
To: "Phil Holmes"
When a policy makes things g
"Phil Holmes" writes:
> I'm having a go at
> http://code.google.com/p/lilypond/issues/detail?id=3495. Some of the
> subsection headings contain punctuation - for example "Warning: key
> signatures and pitches" in
> http://lilypond.org/doc/v2.17/Documentation/learning/accidentals-and-key-signature
I'm having a go at http://code.google.com/p/lilypond/issues/detail?id=3495.
Some of the subsection headings contain punctuation - for example "Warning:
key signatures and pitches" in
http://lilypond.org/doc/v2.17/Documentation/learning/accidentals-and-key-signatures.
Putting the colon into a me
Reviewers: lemzwerg, dak,
Message:
Please review
Description:
An attempt to codify and illustrate how to indent LilyPond's metafont
formatting rules.
Please review this at https://codereview.appspot.com/13400046/
Affected files (+14, -6 lines):
M Documentation/contributor/feta-font.itexi
I
LGTM.
https://codereview.appspot.com/13641043/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
https://codereview.appspot.com/13302048/diff/3001/input/regression/part-combine-mmrest-apart.ly
File input/regression/part-combine-mmrest-apart.ly (right):
https://codereview.appspot.com/13302048/diff/3001/input/regression/part-combine-mmrest-apart.ly#newcode5
input/regression/part-combine-mmres
Keith OHara writes:
> David Kastrup gnu.org> writes:
>
>> You make it sound as if issue 2910 will warrant a bunch of fine-tuning
>> before the results can be called production-ready.
>
> No, the stencil-integral patch had changed the meaning of a padding,
> we started started fine-tuning the d
16 matches
Mail list logo