Yay that looks exactly like Brittens score.
I'll be on the look out for such an implementation.
And indeed, something that is not yet possible isn't a bug.
Always good to know it wasn't me. ;-)
Thanks
vriendelijke groet, Erik Appeldoorn
------ Origineel bericht ------
Van: "Lukas-Fabian Moser" <[email protected]>
Aan: "E Appeldoorn" <[email protected]>; "Hans Aikema"
<[email protected]>; "[email protected]"
<[email protected]>
Verzonden: 25-12-2021 21:14:18
Onderwerp: Re: possible bug?
Hi Erik,
Just showing one other bar that looks suddenly awfull with strict
spacing
<<
\new Staff \relative c'' {
es4-- r8
\tuplet 5/4 {f32([ ges as ges f)]}
es8^.[ \acciaccatura {a} bes^!] es,4-- |
}
>>
Thanks, that really is not desirable.
The \newSpacingSection command also introducing no problems, I see no
good solution with current LilyPond.
The problem is that the setting to treat grace columns as loose
(strict-grace-spacing) is fixed for the spacing spanner. It's almost
trivial to add an \override'able setting to PaperColumns in general,
but this requires re-compiling LilyPond. With a new property
Score.PaperColumn.force-loose-grace-spacing, I can achieve
with
\version "2.23.6"
<<
\new Staff \relative c'' {
\override Score.PaperColumn.force-loose-grace-spacing = ##t
g8[ b16 as] g8[ b] a16[ g b a] g8[ \appoggiatura { g32 a } b8]|
\revert Score.PaperColumn.force-loose-grace-spacing
es4-- r8 \tuplet 5/4 {f32([ ges as ges f)]} es8^.[ \acciaccatura {
a } bes^!] es,4-- |
}
\new Staff \relative c'' {
g8[ b16 as] g8[ b] a16[ g b a] e16[ d f e]
}
>>
You don't need to try compiling this with your version of LilyPond, as
it won't work. But this should be discussed on the developers list;
I'll try to take care of this tomorrow.
Lukas
