@menu
* Invoking lilypond::
-* Command line options::
+* Command line options for lilypond::
* Environment variables::
@end menu
@node Invoking lilypond
-@subsection Invoking lilypond
+@subsection Invoking @command{lilypond}
-@cindex Invoking LilyPond
-@cindex command line options
+@cindex Invoking @command{lilypond}
+@cindex command line options for @command{lilypond}
@cindex options, command line
@cindex switches
@var{base}@file{-cello-1.pdf}.
-@node Command line options
-@subsection Command line options
+@node Command line options for lilypond
+@subsection Command line options for @command{lilypond}
The following options are supported:
@noindent
Note that the string must be enclosed in escaped quotes ( @code{\"} ).
-
+@c Match " in previous line to help context-sensitive editors
@item safe
Do not trust the @code{.ly} input.
@node Updating files with convert-ly
-@section Updating with @command{convert-ly}
+@section Updating files with @command{convert-ly}
@cindex Updating a LilyPond file
@cindex convert-ly
If there are no changes to myfile.ly and file called myfile.ly.NEW
is created, then myfile.ly is already updated.
-@subsection Command line options
+@menu
+* Command line options for convert-ly::
+* Problems with convert-ly::
+@end menu
+
+@node Command line options for convert-ly
+@subsection Command line options for @command{convert-ly}
@command{convert-ly} always converts up to the last syntax change handled by
it. This means that the @code{\version} number left in the file is
@end table
-@menu
-* Problems with convert-ly::
-@end menu
-
-
@node Problems with convert-ly
@subsection Problems with @code{convert-ly}