Pushed as 688f5f1711d8ca07338385a2ae0191b1a8aae315.
http://codereview.appspot.com/4553056/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Thanks a lot, Neil.
Could you have a last look at the Scheme files?
I'm not sure of the indentation.
I created a new scm/text.scm file for the definitions I couldn't put
elsewhere.
Bertrand
http://codereview.appspot.com/4553056/
___
lilypond-devel ma
http://codereview.appspot.com/4553056/diff/106003/Documentation/included/special-characters.ly
File Documentation/included/special-characters.ly (right):
http://codereview.appspot.com/4553056/diff/106003/Documentation/included/special-characters.ly#newcode1
Documentation/included/special-charact
New patch set.
I hope this is ready for to be pushed, now.
http://codereview.appspot.com/4553056/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
http://codereview.appspot.com/4553056/diff/103001/Documentation/notation/notation-appendices.itely
File Documentation/notation/notation-appendices.itely (right):
http://codereview.appspot.com/4553056/diff/103001/Documentation/notation/notation-appendices.itely#newcode909
Documentation/notation/n
http://codereview.appspot.com/4553056/diff/103001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/4553056/diff/103001/Documentation/notation/input.itely#newcode1636
Documentation/notation/input.itely:1636: @end lilypond
Yes, unfor
Tuesday, September 20, 2011 11:18 AM
Do you think I have to move the table from the regtest to the
Appendix A
(and keep the rest of the regtest as a regtest)?
Yes. Between the current A10 and A11 looks a good place.
Trevor
-
No virus found in this message.
Checked by AVG - www.avg.
http://codereview.appspot.com/4553056/diff/103001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/4553056/diff/103001/Documentation/notation/input.itely#newcode1636
Documentation/notation/input.itely:1636: @end lilypond
On 2011/09
Hmm, I don't understand one comment, but I agree with the others.
Thanks,
Bertrand
http://codereview.appspot.com/4553056/diff/103001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/4553056/diff/103001/Documentation/notation/inpu
A few comments following a quick look at the doc changes
Trevor
http://codereview.appspot.com/4553056/diff/103001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/4553056/diff/103001/Documentation/notation/input.itely#newcode1591
New patch set including some documentation work.
http://codereview.appspot.com/4553056/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 2011/09/20 12:07:31, J_lowe wrote:
> Where do you think I should put it? In NR 1.8.1 or 1.8.2?
Hmm.. I'd say 3.3.3 actually
Oh, yes! This is better.
> Do you think I have to move the table from the regtest to the
Appendix A (and
> keep the rest of the regtest as a regtest)?
I am no
On 2011/09/20 10:18:41, Bertrand Bordage wrote:
Hey!
I'm currently writing a doc entry that explains how to use
replacements. I have
a few questions:
Where do you think I should put it? In NR 1.8.1 or 1.8.2?
Hmm.. I'd say 3.3.3 actually
http://lilypond.org/doc/v2.14/Documentation/notat
Hey!
I'm currently writing a doc entry that explains how to use replacements.
I have a few questions:
Where do you think I should put it? In NR 1.8.1 or 1.8.2?
Do you think I have to move the table from the regtest to the Appendix A
(and keep the rest of the regtest as a regtest)?
Bertrand
PS
Hey Bertrand,
Could you show an example, in the regtest, of how one would write:
–
(or whatever) such that – appeared (meaning the string "–" -
not the replacement n-dash).
http://codereview.appspot.com/4553056/
___
lilypond-devel mailing list
lilyp
passes make and reg tests
http://codereview.appspot.com/4553056/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 2011/09/16 21:31:25, J_lowe wrote:
Hello, passes make but fails make check
Sorry ignore this, I just realised I made a mistake in my make check.
I'll redo now.
James
http://codereview.appspot.com/4553056/
___
lilypond-devel mailing list
lilypond
Hello, passes make but fails make check
please see
http://code.google.com/p/lilypond/issues/detail?id=1891#c1
James
http://codereview.appspot.com/4553056/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/
New patch set.
'&' and '@' have been added to the lexer.
'&' is therefore a perfectly working escape character in lyrics.
Bertrand
http://codereview.appspot.com/4553056/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mail
19 matches
Mail list logo