diff options
author | David Kastrup <dak@gnu.org> | 2014-06-05 20:34:14 +0200 |
---|---|---|
committer | David Kastrup <dak@gnu.org> | 2014-07-06 14:31:00 +0200 |
commit | 1d3beed53413315ec6c0553b003b8c5776f8c38f (patch) | |
tree | 4ba79c3b2edbe7ce23ae5cbf79077f7a43a4e929 /scripts | |
parent | 1b554886980bc48aed1ef4025f28292c694b4c55 (diff) |
Issue 3983: Avoid define-public and define*-public with curried definitions
Regarding curried definitions, GUILE has problems with define-public
before version 2.0.10, and with define*-public even later.
define-safe-public is implemented by LilyPond itself rather than the
(ice-9 curried-definitions) module and is unproblematic.
This is basically a cop-out since juggling with overriding bugfix
definitions of define-public is a distraction for getting GUILEv2
migration under way that we can do without.
Diffstat (limited to 'scripts')
-rw-r--r-- | scripts/musicxml2ly.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/scripts/musicxml2ly.py b/scripts/musicxml2ly.py index 2da2dab60e..e270aed95e 100644 --- a/scripts/musicxml2ly.py +++ b/scripts/musicxml2ly.py @@ -41,7 +41,7 @@ additional_definitions = { "tuplet-note-wrapper": """ % a formatter function, which is simply a wrapper around an existing % tuplet formatter function. It takes the value returned by the given % function and appends a note of given length. - #(define-public ((tuplet-number::append-note-wrapper function note) grob) + #(define ((tuplet-number::append-note-wrapper function note) grob) (let* ((txt (if function (function grob) #f))) (if txt (markup txt #:fontsize -5 #:note note UP) |