Shane Brandes writes:
> Thanks all, and Kieran that pattern will definitely work for future
> projects. Unfortunately that leaves me with unwinding, separating the
> music from the score definitions, 200 some such files for a current
> one to get it to work. I had anticipated that the whole book
Thanks all, and Kieran that pattern will definitely work for future
projects. Unfortunately that leaves me with unwinding, separating the
music from the score definitions, 200 some such files for a current
one to get it to work. I had anticipated that the whole bookpart thing
simply encapsulated t
On 12/29/17, 12:35 PM, "Shane Brandes" wrote:
wow. o.k. That does mean there is no simple way of maintaining vast
projects via tidy compartmentalization.
%--- file a.ly
\version "2.17.97"
aTitle = "a"
righteOne = \relative g' {
\clef "treble"
g8
}
righteTwo =
Shane Brandes writes:
> o.k. back to the include with book part problem. Here is my almost
> minimal code example, which consists of files a.ly, b.ly and test.ly.
> The two files compile alone correctly but when stuck in the bookpart
> they go to pieces.
Sigh. Your original complaint was:
On 12/29/17 20:26, Carl Sorensen wrote:
> Variables can only be defined at the top level. See the Notation Reference
> 3.1.4
That's not entirely true. You can define variables in \paper, \layout, and
\midi blocks too.
Also, you could use the (ly:parser-define! k v) function inside a bookpart,
p.s. While it's arguably less "simple", there's also Jan-Peter's amazing
lilytemplate system… =)
> On Dec 29, 2017, at 2:39 PM, Kieren MacMillan
> wrote:
>
> Hi Shane,
>
>> wow. o.k. That does mean there is no simple way of
>> maintaining vast projects via tidy compartmentalization.
>
> No…
Hi Shane,
> wow. o.k. That does mean there is no simple way of
> maintaining vast projects via tidy compartmentalization.
No… I do it all the time:
a_notes.ly
a_single_score.ly
b_notes.ly
b_single_score.ly
ab_double_score.ly
etc.
For example, "Robin Hood: The Legendary Musical Comedy
wow. o.k. That does mean there is no simple way of maintaining vast
projects via tidy compartmentalization.
Thanks for the clarification.
Shane
On Fri, Dec 29, 2017 at 2:26 PM, Carl Sorensen wrote:
>
>
> On 12/29/17, 12:17 PM, "Timothy Lanfear" wrote:
>
> A bookpart cannot contain statemen
On 12/29/17, 12:17 PM, "Timothy Lanfear" wrote:
A bookpart cannot contain statements like
music = { c'1 }
Yes, this is true. Variables can only be defined at the top level. See the
Notation Reference 3.1.4
Carl
___
lilypond-us
A bookpart cannot contain statements like
music = { c'1 }
After the include processing, your file test.ly begins with something like:
\bookpart {
music = { c'1 }
\score { \music }
}
whereas, you should have
music = { c'1 }
\bookpart {
\score { \music }
}
On 29/12/17 18:35, Shane Brande
o.k. back to the include with book part problem. Here is my almost
minimal code example, which consists of files a.ly, b.ly and test.ly.
The two files compile alone correctly but when stuck in the bookpart
they go to pieces. I even tried it running lilypond-book as a tex file
which interestingly yi
Never mind that code does not function. Still trying to reduce the
full files into minimal examples that both preserve the problem and
compile correctly independently and then crash when included.
Shane
On Fri, Dec 29, 2017 at 11:05 AM, Shane Brandes wrote:
> O.k. after reducing things here is t
O.k. after reducing things here is the problem that causes the snafu.
The independent files to be included all happen to have the same
structure where the score is defined and the voices called to a
variable. as in the following.
altoVoice = \relative c' {
a
}
\score {
\new Staff \with {
Shane Brandes writes:
> O.k. having gone in circles trying to figure out the whole bookpart
> apparatus I discovered that the documentations statement that using
> include is the same as copying and pasting the include into a document
> is false if the include consists of a complete lilypond file
Shane,
Here is one possible way to approach this that I have used:
Use a standard template file that contains the structure for
\header,\score, etc. To create a score, use this sructural template in one
file (say File1) and \include a second file (say File2) that contains
*only* the "music" (e.g.
O.k. having gone in circles trying to figure out the whole bookpart
apparatus I discovered that the documentations statement that using
include is the same as copying and pasting the include into a document
is false if the include consists of a complete lilypond file. Is there
a way around that?
S
16 matches
Mail list logo
