On Tue, Jul 28, 2009 at 01:19:46PM +0100, Trevor Daniels wrote: > > Graham Percival wrote Tuesday, July 28, 2009 12:13 AM > >> Those are not predefined commands -- predefined commands are for >> predefined tweaks. Those commands are basic lilypond commands. >> (I suppose we might rename @predef to be "predefined tweaks" >> rather than commands... Trevor, any thoughts?) > > With hindsight "predefined tweaks" would have > been a better name. It's easy to change the > macro, but the term "predefined commands" is > used quite extensively in the text.
I just searched for "redefined" (catching any capitalization), and didn't find many instances of n...@predefined. > It might be just about safe to do a global change on all the > .itely files. If you'd like to do this I could check the commit > to make sure no damage has been done. I think this would be a good idea. > Another thought. Should we find a naming convention as part of > LSD that distinguishes commands from predefined tweaks? Most > commands seem to be single words and most predefined tweaks seem > to be camel-case multiple words. Could this be made a > convention? That's a nice idea... it's definitely worth discussing during LSD. Although I've come up with a better name: GLISS, the Grand Lilypond Input Syntax Standardization. It's even music-related! Cheers, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
