- Original Message -
From: Julien Rioux jri...@physics.utoronto.ca
To: lilypond-devel@gnu.org
Sent: Wednesday, February 29, 2012 10:45 PM
Subject: Re: log files not deleted by doc-clean
On 26/02/2012 8:30 AM, Phil Holmes wrote:
Not sure if that's a good thing or not - it could be
These instructions worked for me. I'd be happy for someone else to try this
out, and then I think it could be updated and added to the CG.
# Create a VM with well over the minimum default file storage
# - in my experience, the VM with 8 gigs runs out of disk and can't
# be increased. YMMV.
On Sun, Mar 18, 2012 at 12:15:20PM -, Phil Holmes wrote:
# A general rule: do not interrupt a build. It seems to use file locks
# as a way of controlling multi-cpu builds, and it can get confused
# if interrupted. I've had to start from scratch in this case. :-(
It's possible to
Reviewers: Graham Percival, Julien Rioux, dak, Reinhold,
Message:
Please review
Description:
We're now down to about 460 lines of output from make doc -s, and
lilypond-book.py (GNU LilyPond) 2.15.34 is nearly 20% of them. If the
way this is output is changed to progress(), then running -book
http://codereview.appspot.com/5848056/diff/1/scripts/lilypond-book.py
File scripts/lilypond-book.py (right):
http://codereview.appspot.com/5848056/diff/1/scripts/lilypond-book.py#newcode104
scripts/lilypond-book.py:104: progress(_ ('%s (GNU LilyPond) %s' %
(ly.program_name,
LGTM, James, apart from a couple of nitpicks (but I
didn't check the sizes :)
Might be worth raising an issue about the lack of an
automated appendix once this is pushed.
Thanks
Trevor
http://codereview.appspot.com/5783075/diff/3001/Documentation/notation/spacing.itely
File
LGTM
http://codereview.appspot.com/5848056/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On Sun, Mar 18, 2012 at 1:49 PM, gra...@percival-music.ca wrote:
http://codereview.appspot.com/5848056/diff/1/scripts/lilypond-book.py
File scripts/lilypond-book.py (right):
http://codereview.appspot.com/5848056/diff/1/scripts/lilypond-book.py#newcode104
scripts/lilypond-book.py:104:
- Original Message -
From: Julien Rioux julien.ri...@gmail.com
To: philehol...@googlemail.com; gra...@percival-music.ca;
julien.ri...@gmail.com; d...@gnu.org; reinhold.kainho...@gmail.com;
lilypond-devel@gnu.org; re...@codereview-hr.appspotmail.com
Sent: Sunday, March 18, 2012 6:19 PM
Le 18/03/2012 19:31, Phil Holmes disait :
http://codereview.appspot.com/5848056/diff/1/scripts/lilypond-book.py#newcode104
scripts/lilypond-book.py:104: progress(_ ('%s (GNU LilyPond) %s' %
(ly.program_name, ly.program_version)))
We don't need the _ (), we don't translate that string.
Julien
Reviewers: ,
Message:
I will need some advice on any inconsistent/incorrect terms for
variables/symbols/values.
Description:
Doc: AU - document -dhelp CLI options
Issue 2216
Add new @node for the -d[Scheme_val] option.
Renamed old node so that it is distinguishable from the
cli using sceheme
http://codereview.appspot.com/5783075/diff/3001/Documentation/notation/spacing.itely
File Documentation/notation/spacing.itely (right):
http://codereview.appspot.com/5783075/diff/3001/Documentation/notation/spacing.itely#newcode211
Documentation/notation/spacing.itely:211: @code{set-paper-size}
\paper { #(set-paper-size a3) }
\new StaffGroup
\new Staff { \repeat unfold 8 {R1 e'1} }
\addlyrics { Worked twice...
but then I ploughed... straight... through. }
\new Staff { R1*16 }
http://codereview.appspot.com/5843063/
___
For 20:00 MDT Tuesday March 21
Critical:
Issue 2408
http://code.google.com/p/lilypond/issues/detail?id=2408: Inconsistent
automatic beaming when using multiple tuplets next to each other - R
5844052 http://codereview.appspot.com/5844052/
Enhancement:
Issue 2406
looks basically good
http://codereview.appspot.com/5843060/diff/1/Documentation/usage/running.itely
File Documentation/usage/running.itely (right):
http://codereview.appspot.com/5843060/diff/1/Documentation/usage/running.itely#newcode56
Documentation/usage/running.itely:56: * Basic command
15 matches
Mail list logo