Hi Nikolai, Can you post a (preferably tiny) example of the variable that produces this problem? LilyPond may not evaluate variables when they appear but it still needs to figure out where they begin and end so perhaps that is the source of the problem? It's hard to know without seeing any code. Kevin
On Mon, Mar 23, 2015 at 7:43 PM, Nikolai Hedler <nhed...@gmail.com> wrote: > I'm attempting to arrange a Bach organ fugue for brass quintet, and I am > attempting to create a single file which outputs the score and all > individual parts. I would like to create a variable which contains the > contents of the \paper block for the individual parts, which is different > than that of the main score, but for some reason, variable definition seems > to function differently than I would expect. > > I had thought that when a variable is defined, it would not be interpreted > in-place, as it is meant to be used elsewhere; as such, if any error is > found within the variable, the first error would be raised where the > variable is called. Instead, it seems that the variable definition is > treated as an isolated, non-printing music "object" which must be parsed > for errors in-place before continuing. Because of this, any perceived error > (i.e. the contents of a \paper block, which are valid in that context) > results in a warning being raised "Music unsuitable for output-def" > referring to the variable name. > > This is incredibly inconvenient, as it seems to prevent anything but music > itself from being defined within a variable. Is there any way around this > or is this intended behavior? > > Thanks in advance for your help! > Nikolai Hedler > > _______________________________________________ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user > >
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
