Le mardi 15 avril 2008 à 15:44 +0200, Jan Nieuwenhuizen a écrit :
> Hi,
>
> There seems to be a make loop in input/lsr building info.
I had a similar problem: make was looping in input/lsr building WWW-post
target. I fixed it by removing
insput/lsr/bagpipes{-intro.itely,.snippet-list} in commit
Actually, it's more likely to do with the lilypond-book
improvements. In any case, it's undergoing current work and we
should expect things to break.
Cheers,
- Graham
On Tue, 15 Apr 2008 22:27:13 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
>
> This might be caused by input/lsr/lilypond-s
This might be caused by input/lsr/lilypond-snippets.tely not being updated
to match the four renamed sections in specialist.itely. I sent a note
to -dev & Jan about this a couple of hours ago. (My git is broken again, so
I can't fix it)
Trevor D
- Original Message -
From: "Graham
On Tue, 15 Apr 2008 21:37:58 +0100
"Neil Puttock" <[EMAIL PROTECTED]> wrote:
> I'm probably stating the obvious, but displaying snippet code is
> broken; every example I've tried clicking on leads to a 404.
I see this too.
John? Are we copying all the ??/ directories inside
input/lsr/out-www?
Jan
Commit bf5fc592ed4ffc6bae4e97d60c52d044554e6872 changed the section headings
in specialist.itely and renamed four files to correspond, as follows:
bagpipes.itely -> wind.itely
guitar.itely -> fretted-strings.itely
piano.itely -> keyboards.itely
strings.itely -> unfretted-strings.itely
The
Currently, lilypond-book explicitly sets
@exampleindent 0
before each quoted lilypond example. This causes problems with other
quotations / examples later on, because they are no longer indented (as one
would expect). I suppose this explicit @exampleindent was due to the fact
that makeinfo conv
Hi,
There seems to be a make loop in input/lsr building info. See the
attached make debug output, here's the gist
Must remake target `out-www/bagpipes.itely'.
Must remake target `out-www/lilypond-snippets.texi'.
Must remake target `out-www/lilypond-snippets.info-images-dir.dep'.
Must r
Han-Wen Nienhuys wrote:
> 2008/4/14, John Mandereau <[EMAIL PROTECTED]>:
> > in current lilypond-book, it seems that using sets for reading existing
> > output file names is a significant speed bottleneck.
> > def split_output_files(directory):
> please convert back to a set before returning
