lilypond-user
[Top][All Lists]
Advanced

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

Re: unhiding a hidden staff at the NEXT line break (instead of previous


From: David Kastrup
Subject: Re: unhiding a hidden staff at the NEXT line break (instead of previous line break)
Date: Sat, 15 Dec 2012 09:32:37 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

Keith OHara <address@hidden> writes:

> <nothingwavering <at> gmail.com> writes:
>> 
>> Anyone know how I can get Lilypond to unhide a staff at the NEXT
>> line break?
>
> No.
>
> It looks like you have a part for a cello section with the form
>     unison  |A|  simple-divisi  |B|  complex-divisi
> where the complex-divisi music demands a separate staff for each part.
>
> If you put your wished-for \showStaffNextBreak at |A| then you would
> be assuming there is at least one line break between |A| and |B|.
>
> Placing your \showStaff at |B| on the two separate-part staves makes more
> sense.   But I do not see a way to stop the combined-part staff at the 
> same linebreak where the seaparate-part staves need to begin.  For a dirty
> way to get your job done, you could mark the combined-part staff as 
> removable starting _almost_one_line_ before |B| (see below).
>
>> hideStaff = \set Staff.keepAliveInterfaces = #'()
>> This ends up working quite well for 
>> * short to moderate-length pieces 
>> * where only one score is to be created from music 
>>   so annotated with \hideStaff and \showStaff 
>> * and where explicit line breaks (\beak and \noBreak) are used.
>
> Without the transition from chords to separate staves, you can use 
> RemoveEmptyStaves to set the second staff, with automatic line-breaking
> <http://lists.gnu.org/archive/html/lilypond-user/2012-12/msg00061.html>
>   
> \version "2.16.0"
> \paper { #(set-paper-size "a6") indent = 1.0\cm short-indent = 1.2\cm }
>
> letStaffVanish = \set Staff.keepAliveInterfaces = #'()
> showStaff = \unset Staff.keepAliveInterfaces

So it would seem that we need something like an inHades property that,
if set, let's the Harakiri_engraver remove everything that would
properly be alive.

Ok, inHades is likely too cute.  How about reverseHarakiri instead?

-- 
David Kastrup




reply via email to

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