On 2014/01/14 14:30:45, dak wrote:
https://codereview.appspot.com/51230043/diff/20001/ly/satb.ly#newcode75
ly/satb.ly:75: #(define-once Key *unspecified*) I don't see that using some Scheme interface rather than providing
that facility
on the LilyPond level makes a lot of sense. For one thing, this will
not
overload identifiers defined in the Guile module rather than the
parser even
though
Key = \key\default
would do.
So you you mean that define-once should be added to LilyPond as a generally available facility, or that some other mechanism is needed?
The goal is not just that an ordinary user finds it easy to _use_ a
particular
template, but also that he or she finds it easy to define his own
templates.
That's what we need to get a template ecosystem off the ground.
To do this we'll need a general mechanism for defining such built-in templates - what the variables' names are and their defaults, and the context structure with the variables in place - and a means of invoking them. Perhaps we should set up a new issue to track the discussion of this. Trevor https://codereview.appspot.com/51230043/ _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
