Le 04/12/2021 à 17:35, David Kastrup a écrit :
Simon Albrecht <[email protected]> writes:
Hi everyone,
I have had a very weird error pop up, which doesn’t appear to be
related to a specific LilyPond version, nor was it triggered by any
recent update to OLL (though I’m using chordmode very rarely):
In the following snippet,after loading the core package loader from
openLilyLib,Lily won’t recognise the changed note name language inside
any explicit input mode.
[...]
I attach the package.ily file from openLilyLib—I can’t see anything in
there which might cause this odd behaviour…
(ly:parser-include-string "\\include \"oll-core/internal/init.ily\"")))
This will include oll-core/internal/init.ily if it hasn't yet been
loaded, and that will likely be responsible for messing with the
language.
In short, what you quoted likely doesn't contain the culprit.
In oll-core/internal/file-handling.scm, I see
(define (immediate-include file)
(if (file-exists? file)
(let ((parser (ly:parser-clone)))
(ly:parser-parse-string parser "\\language \"nederlands\"")
(ly:parser-parse-string parser
(format "\\include \"~a\"" file))
#t)
#f))
This seems a likely source of trouble, but I have
not investigated the handling of pitch names to
see how it should work.
Regards,
Jean
