lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: \book usage


From: Gilles
Subject: Re: \book usage
Date: Wed, 2 Nov 2005 01:19:45 +0100
User-agent: Mutt/1.5.11

> 
> AFAIK, named music expressions *have to* be defined at toplevel, not
> within a \book or \score block. So, a simple thing to do may be moving
> every
> 
> \include "<staff>_<movement>.inc.ly"
> 
> statement from all_<movement>.inc.ly to all.ly, before \book. You will
> certainly have to rename expressions to avoid redefinitions, e.g. you'll
> have to replace each  recorderNotes  occurence with
> <movement>RecorderNotes
> otherwise all movements will be the same.
> 

Of course, I thought of this solution, but it provides a much less
systematic and maintainable layout :-{
Instead of only having instrument name based variables (and reuse them
for each movement), there must now be every combination of instrument
and movement name variables, and worse even, since everything must be
defined before actual use (in \book), you have to keep track of all the
other variables that could have been defined to simplify input (e.g. 
repetitive patterns) in a given instrument and be sure that the name
won't be used in another file included later on...

In the documentation, section 11.1.1, about "Input variables and Scheme",
it is mentioned that variables can also be defined in \header, \midi and
\layout blocks.
Is there some inherent impossibility to being able to do the same for
\book?
Or, is there another "recommended" way to build documents from reusable
elements, as was asked in another post today?


Thanks,
Gilles




reply via email to

[Prev in Thread] Current Thread [Next in Thread]