Re: removing non-empty staves

2012-12-03 Thread Keith OHara
gmail.com> writes: > I'm familiar with the instruction > \context { \Staff \RemoveEmptyStaves } > Is there a way to tell Lilypond to stop showing a non-empty staff > (that contains notes) and reclaim its space after the next line break? There is a variable called keepAliveInterfaces

Re: removing non-empty staves

2012-12-03 Thread Wim van Dommelen
Hi Christopher,I'm not sure if this example matches your need, but it is a thing I once crafted for a special piece. It shows an ossia stave in a different color and size. Starting at some point and ending after I don't need it anymore. But alas not on a line break, don't know how to do thatCom

removing non-empty staves

2012-12-03 Thread nothingwavering
Greetings. I'm a long-time user of lilypond. I love it and have used it for my massive solo pipe organ transcription of a 30-minute movement of a symphony scored for large orchestra, so I feel like I know my way around Lilypond at an intermediate level. I don't really delve deeply into the Sc

Re: Parameterizing a LilyPond function

2012-12-03 Thread PMA
David Kastrup wrote: PMA writes: David& David, Thank you Both! I'm using the one-param version, as in this score my X& Y offsets always match. But on exec -- uh oh -- Scheme is yelling: :2:65: error: GUILE signaled an error for the expression beginning here \once \override Gli

Re: Parameterizing a LilyPond function

2012-12-03 Thread David Kastrup
PMA writes: > David & David, > > Thank you Both! > > I'm using the one-param version, as in this score my X & Y offsets > always match. > But on exec -- uh oh -- Scheme is yelling: > >:2:65: error: GUILE signaled an error for the expression > beginning here >\once \override Glissando