Hi all,
I'd like to know how I can do a git pull on all branches simultaneously.
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Are there still any objections against applying?
Regards,
Michael
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
> 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
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 writes:
> > >
> > > > l.2850 \entry {\code \"
> > > >Uber die Nicht-Schachtelung von Klammern und
> > > >
On 2009-09-29, Graham Percival wrote:
> On Tue, Sep 29, 2009 at 06:26:08PM +0200, David Kastrup wrote:
> > Graham Percival writes:
> >
> > > l.2850 \entry {\code \"
> > >Uber die Nicht-Schachtelung von Klammern und
> > > Bindeb\"...
> >
> > It would appear that \code tak
On Tue, Sep 29, 2009 at 06:26:08PM +0200, David Kastrup wrote:
> Graham Percival 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
> be \code{..
On 2009-09-29, Patrick McCarty wrote:
> On Tue, Sep 29, 2009 at 9:15 AM, Graham Percival
> 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 with only 1
Good evening!
I have made some additions to the French texidocs directory along with
my review of NR 1.6 (Staff notation). It would be nice to update the
snippets before releasing but I'm too tired and ill (don't be
frightened, it is not H1N1).
Cheers,
Jean-Charles
On Tue, Sep 29, 2009 at 9:15 AM, Graham Percival
wrote:
> On Mon, Sep 28, 2009 at 10:06:27PM +0100, Neil Puttock wrote:
>> 2009/9/28 Patrick McCarty :
>>
>> > 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 s
2009/9/28 Joe Neeman :
> 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; perhaps it was more wish
Graham Percival writes:
> Attempting to build the docs ends apparently with an error in the
> German translations:
>
> ./notation.cps:2850: Argument of \" has an extra }.
>
> \par
>
>}
> \tclose ...n \rawbackslash \plainfrenchspacing #1}
>
2009/9/28 Graham Percival :
> 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 reinstates the relevant \p
LGTM.
http://codereview.appspot.com/126048/diff/1001/4
File input/regression/quote-kill-cues.ly (right):
http://codereview.appspot.com/126048/diff/1001/4#newcode11
Line 11: q = \relative c' { d2 \quoteDuring #"M" { s1 } e2 \cueDuring
#"M" #UP {s1} f2 }
{ s1 }
http://codereview.appspot.com/1260
2009/9/29 Graham Percival :
> 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 mostly-successful doc bu
On Mon, Sep 28, 2009 at 10:06:27PM +0100, Neil Puttock wrote:
> 2009/9/28 Patrick McCarty :
>
> > 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 done a litt
Attempting to build the docs ends apparently with an error in the
German translations:
./notation.cps:2850: Argument of \" has an extra }.
\par
}
\tclose ...n \rawbackslash \plainfrenchspacing #1}
\null
\codex #
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):
http://codereview.appspot.c
-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 pa
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
On Mon, Sep 28, 2009 at 09:08:46PM -0600, Andrew Hawryluk wrote:
> On Sun, Sep 27, 2009 at 6:57 AM, Graham Percival
> wrote:
> > What do people think about the doc reorg shown in:
> > http://kainhofer.com/~lilypond/Documentation/general/Manuals.html
> > (and the actual manual pages, of course)
>
20 matches
Mail list logo
