This seems to have been fixed in lilypond 2.22.1.

Reply via email to