John Mandereau wrote:
Le jeudi 06 décembre 2007 à 15:24 -0800, Graham Percival a écrit :
Or, you could think of it as a
@lilypondfile{}
except that this macro (say, @lsrfile{} ) also includes the texinfo
from the snippet file, instead of just the .ly code.
It looks like you're looking for "@lilypondfile[texidoc]{foo/bar.ly}".
Look at what I just committed to master, in Accidentals. Is it what you
want?
I could kiss you!! Yes, that's exactly what I wanted!!!
*ahem* On the cheek. In traditional French greeting style.
... wait a moment. [texidoc] was there all along? All my angst over
this for the past three months was completely unnecessary? Gee, don't I
feel like an idiot now.
:)
It seems like we currently cannot quote the music without quoting
the text; maybe we should use 'indent=10' instead of 'quote'?
Hmm... I'd rather not specify an exact indent=XX number. If possible
I'd rather have lilypond-book modified -- I think that [quote,texinfo]
should only apply the [quote] to the actual lilypond code, not the
texinfo portion. Or potentially we could add a [lilyquote] or
[noquotetexinfo]
I changed LILYPOND_BOOK_INCLUDES in make/lilypond-vars.make, so you can
include any snippet from input/new or input/lsr.
We don't want to link directly to input/new (I've removed this) -- the
buildscripts/makelsr.py script copies everything from input/new/ to
input/lsr/
This was the last major stumbling block. Here's the plan:
1. Get .36 out the door.
2. I'll check the current LSR->docs stuff, then explain it to John.
3. make the times->tuplet change.
4. Get .37 out the door
5. Wait a week for bug reports. If there's nothing major, then
6. Update LSR to use .37.
Cheers,
- Graham
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
