...and I just realized that I can use \once for that purpose! Thank you for
helping me through this!
On Tue, Dec 3, 2024 at 4:25 PM Eric Benson wrote:
> OK, I see the problem. Since my page breaks are nearly always explicit, I
> could get the effect I need if there was a way to say "change the r
OK, I see the problem. Since my page breaks are nearly always explicit, I
could get the effect I need if there was a way to say "change the rule for
this upcoming break, but then change it back immediately after". Otherwise
I have to put the undo setting somewhere after the beginning of the first
Eric Benson writes:
>> On Fri, Nov 29, 2024 at 1:13 PM Eric Benson wrote:
>>
>>> I'm making lead sheets, where, unlike common practice, the key signature
>>> and clef are not usually shown at the beginning of each line. LilyPond
>>> makes this easy to control, with
>>>
>>> \override Score.Clef.b
Any thoughts? Anyone?
On Fri, Nov 29, 2024 at 1:13 PM Eric Benson wrote:
> I'm making lead sheets, where, unlike common practice, the key signature
> and clef are not usually shown at the beginning of each line. LilyPond
> makes this easy to control, with
>
> \override Score.Clef.break-visibilit
Variables can be rebound.
On Tue, Dec 3, 2024, 2:52 AM Raphael Mankin wrote:
>
>
> On 02/12/2024 18:00, Saul Tobin wrote:
> > Hi Raphael,
> >
> > Lilypond variables exist in the same namespace, with the exception that
> > output-def blocks like paper and layout are Scheme modules. Lilypond
> > i
Il giorno mar 3 dic 2024 alle 15:45:21 +00:00:00, N. Andrew Walsh
ha scritto:
Hi List,
On Monday, December 2nd, 2024 at 16:39, Simon Albrecht
wrote:
> Please note that the new qpageview which works with Qt6 has not
been
> released yet, so you have to install it from git master branch.
Hi List,
On Monday, December 2nd, 2024 at 16:39, Simon Albrecht
wrote:
> > Please note that the new qpageview which works with Qt6 has not been
> > released yet, so you have to install it from git master branch.
On a related note: it seems that there would also need to be an updated
python-pop
Dear Thomas,
Let me know if the attached file achieves what you were hoping for.
Thanks,
-William
%
\version "2.25.21"
scoreAViolinIPart = {c'4 c' c' c' c' c' c' c' c' c' c' c' c'1 }
scoreAViolinIIPart = {
% for every staff which is the BOTTOM of a group (example: piano left
hand)
Hi,
I have this Score:
<<
\new StaffGroup
<<
\scoreAViolinIPart
\scoreAViolinIIPart
>>
\new ChoirStaff
<<
\scoreASopranoVoicePart
\scoreAAltoVoicePart
\scoreATenorVoicePart
\scoreABassVoicePart
>>
\scoreABassoContinuoPart
>>
I w
