PATCHES - Countdown to March 18
Here is the current countdown report. The next countdown will begin on 2024-03-18 A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: No patches in Push at this time. Countdown: No patches in Countdown at this time. Review: !2273 Doc: Fix old value of bottom-margin in changes.tely - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/2273 !2272 Context::check_removal(): iterate more carefully - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/2272 !2271 Acceptance_set improvements - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/2271 New: No patches in New at this time. Waiting: No patches in Waiting at this time. Cheers, Colin
Re: strange `break-align-symbols` behaviour
> there is no key signature at this point, right? This is my interpretation: the key signature is removed by break-visibility, but the X alignment of a mark is computed before that happens. signature.asc Description: This is a digitally signed message part
strange `break-align-symbols` behaviour
In December I asked the question below on the 'lilypond-user' list (https://lists.gnu.org/archive/html/lilypond-user/2023-12/msg00014.html), alas, without an answer – I try again, this time on 'lilypond-devel'. I'm also attaching the image for completeness. Please help. Werner == Please consider this example. ```tex \version "2.25.11" music = { c'1 \tempo "T-note" c'1 } \markup { time-signature } { \override Score.MetronomeMark.break-align-symbols = #'(time-signature) \music } \markup { time-signature, key-signature } { \override Score.MetronomeMark.break-align-symbols = #'(time-signature key-signature) \music } \paper { ragged-right = ##f } ``` I don't understand why the addition of `key-signature` to the `break-align-symbols` list makes 'T-note' left-align to the bar line — there is no key signature at this point, right? IMHO, the correct behaviour would be that 'T-note' is still aligned to the note. What am I missing? Or is this a bug?