Thomas Morley <thomasmorle...@gmail.com> writes: > Am So., 1. Jan. 2023 um 11:52 Uhr schrieb Jean Abou Samra > <j...@abou-samra.fr>: >> >> Le 31/12/2022 à 21:15, Thomas Morley a écrit : >> > Today I found some time :) >> > >> > lilypond *.ly on all lsr-snippets fails because of the following snippets: >> > custom-tuning-and-midi-rendering.ly >> > dodecaphonic-staff.ly >> > dodecaphonic-staff-with-accurate-ledger-lines.ly >> > microtonal-notation-and-theory-of-harmony.ly >> > retuning-to-a-regular-temperament.ly >> > >> > All of them are using ly:set-default-scale and/or >> > ly:parser-set-note-names on toplevel niveau. >> > >> > How to limit those settings to the current file? >> >> >> I would approach it differently: not "how to fix the snippets?", but >> "how to fix LilyPond so that these settings apply to the current file?". >> > > Sure, out of my depth, though. > And any fix in lilypond would be too late for the 2.24. lsr-update.
Session bleedover does not invalidate the isolated snippets but invalidates our testing infrastructure. The testing infrastructure is not inherently tied to the release version. Have a fix for set-default-scale in the queue. The notenames are more tricky: the way it looks to me, they are maintained in the parser (or lexer?). If we don't set up a new parser, it could be that we get bleedover of things like the default duration and the default tremolo duration as well. That would be worth checking. -- David Kastrup
