On Mon, Sep 28, 2009 at 09:08:46PM -0600, Andrew Hawryluk wrote:
On Sun, Sep 27, 2009 at 6:57 AM, Graham Percival
gra...@percival-music.ca wrote:
What do people think about the doc reorg shown in:
http://kainhofer.com/~lilypond/Documentation/general/Manuals.html
(and the actual manual
On Mon, Sep 28, 2009 at 01:40:14PM -0700, Patrick McCarty wrote:
On 2009-09-28, Graham Percival wrote:
Yes, precisely. Add a remove preamble bit to
def relevant_contents (self, ly):
on line 1253.
I just pushed a fix. I did various tests on a small lilypond-book
project (with 8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As the name suggests, \killCues should only remove cue notes generated with
\cueDuring, but not quoted music generated with \quoteDuring. (In my case, I'm
constructing a staff with the choir and the solo voice combined, using
\quoteDuring).
This
LGTM.
There are a few trailing spaces in the regtest though.
Some of the lines in recording-group-emulate are far too long
(particularly where you've added the comment).
http://codereview.appspot.com/124064/diff/1/2
File input/regression/quote-overrides.ly (right):
Attempting to build the docs ends apparently with an error in the
German translations:
./notation.cps:2850: Argument of \ has an extra }.
inserted text
\par
to be read again
}
\tclose ...n \rawbackslash \plainfrenchspacing #1}
On Mon, Sep 28, 2009 at 10:06:27PM +0100, Neil Puttock wrote:
2009/9/28 Patrick McCarty pnor...@gmail.com:
I just pushed a fix. I did various tests on a small lilypond-book
project (with 8 snippets), and the file/folder names now stay the same
if the preamble is changed.
I've just
2009/9/29 Graham Percival gra...@percival-music.ca:
Hmm. I'm now getting random errors (file not found) while
compiling the docs with 4 jobs. This worked fine a few days ago.
I had the same problem last night with a random png, but had a
successful build after restarting.
I just did a
2009/9/28 Graham Percival gra...@percival-music.ca:
If you can make these, or give me exact instructions on how to
generate them myself, I will be delighted to do so. :)
I have tons of horsepower at my disposal; the only thing that
(should be) lacking is time.
OK, here's a patch which
Graham Percival gra...@percival-music.ca writes:
Attempting to build the docs ends apparently with an error in the
German translations:
./notation.cps:2850: Argument of \ has an extra }.
inserted text
\par
to be read again
}
\tclose ...n \rawbackslash
2009/9/28 Joe Neeman joenee...@gmail.com:
In C++, a function must be either prototyped or defined before being
used.
Hmm, in that case I'd better dump my reference manual and get a more
recent version. :) It's 1998 vintage, so it's hot off the press after
the C++ standard was ratified;
On Tue, Sep 29, 2009 at 9:15 AM, Graham Percival
gra...@percival-music.ca wrote:
On Mon, Sep 28, 2009 at 10:06:27PM +0100, Neil Puttock wrote:
2009/9/28 Patrick McCarty pnor...@gmail.com:
I just pushed a fix. I did various tests on a small lilypond-book
project (with 8 snippets), and the
On 2009-09-29, Patrick McCarty wrote:
On Tue, Sep 29, 2009 at 9:15 AM, Graham Percival
gra...@percival-music.ca wrote:
Hmm. I'm now getting random errors (file not found) while
compiling the docs with 4 jobs. This worked fine a few days ago.
I just did a mostly-successful doc build
On Tue, Sep 29, 2009 at 06:26:08PM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
l.2850 \entry {\code \
Uber die Nicht-Schachtelung von Klammern und
Bindeb\...
It would appear that \code takes an argument, so the usual usage would
On 2009-09-29, Graham Percival wrote:
On Tue, Sep 29, 2009 at 06:26:08PM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
l.2850 \entry {\code \
Uber die Nicht-Schachtelung von Klammern und
Bindeb\...
It would appear that
On 2009-09-29, Patrick McCarty wrote:
On 2009-09-29, Graham Percival wrote:
On Tue, Sep 29, 2009 at 06:26:08PM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
l.2850 \entry {\code \
Uber die Nicht-Schachtelung von Klammern und
I *do* suspect there's a problem with the @lilyvindex macro, though.
I doubt that since I've basically duplicated code from texinfo.tex.
On the other hand, it is possible that the standard indexing macros
don't work well for non-ASCII stuff; this would indicate a generic
problem.
But I can't
16 matches
Mail list logo
