On Thu, 17 Apr 2008 19:09:35 +0200 "Valentin Villenave" <[EMAIL PROTECTED]> wrote:
> OK. Graham, I did implement something that could be useful -- or not. > It's not very elegant, but at least it doesn't break anything. > > Here's what it looks like (look at the appendix): > http://valentin.villenave.info/lilypond/Documentation/user/lilypond/index.html Mao, that looks sexy. I could kiss you. I can't wait until we get a few more examples from Neil to add to it... Neil, feel free to send an update before you've finished the whole thing. I want to see how it looks. :) Keep the "global markup commands", although maybe rename it to "all markup commands" or something like that. Some people (I'm thinking of Trevor) will want to Get rid of the patch to text.itely from your patch. It has nothing to do with the internal markup rearrangement. > Right now, this implementation is not elegant at all. The best > solution would have been to modify the define-builtin-mrkup-command > itself, to make it take the categories as an argument (in some way, to > "tag" the markup commands as we do for LSR snippets). Yes, definitely. Creating separate define-graphic-markup... commands (and marking everything in define-markup-commands.scm with them!) was a waste of time. > The reason why I > didn't do it is ( because I'm an ignoramus and) because this could > break compatibility at some points: if a command is defined without a > markup-category, I don't know how to handle this situation. >From a general programming standpoint, these are called "optional arguments". 20 seconds of googling seems to show that scheme supports this; for examle: http://www.cs.aau.dk/~normark/prog3-03/html/notes/fu-intr-1-note-optpar1.html Set the default value of the "category" variable to "unsorted". Hmm... actually, that might get awkward with notation-appendices. OK, set it to "other" for now; this list will be short enough that we can spot "other" commands that shouldn't be in that category. Cheers, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
