* Documentation/user/lilypond-book.itely: small cleanups

[lilypond.git] / Documentation / user / invoking.itexi

diff --git a/Documentation/user/invoking.itexi b/Documentation/user/invoking.itexi
index e8b7699644a1b8fdc1e390e50d6f13b5cb7cda55..67bafae06f01d3064498e207aa2d92177cbee82c 100644 (file)
--- a/Documentation/user/invoking.itexi
+++ b/Documentation/user/invoking.itexi
@@ -3,9 +3,9 @@
 @chapter Invoking LilyPond
 
 @menu
-* Reporting bugs::             
-* Website::                    
-* Titling LilyPond scores::    
+* Reporting bugs::              
+* Website::                     
+* Invoking ly2dvi::           Titling LilyPond scores.
 @end menu
 
 @cindex Invoking LilyPond
@@ -20,7 +20,6 @@ Usage:
 @end example
 
 
-
 When invoked with a filename that has no extension, LilyPond will try
 to add @file{.ly} as an extension first.  To have LilyPond read from
 stdin, use a dash @code{-} for @var{file}.
@@ -41,13 +40,12 @@ The following options are supported:
 
 @table @code
 
-@item -e,--evaluate=@var{code}
-  Evaluates the Scheme @var{code} before parsing @file{.ly}
-files. Multiple @code{-e} options may be given. They will be evaluated
-sequentially. The function @code{set-lily-option} may be invoked to
-set various debugging options.
-
-
+@item -e,--evaluate=@var{expr}
+Evaluate the Scheme @var{expr} before parsing any @file{.ly} files.
+Multiple @code{-e} options may be given, they will be evaluated
+sequentially.  The function @code{ly-set-option} allows for access to
+some internal variables.  Use @code{-e '(ly-option-usage')} for more
+information.
 
 @item -f,--format=@var{format}
 @c
@@ -112,12 +110,18 @@ Show the warranty with which GNU LilyPond comes. (It comes with
 
 
 For processing both the @TeX{} and the PostScript output, you must
-have appropriate environment variables set.  Scripts to do this are
-included in @file{buildscripts/out/lilypond-profile} (for sh shells)
-and @file{buildscripts/out/lilypond-login} (for C-shells), and should
-normally be sourced as part of your login process. If these scripts
-are not run from the system wide login process, then you must run it
-yourself.
+have appropriate environment variables set.  The following scripts  do
+this:
+
+@itemize @bullet
+@item @file{buildscripts/out/lilypond-profile}
+(for sh shells)
+@item  @file{buildscripts/out/lilypond-login} (for C-shells)
+@end itemize
+
+They should normally be sourced as part of your login process. If
+these scripts are not run from the system wide login process, then you
+must run it yourself.
 
 @cindex installing LilyPond
 
@@ -226,20 +230,19 @@ website contains updates to the manual. You can find the lilypond
 website at @uref{http://www.lilypond.org/}.
 
 
-@node Titling LilyPond scores
-@section Titling LilyPond scores
+@node Invoking ly2dvi
+@section Invoking ly2dvi
 
 Nicely titled output is created through a separate program:
 @file{ly2dvi} is a script that uses LilyPond and La@TeX{} to create a
 nicely titled piece of sheet music, in DVI format or PostScript.
 
-@subsection Invoking ly2dvi
-
-@c ly2dvi needs at least one FILE, can't act as filter yet
 @example
         ly2dvi [@var{option}]@dots{} @var{file}@dots{}
 @end example
 
+To have ly2dvi read from stdin, use a dash @code{-} for @var{file}.
+
 Ly2dvi supports the following options:
 
 @table @code
@@ -261,8 +264,8 @@ files. The temporary directory is created in the current directory as @code{ly2d
 @item -P,--postscript
     Also generate PostScript output, using dvips.  The postscript uses
 the standard @TeX{} bitmap fonts for your printer.
-@item --pdf
-    Also generate Portable Document Format (PDF). This option will
+@item -p,--pdf
+    Also generate Portable Document Format (PDF).  This option will
 generate a PS file using scalable fonts, and will run the PS file
 through @code{ps2pdf} producing a PDF file.