Re: ly:load (LSR 785)

[David Kastrup]

Simon Albrecht <address@hidden> writes:

> Hello everybody,
>
> I am very grateful to have found
> <http://lsr.di.unimi.it/LSR/Snippet?id=785> – it’s amazing to just
> have a readymade solution for that available.
>
> Downloading the file and compiling works fine with 2.18.2, however
> with 2.19.80 I get the following:
>
> $ lilypond lsr-785.ly
> GNU LilyPond 2.19.80
> Processing `lsr-785.ly'
> Parsing...
> lsr-785.ly:38:2: error: GUILE signaled an error for the expression
> beginning here
> #
>  (ly:load "define-note-names.scm") \language "nederlands"
> Unbound variable: define-session-public
>
> I’m all the more puzzled since ly:load isn’t documented in the NR
> Appendix List of Scheme functions of both 2.18.2 and 2.19.80. Also,
> there doesn’t seem to be a convert-ly rule for ly:load.
>
> How should I circumvent this?

ly:load is not at fault here.  This LSR redefines basics of LilyPond's
operation, then reloads some of its internals.  That's completely messed
up.  You can probably say something like

#(define define-session-public define)

before the load in order to mess up things even more.  But
define-note-names.scm has not been written with the intent to be
reloaded by users.  This should be done in a saner manner.

-- 
David Kastrup