Le mardi 01 août 2023 à 20:35 +, Ole V. Villumsen a écrit :
> Finally a warning message from Lilypond would be nice when I do it wrong so
> that I don’t start suspecting a bug. Explanatory and with suggestion how to
> fix if possible.
If anybody is going to invest work into this, I think it w
Hi Will,
Thanks for your question.
My first wish would be to have cross-staff stems explained in the NR proper,
not just in a snippet. Maybe it would fit somewhere under 2.2.1 Common notation
for keyboards? The description would obviously best make the requirements clear
in the text, not only i
I can see "\autoBeamOff" pretty clearly here, which was the first link
found from googling "lilypond cross-staff stems"
https://lilypond.org/doc/v2.25/Documentation/snippets/staff-notation_003a-cross-staff-stems
-will
On 8/1/23 15:22, Ole V. Villumsen via bug-lilypond wrote:
Hi Jean,
indeed.
> And no, this is pretty far from perfect and could also benefit from
> being made clear in the NR.
What do you want to have where exactly?
Werner
Hi Jean,
indeed. I retract my bug report.
Your solution works in the case where I specify \crossStaff in the lower staff
(or both) and, as you say, the manual beams only in the upper staff.
And no, this is pretty far from perfect and could also benefit from being made
clear in the NR.
Cheers,
Ole
Le mardi 01 août 2023 à 18:34 +, Ole V. Villumsen via bug-lilypond a écrit :
> % Manual beams and cross-staff stems don’t seem to work together.
> % Expected result: Shared stems across staves; beams above notes in upper
> staff only.
>
> % I have tried all possible combinations of specifying
% Manual beams and cross-staff stems don’t seem to work together.
% Expected result: Shared stems across staves; beams above notes in upper staff
only.
% I have tried all possible combinations of specifying beams and \crossStaff in
the
% upper staff, the lower one and both. I always get unwanted
