> I think that having --preprocessor is feeping creaturitis, and I
> don't really see the point.
See example below.
> > PS: m4 seems to be suited well for preprocessing LilyPond input;
> > at least I've used it successfully.
>
> I tried a long time ago, and got barking mad from the strange
> quoting rules. Anyways, IMNSHO, Macro Languages Suck (tm).
Well, here is an example. Since you won't add variables to macros, I
*have* to use m4 or something similar to avoid extremely unreadable
ly files. Other suggestions how to handle this are highly welcome.
Werner
======================================================================
dnl change quote characters to [ and ] while defining macros
changequote([, ])
dnl change comment character to % (up to the newline)
changecom([%], [
])
define([TextVShift],
[\property Voice.TextScript \set #'extra-offset = #'(0 . $1)])
dnl use \ as an escape for macros
changesyntax([@\])
\dnl remove quote characters
\changequote(,)
< { \TextVShift(1) s1^"\\textbf{\\large Langsam}" } \\
R1 > |
_______________________________________________
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
