David Sumbler writes:
> From: David Kastrup
>> > Date: Mon, 11 Apr 2016 09:29:40 +0200
>> >
>> > #... at top level is executed and the result ignored to allow for
>> > #(set! ...) and similar expressions with usually unspecified return
>> > #codes. Just try
>> >
>> > $(if sectionA compileA)
>
Am 15.04.2016 um 19:46 schrieb David Sumbler:
>>> You seem to be ready to *do* some manual changes to your master file
>>> > > (e.g. defining a variable or not). So you could simply put your
>>> > > different scores in individual include files and comment in/out these
>>> > > includes.
>>> > > If
David Sumbler writes:
> As an experiment, I produced this:
>
> File: experimentNotes.ly
>
> \version "2.19.24"
>
> compileA =
> \score {
> \new Staff {
>a' a' a' a'
> }
> \layout { }
> }
[...]
> #(if sectionA #{ \compileA #} )
From: David Kastrup
> > Date: Mon, 11 Apr 2016 09:29:4
David Sumbler writes:
> As an experiment, I produced this:
>
> File: experimentNotes.ly
>
> \version "2.19.24"
>
> compileA =
> \score {
> \new Staff {
>a' a' a' a'
> }
> \layout { }
> }
[...]
> #(if sectionA #{ \compileA #} )
#... at top level is executed and the result ignored to
Hi David,
compileA is not compiled, because it is just a music-expression inside a
scheme-expression.
But if you add it to the current book, it will appear. So your example
will work with a tiny extension:
#(if sectionA (add-score #{ \compileA #} ))
But you should look around for templating
Hi David,
I'm sure this could be made work, with some more complex Scheme code.
But If I'm understanding you correctly there seems to be a simpler way.
You seem to be ready to *do* some manual changes to your master file
(e.g. defining a variable or not). So you could simply put your
different sc
When editing a piece with several instruments and several movements,
there are various outputs I would like, such as a complete full score, a
full score of a single movement, a complete instrumental part, the
instrument part of a single movement, and also a midi file of any of
these items.
I thoug
