On 22/02/2022 23:28, Lukas-Fabian Moser wrote:
Do you consider this inferior (or unnecessarily verbose and therefore
non-minimal)?
No, the motivation for that was more naive. You’re probably right that
it would actually be more minimal in a deeper sense to explicitly
instantiate the staves.
On 2/22/22, 3:29 PM, "lilypond-user on behalf of Lukas-Fabian Moser"
wrote:
Hi Simon,
> This is a minimal example for the issue you were having:
>
> %%%
> \version "2.22.1"
>
> upper = { 1 \break 1 }
> lower = { R1*2 }
>
> \
Hi Simon,
This is a minimal example for the issue you were having:
%%%
\version "2.22.1"
upper = { 1 \break 1 }
lower = { R1*2 }
\score {
\new PianoStaff << \upper \lower >>
\layout {
\context {
\Staff
\RemoveEmptyStaves
}
}
}
Hi,
On 12/02/2022 20:22, jh wrote:
This is the shortest example I could figure out how to make
David and Lukas-Fabian have already answered the core question, so allow
me to comment on this: tiny examples are important for communication on
the list and it takes a while to learn how to make
Hi Jay,
Am 12.02.22 um 20:22 schrieb jh:
From one project to the next sometimes 'Frenching' a score works and
sometimes it doesn't
This is the shortest example I could figure out how to make
the second system should be just two staves (and using the same
context etc 5 days ago worked as expect
jh writes:
> From one project to the next sometimes 'Frenching' a score works and
> sometimes it doesn't
> This is the shortest example I could figure out how to make
> the second system should be just two staves (and using the same
> context etc 5 days ago worked as expected on a different score
From one project to the next sometimes 'Frenching' a score works and
sometimes it doesn't
This is the shortest example I could figure out how to make
the second system should be just two staves (and using the same context
etc 5 days ago worked as expected on a different score so this was copy
p
