Guide, node Updating translation committishes..
@end ignore
-@c \version "2.13.36"
+@c \version "2.14.0"
@node Running lilypond
@end example
-When invoked with a filename that has no extension, the @file{@/.ly}
+When invoked with a filename that has no extension, the @file{.ly}
extension is tried first. To read input from stdin, use a
dash (@code{-}) for @var{file}.
-When @file{filename@/.ly} is processed it will produce @file{filename@/.ps}
-and @file{filename@/.pdf} as output. Several files can be specified;
+When @file{filename.ly} is processed it will produce @file{filename.ps}
+and @file{filename.pdf} as output. Several files can be specified;
they will each be processed independently. @footnote{The status of
GUILE is not reset after processing a @code{.ly} file, so be careful
not to change any system defaults from within Scheme.}
-If @file{filename@/.ly} contains more than one @code{\book}
+If @file{filename.ly} contains more than one @code{\book}
block, then the rest of the scores will be output in numbered files,
-starting with @file{filename@/-1@/.pdf}. In addition, the value of
+starting with @file{filename-1.pdf}. In addition, the value of
@code{output-suffix} will be inserted between the basename and the
number. An input file containing
@end example
@noindent
-will output @var{base}@file{@/-violin@/.pdf} and
-@var{base}@file{@/-cello@/-1@/.pdf}.
+will output @var{base}@file{-violin.pdf} and
+@var{base}@file{-cello-1.pdf}.
@unnumberedsubsubsec Standard shell commands
@table @code
@item -e,--evaluate=@var{expr}
-Evaluate the Scheme @var{expr} before parsing any @file{@/.ly} files.
+Evaluate the Scheme @var{expr} before parsing any @file{.ly} files.
Multiple @code{-e} options may be given, they will be evaluated
sequentially.
The @code{-dsafe} option works by evaluating in-line Scheme
expressions in a special safe module. This safe module is derived from
-GUILE @file{safe@/-r5rs} module, but adds a number of functions of the
-LilyPond API. These functions are listed in @file{scm/@/safe@/-lily@/.scm}.
+GUILE @file{safe-r5rs} module, but adds a number of functions of the
+LilyPond API. These functions are listed in @file{scm/safe-lily.scm}.
In addition, safe mode disallows @code{\include} directives and
disables the use of backslashes in @TeX{} strings.
Schoolbook fonts, included with your LilyPond installation, for
optimal rendering. Under UNIX, simply copy these fonts from the
LilyPond directory (typically
- @file{/@/usr/@/share/@/lilypond/@/VERSION/@/fonts/@/otf/@/}) to
- @file{@/~/@/@/.fonts/@/}. The SVG output should be compatible with any
+ @file{/usr/share/lilypond/VERSION/fonts/otf/}) to
+ @file{~/.fonts/}. The SVG output should be compatible with any
SVG editor or user agent.
@item scm
The @code{ps}, @code{eps}, and @code{svg} backends support this
option.
+@item gui
+Runs silently and redirect all output to a log file.
+
+Note to Windows users: By default @code{lilypond.exe} outputs all
+progress information to the command window, @code{lilypond-windows.exe}
+does not and returns a prompt, with no progress information, immediately
+at the command line. The @code{-dgui} option can be used in this case
+to redirect output to a log file.
+
+
@item print-pages
Generate the full pages, the default. @code{-dno-print-pages} is
useful in combination with @code{-dpreview}.
found the search will continue in subsequent directories.
@item -i,--init=@var{file}
-Set init file to @var{file} (default: @file{init@/.ly}).
+Set init file to @var{file} (default: @file{init.ly}).
+
+@cindex loglevel
+@cindex output verbosity, setting
+
+@item -l,--loglevel=@var{LEVEL}
+Set the verbosity of the console output to @var{LEVEL}. Possible values are:
+@table @code
+@item NONE
+No output at all, not even error messages.
+
+@item ERROR
+Only error messages, no warnings or progress messages.
+
+@item WARN
+Warnings and error messages, no progress.
+
+@item BASIC_PROGRESS
+Basic progress messages (success), warnings and errors.
+
+@item PROGRESS (default)
+All progress messages, warnings and errors.
+
+@item DEBUG
+All possible messages, including verbose debug output.
+@end table
+
@cindex folder, directing output to
@cindex output filename, setting
LilyPond needs to read a number of files while running. All these files
are to be copied into the jail, under the same path they appear in the
real root filesystem. The entire content of the LilyPond installation
-(e.g., @file{/@/usr/@/share/@/lilypond})
+(e.g., @file{/usr/share/lilypond})
should be copied.
If problems arise, the simplest way to trace them down is to run
@item LILYPOND_DATADIR
This specifies a directory where locale messages and
data files will be looked up by default. The directory should contain
-subdirectories called @file{ly/@/}, @file{ps/@/}, @file{tex/@/}, etc.
+subdirectories called @file{ly/}, @file{ps/}, @file{tex/}, etc.
@item LANG
This selects the language for the warning messages.
+@item LILYPOND_LOGLEVEL
+The default loglevel. If LilyPond is called without an explicit loglevel (i.e.
+no @code{--loglevel} command line option), this value is used.
+
@item LILYPOND_GC_YIELD
-With this variable the memory footprint and performance can be
-adjusted. It is a percentage tunes memory management behavior. With
-higher values, the program uses more memory, with smaller values, it
-uses more CPU time. The default value is @code{70}.
+A variable, as a percentage, that tunes memory management
+behavior. A higher values means the program uses more memory, a
+smaller value means more CPU time is used. The default value is
+@code{70}.
@end table
@unnumberedsubsec Apparent error in @code{../ly/init.ly}
Various obscure error messages may appear about syntax errors in
-@file{@/.@/./@/ly/@/init@/.ly} if the input file is not correctly formed,
+@file{../ly/init.ly} if the input file is not correctly formed,
for example, if it does not contain correctly
matched braces or quote signs.