[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lilypond-book: inline option
From: |
John Williams |
Subject: |
Re: lilypond-book: inline option |
Date: |
Tue, 19 Apr 2005 14:45:08 -0600 (MDT) |
On Tue, 19 Apr 2005, Han-Wen Nienhuys wrote:
> Op za, 02-04-2005 te 20:44 -0700, schreef John Williams:
> >
> > P.S. this group of patches should apply cleanly to 2.5.17 in the
> > following order:
> >
> > 1. refactor.patch
> > 2. htmlquote.patch
> > 3. filename.patch
> > 4. alt.patch
> > 5. inline.patch
>
> can you have a look at the lilypond-book.py in 2.5.20 to see what parts
> are still missing, and which you need? I added meaningful error messages
> (including file and line numbers for input snippets) to lilypond-book
> recently.
The refactor patch has been applied in cvs, but none of the other ones
have been.
Right now, all I can get lilypond cvs to do is segfault. It might be
because I only have guile-1.6.4 instead of guile-1.6.5. I cannot find a
higher rpm for fc3. Yes, I'm lazy.
I'll resubmit 2-5 when I can get lilypond working again.
Concerning filename.patch, my argument for allowing snippet files to be
named bach.ly (bach.png, etc) instead of bach-373738.ly is that knowing
the real name allows me do do things which the lilypond programmers did
not think of. I can link to those images from another document, I can
compile a .midi from the .ly and link to that, etc. And all without
having old links break and wondering what the new name will be if I tweak
the music.
~ John Williams