David Kastrup <d...@gnu.org> writes: > Nicolas Sceaux <nicolas.sce...@gmail.com> writes: > >> I'd be insterested to see an implementation of a single >> `define-markup-command' for builtin and user defined markups, where >> user defined commands do not pollute the (lily) module, and still are >> available across file includes. >> >> If you can come up with one, fine, I'm not opposed to #:property or >> #:category keywords. But if that's not possible, then please stop with >> this macro unification debate. IMHO it's just waisting time, for this >> is not a problem that you're trying to solve, but at most a little >> inconvenience. > >> PS: *please*, call things by there name, it's "builtin", not >> "internal". > > Wouldn't it be worth it alone to do this change because of not having to > get annoyed time and again by me confusing the two? > > I'll see whether I can cook up a suitable patch.
Done. The current state of <URL:http://codereview.appspot.com/160048> (Patchset 4) removes *-builtin-* completely and appears to pass all tests. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
