Carl D. Sorensen wrote:
I think the breakage about which Valentin is concerned is not in the LilyPond
distribution, but in user's files. Users may have their own defined markups that
aren't part of the distribution. And if the category requirement is not optional,
existing code would break (with no possibility of fixing in convert-ly)>
Such a syntax change should indeed be possible to fix in convert-ly,
which could insert a dummy
value for the argument. Note also that the extra argument wouldn't go
into define-markup-command
(where it doesn't make sense) but only into
define-builtin-markup-command, which normally shouldn't
be used in user files.
/Mats
_______________________________________________
lilypond-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
