Carl Sorensen <c_soren...@byu.edu> writes: > I still don't like the divergence between define-markup-command and > define-internal-markup-command.
Agree. I think define-internal-markup-command makes for more readable code. If we can consider define-internal-markup-command to be used _only_ in the distributed Lilypond tree, we can change its behavior any way we like. > Perhaps we should move towards required the default properties list > for all defined markup commands. My personal preference would be to phase out all *-internal-* commands completely. One way to do this would be a keyword based approach, something like (define-markup-command (args as previous) :properties ((var1 . default) var2) "DOC string" ... ) The DOC string likely does not need a keyword of its own since it will not be the only expression in the body. In that manner, defaulted properties and DOC string can be added on an as-needed base. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
