Alle 23:37, mercoledì 24 marzo 2004, Erik Sandberg ha scritto:
> There are problems with this setup: your .ly files will not be compatible
> with future lilypond versions. If Lilypond will change its autobeaming
> code, and you try to use your old file with the new lilypond, then the
> lyrics may b
There is no dependency itely->texi! If I apply a change to an itely
file like preface.itely I expect that preface.texi is rebuilt
automatically, but this isn't true.
Werner
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/ma
> Hmm. I don't see any change for this in the ChangeLog, but when I
> run the current cvs makeinfo -o foo.info lilypond.nexi, I get
>
> Node: Staff notation<0x7f>81023
>
> and that is indeed where the Staff notation node starts.
It works now for me too with the current CVS of texinfo.
Wer
I'm not sure that this code:
# makeinfo <= 4.6 image bug workaround
if [ $(MAKEINFO_VERSION) -le 4006000 ]; then \
(cd $(outdir) && \
ls -1 lily-*.ly | sed 's/.ly$$/.txt/' | xargs touch) || true; \
fi
from ly-rules.make is optimal. With newer versions of makeinfo you
get zillions
