Hi, I am typesetting a movement with a repeat and a clef change right after the
repeat. I have a suitable line break where the repeat ends and the clef change
happens. Default Lilypond sets the new clef within the repeat, before the
end-repeat sign, which I don’t want and find meaningless in my
Sent with Proton Mail secure email.
--- Original Message ---
On Saturday, January 28th, 2023 at 00:09, Jean Abou Samra
wrote:
> On 27/01/2023 22:35, Ole V. Villumsen wrote:
>
> > Hi, I am typesetting a movement with a repeat and a clef change right after
> > the repeat. I
ith Proton Mail secure email.
--- Original Message ---
On Saturday, January 28th, 2023 at 06:52, Ole V. Villumsen
wrote:
> Thanks, everyone, for your contributions.
>
> First of all Jean. Your code gives me exactly what I wanted. I haven’t
> learned to use the internals, bu
It seems to me that when an ossia staff (or similar supplementary staff)
happens to begin at a line break, Lilypond meaninglessly sets space apart for a
key signature before the line break even though there is no key signature
printed there. Is this a bug? Is there a workaround?
The output from
\new Staff \with {
alignAboveContext = main
}
{
\set Staff.explicitKeySignatureVisibility = #end-of-line-invisible %%
<-- The solution
\mainKey
g4 f g2 |
}
>>
}
}
Sent with Proton Mail secure email.
On Tuesday, November 28th, 2
**Question in short**: Suppose I have a staff in a variable. Can I impose
breaks (line breaks, page breaks, page turns) on that staff without modifying
the variable? My use case is using the staff in a part and in a score with
other parts, where obviously the breaks need to be different. Another
> The classic fix is
>
> <<
> \new Devnull { s1*5 \break }
> \staffIGot
> >>
This was exactly what I was after. It’s nice and simple and works well. Thank
you.
I might wish for it being better documented. I see Devnull documented well in
the Internals Reference, but I didn’t readily see it
Nice, Knute, thanks, that gives me what I wanted.
I had had something similar in mind, but wasn’t able to carry it out.
Sent with [Proton Mail](https://proton.me/) secure email.
On Wednesday, May 22nd, 2024 at 20:36, Knute Snortum wrote:
> On Wed, May 22, 2024 at 10:43 AM Ole V. Villum
