Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > I wonder whether this should be changed too. This would mean that > > \clef alto > \clef "alto" > > becomes > > \clef #"alto" > > or > > \clef #'alto > > This will simplify the syntax a bit, at the expense ease of entry. > > What do you think?
I see some cases where this would be clearly a win. Few weeks ago, a singer asked me to change all alto clefs to treble clefs in a voice+piano reduction score. Just redefining the \clef music function would have made that really easy and quick. The more music functions there are, and the less hardcoded syntax is, the more extensible and flexible LilyPond is. Ideally, even \include should be some kind of (not only-)music function, so that users could define their own \include version (for including different files depending on some parameters for instance, or adding a path). BTW, Erik, weren't you investigating on a more flexible music function system, where for instance a "simple_string" argument could be used instead of a #"scheme-string"? (or maybe this is part of your thesis work). Nicolas _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
