lilypond-user
[Top][All Lists]
Advanced

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

Re: \book usage


From: John Mandereau
Subject: Re: \book usage
Date: Wed, 02 Nov 2005 00:33:38 +0100

Gilles wrote:
> "all_allegro.ly" includes "all_allegro.inc.ly" and contains a \score.
> "all_allegro.inc.ly" defines a StaffGroup and includes all the parts
> for this movement, e.g. "recorder_allegro.inc.ly" which defines the
> a variable ("recorderNotes") containing the note sequence.
> [And similarly for the other movements.]

> %--- all.ly ---
> \version "2.6.0"
> 
> \paper {
>   raggedbottom = ##f
>   raggedlastbottom = ##t
> }
> 
> \book {
>   \header {
>     \include "header.inc.ly"
>   }
> 
>   \include "all_allegro.ly"
>   \include "all_siciliana.ly"
>   \include "all_bourree.ly"
>   \include "all_menuet.ly"
>   \include "all_trio.ly"
> }
> %-----
> 
> but lilypond doesn't like it:
> 
> $ lilypond all.ly
> GNU LilyPond 2.6.3
> Processing `all.ly'
> Parsing...
> recorder_allegro.inc.ly:3:0: error: syntax error, unexpected STRING
> 
> recorderNotes = \relative c'' {
> recorder_allegro.inc.ly:135:0: error: syntax error, unexpected '}'
> 
> }
> recorder_allegro.inc.ly:146:21: error: unknown escaped string: 
> `\recorderNotes'
>     \transpose c c {
>                      \recorderNotes }
> recorder_allegro.inc.ly:146:21: error: syntax error, unexpected STRING
>     \transpose c c {
>                      \recorderNotes }
> all_allegro.ly:5:7: error: errors found, ignoring music expression
> \score
>        {
> all_allegro.ly:16:2: error: errors found, ignoring music expression
> 
>   \unfoldRepeats \staves
> all.ly:24:0: error: syntax error, unexpected '}'
> 
> }
> error: failed files: "all.ly"
> 
> 
> Could you explain why it doesn't work?

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.

-- 
John Mandereau <address@hidden>





reply via email to

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