Yes, that's a good idea. It would have helped me much when I just started to learn LilyPond. This would be also useful to review my template generator template (aka document wizard) and apply conventions that can be called 'official'. (However I must note that using lily4jedit's document wizard generating any score in the structure of these templates is approximately takes 10 seconds :-) )
The question of an "official" LilyPond style comes up every so often. (ie something like "always begin with a \version string, then the \headers. Violinx should be written as violinOne, violinTwo, etc")
I used to like the idea, but now I've moved into the "don't care; do whatever
you want, as long as it compiles" camp. However, if there was interest
in it, I wouldn't mind including a section on "official" templates / style
stuff. With a note that these are suggestions; like all coding styles, there's
no real "right" answer. (apart from two-space tabs. That's definitely the
right answer. ;)
Anyway, shall I bring this up on lilypond-user? Or is there some reason why
the Lilypond Project doesn't want to include Official Style Guidelines (tm) ?
Cheers, - Graham
_______________________________________________ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
