lilypond-user
[Top][All Lists]
Advanced

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

Re: Problems with using \bookpart


From: Timothy Lanfear
Subject: Re: Problems with using \bookpart
Date: Tue, 20 Dec 2016 22:36:02 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1

How about this?

\version "2.19.48"

\language "english"

printScore  = ##t
printMvtOne = ##t
printMvtTwo = ##t

#(if
  (and printScore
   (or printMvtOne printMvtTwo))
     (ly:parser-include-string "\\include \"testprint.ily\""))


On 20/12/16 21:57, David Sumbler wrote:
I am still experimenting with constructing a file structure which makes
sense to me for more complex works.  I have come quite a long way with
it and discovered some interesting things.

But \bookpart seems to cause problems.

The following works:

File: test.ly
%%%%%
\version "2.19.48"

\language "english"

printScore  = ##t
printMvtOne = ##t
printMvtTwo = ##t

$(if
   (and printScore
    (or printMvtOne printMvtTwo))
   #{ \include "testprint.ily" #} )
%%%%%

File: testprint.ily
%%%%%
\version "2.19.48"

\book {
   \score { c }
}
%%%%%

Modify the second file thus:

File: testprint.ily
%%%%%
\version "2.19.48"

\book {
   \bookpart {
     \score { c }
   }
}
%%%%%

This no longer works, but gives the following error messages:

Parsing.../usr/local/lilypond/usr/share/lilypond/current/scm/lily-library.scm:243:5:
 In procedure ly:book-process in expression (process-procedure book paper ...):
/usr/local/lilypond/usr/share/lilypond/current/scm/lily-library.scm:243:5: Wrong type 
(expecting real number): #<undefined>

Once again I am finding that the use of \bookpart is giving problems.  I don't 
know if this is once again somehow connected with the fact that bookparts have 
no variable scope, but it's a damn nuisance anyway!

Any suggestions?

David


_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user

--
Timothy Lanfear, Bristol, UK.




reply via email to

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