@menu
-* Suggestions for writing LilyPond input files::
-* When things don't work::
-* Scores and parts::
+* Suggestions for writing LilyPond input files::
+* When things don't work::
+* Scores and parts::
@end menu
@node Suggestions for writing LilyPond input files
@section Suggestions for writing LilyPond input files
-Now you're ready to begin writing larger LilyPond input files --
+Now you're ready to begin writing larger LilyPond input files --
not just the little examples in the tutorial, but whole pieces.
But how should you go about doing it?
@end itemize
@menu
-* General suggestions::
-* Typesetting existing music::
-* Large projects::
-* Saving typing with variables and functions::
-* Style sheets::
+* General suggestions::
+* Typesetting existing music::
+* Large projects::
+* Saving typing with variables and functions::
+* Style sheets::
@end menu
per line. Saving screen space by cramming eight bars per line just isn't
worth it if you have to @q{debug} your input files.
-@item @strong{Comment your input files}. Use either bar numbers
+@item @strong{Comment your input files}. Use either bar numbers
(every so often) or
references to musical themes (@q{second theme in violins,} @q{fourth
variation,} etc.). You may not need comments when you're writing the piece
@section When things don't work
@menu
-* Updating old input files::
-* Troubleshooting (taking it all apart)::
-* Minimal examples::
+* Updating old input files::
+* Troubleshooting (taking it all apart)::
+* Minimal examples::
@end menu
@node Updating old input files