|
From: | Marc Hohl |
Subject: | Re: [Lilypond-auto] Issue 2856 in lilypond: Patch: Get along with use of grob-property instead of grob-property-path in overrides |
Date: | Mon, 24 Sep 2012 12:15:35 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 |
Am 24.09.2012 12:04, schrieb address@hidden:
Status: New Owner: ---- Labels: Type-Enhancement Patch-newNew issue 2856 by address@hidden: Patch: Get along with use of grob-property instead of grob-property-path in overrideshttp://code.google.com/p/lilypond/issues/detail?id=2856Get along with use of grob-property instead of grob-property-path in overridesLilyPond uses a willy-nilly mixture of grob-property and grob-property-path when generating overrides programmatically (the parser only uses grob-property-path). Several override-reinterpreting commands and functionalities were not prepared to deal with this. http://codereview.appspot.com/6544060
A quick glance at the code shows + (cond + ((ly:music-property m 'grob-property #f) => list) + (else + (ly:music-property m 'grob-property-path))))) what does the second line mean? I have never seen '=>' in a scheme program. Sorry for this beginner's question... Marc
[Prev in Thread] | Current Thread | [Next in Thread] |