running `make grand-replace`
We should run `make grand-replace` to update all copyright years. Since this is a completely mechanical thing to do, I suggest to submit the MR, wait until a build was successful, then immediately merging and committing it, bypassing the normal reviewing cycle. This should minimize the hassles with additional rebasing of future MRs. Objections? Werner
PATCHES - Countdown for February 14th
Hello, Here is the current patch countdown list. The next countdown will be on February 18th. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !645 Preparations for `make grand-replace` - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/645 !642 python: Globally replace codecs.open() by open() - Jonas Hahnfeld https://gitlab.com/lilypond/lilypond/-/merge_requests/642 Countdown: !653 Scoped lookup of music properties - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/653 !651 NR: Index entries for grob direction prefixes - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/651 !648 Recognize empty bar lines by shape, not glyph name - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/648 !644 Update auxiliary scripts for `configure`. - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/644 !643 IR beautification - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/643 !622 Initialize session from a dedicated parser - Han-Wen Nienhuys https://gitlab.com/lilypond/lilypond/-/merge_requests/622 Review: !654 Don't close volta bracket at bar ".|:" or ".|" - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/654 !652 Avoid transparent bar lines in ancient staves - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/652 !649 Staff_spacing: recognize empty bar lines by width - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/649 New: No patches in New at this time. Waiting: No patches in Waiting at this time. *** Regards, James
Re: overfull lines in IR
> Right now, some overlong lines are auto-generated in the Internals > Reference. As an example, look at the entry for `KievanStaff`, > which contains the following. > > • Set translator property autoAccidentals to: > > '(Staff # > # measurepos)>) > > In the file `engraver-init.ly` you can find the following code, > which is what the IR documents: > > autoAccidentals = #`(Staff ,(make-accidental-rule 'same-octave 0) > ,neo-modern-accidental-rule) > > Showing this `#` stuff doesn't make much sense to me – > in particular, having the function arguments appears to be useless. > > Can a Scheme guru improve this, replacing the current IR output with > something that resembles the code in `engraver-init.ly`? Another bad example is • Set translator property ottavationMarkups to: '((4 . "29") (3 . "22") (2 . "15") (1 . "8") (-1 . "8") (-2 . "15") (-3 . "22") (-4 . "29")) in the documentation, while the code in `ly/engraver-init.ly` is simply ottavationMarkups = #ottavation-numbers It seems to me that during the creation of the documentation, expansion of the property value should be prevented. Can this be done? Werner
