Re: multiple \scores in a lily-book included file?

[David Raleigh Arnold]

On Monday 17 March 2003 09:03 am, David Raleigh Arnold wrote:
> On Saturday 15 March 2003 11:30 pm, Hans Forbrich wrote:
> > I agree to a certain extent.  Judicious use of < music > and {
> > music } and \break - along with a very strict naming rules (drawing
> > on years of large project s/w coding experience) -  helped me
> > recently (70+ page Cantata). You are however quite correct - the
> > source score blocks are very, very ugly.
> >
> > I could also request the reverse - having an external file
> > containing the music assigned to an Identifier, I'd love to be able
> > to 'extract bars 3-8' into the current score.
>
> Sly gets the notes out of the .ly file.  All you would have to do
> is copy the .sly score, delete lines 1-2 and 9-x, and run sly.
> If you want both the long and short, you would have a different name
> on the new includes. Not a problem.
> DaveA

I should have mentioned the situation with the level
of includes with lilypond-book.  It is a feature, not a bug, because
otherwise you find yourself spending a lot of time staring at the 
screen watching unnecessary recompiles.  Your script can make a 
date-stamped copy (%dateandtime at the bottom)
of the envelope nonotes.ly file (nonotes-copy.ly) whenever you change 
its included notes and the .lytex file should include the copy rather 
than the original.

Also, I'm not at all sure whether it is a feature of lilypond-book, 
LaTeX, or TeX.

Could this be the problem with the multiple scores?  If the first c 
scale is included, make a change
in that and see if the product changes.

For a lilypond book where I could use a single template for all the .ly 
files, I had separate files for notes and used a sed script
to create a complete .ly file with the notes in it, but I haven't
rewritten sly to generate both -ptn.ly files, stamped copies, and
and -inc.ly file with notes written into it, all at once.  The latter 
would be great for sending in bug reports, not so good for editing and 
fixing, or I would never have written sly in the first place.  That 
extends sly considerably by making it useful to make .sly files with a 
single part.  Now, sly doesn't have to know anything about the .ly 
file, and that would change.  It will be automatic when I do it, 
hopefully about two months from now.  There will have to be at least 
three arguments instead of two.  If I were a real programmer I could do 
it in a few minutes, but I'll have to get back to it.  DaveA

-- 
Lies are the first casualty of peace.
dra@ or http://www.openguitar.com