Re: lilypond-book

[Phil Hézaine]

Le 20/02/2011 14:52, Peter Buhr a écrit :
>    Le 19/02/2011 20:21, Peter Buhr a écrit :
>    > I'm attempting to use lilypond-book but have run into the following 
> anomaly.
>    ...
>    I think you have to put the whole path for test.ind
>    if your test.ind is one directory upstairs of out2 you could also write:
> 
>    \input{../test.ind}
> 
> So I tried both of your suggestions, and this problem only gets worse.  Below
> are the two test files with the relative and absolute path-names to the 
> test.ind
> file and the output from running lilypond-book.
> 
> In the first case using the relative path-name, lilypond-book cannot find file
> ../test.ind. I conjecture that lilypond-book is running in the current
> directory and not the "out2" directory; hence, it is looking in the parent
> directory for test.ind and cannot find it.

Yes. Sorry. I thought you're following the process described in the
documentation. I process like this:

cd /your/current/directory)

/usr/local/bin/lilypond-book --lily-output-dir=out-lily --pdf
--output=out2  your.lytex

Note that I have already created a dir: out-lily

cd out2

pdflatex  your.tex

You'll have a error message about ../test.ind while you process the
first run and it disappears for the second (when you are in out2)

> In the second case using the absolute path-name, it DOES work. I get the
> preprocessed file test.tex in directory "out2". HOWEVER!!! Look at the last
> line of the output from lilypond-book:
> 
> Writing `/home/pabuhr/guitar/music/test.tex'...
> 
> For some reason, lilypond-book has written a file called test.tex in the
> CURRENT directory versus directory "out2". In fact, it overwrote the file
> test.tex I had in the current directory, destroying it!!!
> 
> SO FOR ANYONE USING LILYPOND-BOOK, A STRONG CAUTIONARY NOTE. IT CAN DESTROY
> FILES IN THE CURRENT DIRECTORY, SO BE VERY CAREFUL.

I think there is a note in the documentation. No?

Phil.