Re: first-page-number silently ignored sometimes
Jean Abou Samra <[email protected]>
| Newsgroups | gmane.comp.gnu.lilypond.bugs |
|---|---|
| Message-ID | <[email protected]> |
Le 08/09/2022 à 03:35, Nikolai Hedler a écrit : > Putting the function inside a bookpart's paper block causes it to have > no effect. Well, that's expected. It's similar to \override Clef.color = ... instead of \override Staff.Clef.color = ... Page numbering is handled on the book level, so you have to put first-page-number there. Starting with LilyPond 2.23.12, there is actually a bookpart-level-page-numbering paper variable that allows to do the numbering per-bookpart. LilyPond tries not to get in the way of the user if they want to customize things. If there had been a warning, this Scheme-based implementation of bookpart-level-page-numbering before it was added to LilyPond would not have worked with first-page-number: https://lists.gnu.org/archive/html/lilypond-user-fr/2022-07/msg00043.html _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond