Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(93)

Delta Between Two Patch Sets: Documentation/usage/running.itely

Issue 351850043: running.itely: Revise documentation of command line options.
Left Patch Set: More improvements. Created 5 years, 3 months ago
Right Patch Set: Another round of fixes. Created 5 years, 3 months ago
Left:
Right:
Use n/p to move between diff chunks; N/P to move between comments. Please Sign in to add in-line comments.
Jump to:
Left: Side by side diff | Download
Right: Side by side diff | Download
« no previous file with change/comment | « no previous file | no next file » | no next file with change/comment »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
LEFTRIGHT
1 @c -*- coding: utf-8; mode: texinfo; -*- 1 @c -*- coding: utf-8; mode: texinfo; -*-
2 2
3 @ignore 3 @ignore
4 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH 4 Translation of GIT committish: FILL-IN-HEAD-COMMITTISH
5 5
6 When revising a translation, copy the HEAD committish of the 6 When revising a translation, copy the HEAD committish of the
7 version that you are working on. For details, see the Contributors' 7 version that you are working on. For details, see the Contributors'
8 Guide, node Updating translation committishes.. 8 Guide, node Updating translation committishes..
9 @end ignore 9 @end ignore
10 10
(...skipping 55 matching lines...) Expand 10 before | Expand all | Expand 10 after
66 the command line. 66 the command line.
67 67
68 @example 68 @example
69 lilypond [@var{option}]@dots{} @var{file}@dots{} 69 lilypond [@var{option}]@dots{} @var{file}@dots{}
70 @end example 70 @end example
71 71
72 When invoked with a filename that has no extension, the @file{.ly} 72 When invoked with a filename that has no extension, the @file{.ly}
73 extension is tried first. To read input from stdin, use a 73 extension is tried first. To read input from stdin, use a
74 dash (@code{-}) for @var{file}. 74 dash (@code{-}) for @var{file}.
75 75
76 When @file{filename.ly} is processed it will produce @file{filename.ps} 76 When @file{filename.ly} is processed it produces @file{filename.ps}
77 and @file{filename.pdf} as output. Several files can be specified; 77 and @file{filename.pdf} as output. Several files can be specified;
78 they will each be processed independently. @footnote{The status of 78 they are each processed independently. @footnote{The status of
79 GUILE is not reset after processing a @code{.ly} file, so be careful 79 GUILE is not reset after processing a @file{.ly} file, so be careful
80 not to change any system defaults from within Scheme.} 80 not to change any system defaults from within Scheme.}
81 81
82 If @file{filename.ly} contains more than one @code{\book} 82 If @file{filename.ly} contains more than one @code{\book}
83 block, then the rest of the scores will be output in numbered files, 83 block, the rest of the scores is output in numbered files,
84 starting with @file{filename-1.pdf}. In addition, the value of 84 starting with @file{filename-1.pdf}. In addition, the value of
85 @code{output-suffix} will be inserted between the basename and the 85 @code{output-suffix} is inserted between the basename and the
86 number. An input file containing 86 number. For example, if @file{filename.ly} contains
87 87
88 @example 88 @example
89 #(define output-suffix "violin") 89 #(define output-suffix "violin")
90 \score @{ @dots{} @} 90 \score @{ @dots{} @}
91 #(define output-suffix "cello") 91 #(define output-suffix "cello")
92 \score @{ @dots{} @} 92 \score @{ @dots{} @}
93 @end example 93 @end example
94 94
95 @noindent 95 @noindent
96 will output @var{base}@file{-violin.pdf} and 96 LilyPond outputs @file{filename-violin.pdf} and
97 @var{base}@file{-cello-1.pdf}. 97 @file{filename-cello-1.pdf}.
98 98
99 99
100 @unnumberedsubsubsec Using LilyPond with standard shell features 100 @unnumberedsubsubsec Using LilyPond with standard shell features
101 101
102 Since LilyPond is a command line application, features of the @q{shell} 102 Since LilyPond is a command line application, features of the @q{shell}
103 used for calling LilyPond can also be put to good use. 103 used for calling LilyPond can also be put to good use.
104 104
105 For example, 105 For example,
106 106
107 @example 107 @example
108 lilypond *.ly 108 lilypond *.ly
109 @end example 109 @end example
110 110
111 @noindent 111 @noindent
112 will process all LilyPond files in the current directory. 112 processes all LilyPond files in the current directory.
113 113
114 Redirecting the console output (e.g. to a file) may also be useful: 114 Redirecting the console output (e.g. to a file) may also be useful:
115 115
116 @example 116 @example
117 lilypond file.ly 1> stdout.txt 117 lilypond file.ly 1> stdout.txt
118 118
119 lilypond file.ly 2> stderr.txt 119 lilypond file.ly 2> stderr.txt
120 120
121 lilypond file.ly &> all.txt 121 lilypond file.ly &> all.txt
122 @end example 122 @end example
123 123
124 @noindent 124 @noindent
125 The above commands divert @q{normal} output, @q{errors} only, or @q{everything}, 125 The above commands divert @q{normal} output, @q{errors} only, or @q{everything},
126 respectively, to text files. Consult the documentation for your 126 respectively, to text files. Consult the documentation for your
127 particular shell, Command (Windows), Terminal or Console 127 particular shell, Command (Windows), Terminal or Console
128 applications (MacOS X) to see if output redirection is supported or if 128 applications (MacOS X) to see if output redirection is supported or if
129 the syntax is different. 129 the syntax is different.
130 130
131 The following example searches and processes all input files in the 131 The following example searches and processes all input files in the
132 current directory and all directories below it recursively. The output 132 current directory and all directories below it recursively. The output
133 files will be located in the same directory that the command was run in, 133 files are located in the same directory that the command was run in,
134 rather than in the same directories as the original input files. 134 rather than in the same directories as the original input files.
135 135
136 @example 136 @example
137 find . -name '*.ly' -exec lilypond '@{@}' \; 137 find . -name '*.ly' -exec lilypond '@{@}' \;
138 @end example 138 @end example
139 139
140 @noindent 140 @noindent
141 This should also work for MacOS@tie{}X users. 141 This should also work for MacOS@tie{}X users.
142 142
143 A Windows user would run 143 A Windows user would run
(...skipping 26 matching lines...) Expand all
170 @node Basic command line options for LilyPond 170 @node Basic command line options for LilyPond
171 @unnumberedsubsec Basic command line options for LilyPond 171 @unnumberedsubsec Basic command line options for LilyPond
172 172
173 @cindex Invoking @command{lilypond} 173 @cindex Invoking @command{lilypond}
174 @cindex command line options for @command{lilypond} 174 @cindex command line options for @command{lilypond}
175 @cindex options, command line 175 @cindex options, command line
176 @cindex switches 176 @cindex switches
177 177
178 The following options are supported. 178 The following options are supported.
179 179
180 @table @code 180 @table @asis
181 181
182 @item -d, --define-default=@var{var}=@var{val} 182 @item @code{-d}, @code{--define-default=}@var{var}[@code{=}@var{val}]
183 See @ref{Advanced command line options for LilyPond}. 183 See @ref{Advanced command line options for LilyPond}.
184 184
185 @cindex Scheme, expression evaluation 185 @cindex Scheme, expression evaluation
186 @cindex expression evaluation, Scheme 186 @cindex expression evaluation, Scheme
187 187
188 @item -e, --evaluate=@var{expr} 188 @item @code{-e}, @code{--evaluate=}@var{expr}
189 Evaluate the Scheme @var{expr} before parsing any @file{.ly} files. 189 Evaluate the Scheme @var{expr} before parsing any @file{.ly} files.
190 Multiple @option{-e} options may be given, they will be evaluated 190 Multiple @option{-e} options may be given, they are evaluated
191 sequentially. 191 sequentially.
192 192
193 The expression will be evaluated in the @code{guile-user} module, so 193 The expression is evaluated in the @code{guile-user} module, so
194 if you want to use definitions in @var{expr}, use 194 if you want to use a definition like @code{(define-public a 42)} as
195 @var{expr}, use
195 196
196 @example 197 @example
197 lilypond -e '(define-public a 42)' 198 lilypond -e '(define-public a 42)'
198 @end example 199 @end example
199 200
200 @noindent 201 @noindent
201 on the command-line, and include 202 on the command-line, and include
202 203
203 @example 204 @example
204 #(use-modules (guile-user)) 205 #(use-modules (guile-user))
205 @end example 206 @end example
206 207
207 @noindent 208 @noindent
208 at the top of the @code{.ly} file. 209 at the top of the @file{.ly} file.
209 210
210 @warning{Windows users must use double quotes instead of single quotes.} 211 @warning{Windows users must use double quotes instead of single quotes.}
211 212
212 @item -E, --eps 213 @item @code{-E}, @code{--eps}
213 Generate EPS files. 214 Generate EPS files.
214 215
215 This option is equivalent to setting LilyPond's command line options 216 This option is equivalent to setting LilyPond's command line options
216 @code{--ps}, @code{-dbackend=eps}, and @code{-daux-files="#f"}. 217 @code{--ps}, @code{-dbackend=eps}, and @code{-daux-files='#f'}.
217 218
218 @cindex output, format 219 @cindex output, format
219 @cindex format, output 220 @cindex format, output
220 221
221 @item -f, --format=@var{format} 222 @item @code{-f}, @code{--format=}@var{format}
222 The format of the (main) output file or files. Possible values for 223 The format of the (main) output file or files. Possible values for
223 @var{format} are @code{ps}, @code{pdf}, or @code{png}. 224 @var{format} are @code{ps}, @code{pdf}, or @code{png}.
224 225
225 Example: @code{lilypond -fpng @var{filename}.ly} 226 Example: @code{lilypond -fpng foo.ly}
226 227
227 For @code{svg} and @code{eps} formats use the @code{-dbackend} option. 228 For @code{svg} and @code{eps} formats use the @code{-dbackend} option.
228 See @ref{Advanced command line options for LilyPond}. 229 See @ref{Advanced command line options for LilyPond}.
229 230
230 @item -h, --help 231 @item @code{-h}, @code{--help}
231 Show a summary of usage. 232 Show a summary of usage.
232 233
233 @item -H, --header=@var{field} 234 @item @code{-H}, @code{--header=}@var{field}
234 Dump a header field to file @file{BASENAME.@var{field}}. 235 Dump a header field to file @file{BASENAME.@var{field}}.
235 236
236 As an example, let's assume that you have an input file @file{foo.ly} 237 As an example, let's assume that you have an input file @file{foo.ly}
237 containing 238 containing
238 239
239 @example 240 @example
240 \header @{ title = "bar" @} 241 \header @{ title = "bar" @}
241 \score @{ c1 @} 242 \score @{ c1 @}
242 @end example 243 @end example
243 244
244 @noindent 245 @noindent
245 The command 246 The command
246 247
247 @example 248 @example
248 lilypond -H title foo.ly 249 lilypond -H title foo.ly
249 @end example 250 @end example
250 251
251 @noindent 252 @noindent
252 then creates a plain text file @file{foo.title} containing the string 253 then creates a plain text file @file{foo.title} containing the string
253 @code{bar}. 254 @code{bar}.
254 255
255 @item -i, --init=@var{file} 256 @item @code{-i}, @code{--init=}@var{file}
256 Set init file to @var{file} (default: @file{init.ly}). 257 Set init file to @var{file} (default: @file{init.ly}).
257 258
258 @cindex file searching 259 @cindex file searching
259 @cindex search path 260 @cindex search path
260 261
261 @item -I, --include=@var{directory} 262 @item @code{-I}, @code{--include=}@var{directory}
262 Append @var{directory} to the search path for input files with 263 Append @var{directory} to the search path for input files with
263 relative paths. By default, only the current working directory gets 264 relative paths. By default, only the current working directory gets
264 searched. 265 searched.
265 266
266 Multiple @option{-I} options may be given. The search will start in 267 Multiple @option{-I} options may be given. The search starts in
267 the current working directory, and if the file to be included is not 268 the current working directory, and if the file to be included is not
268 found the search will continue in the directory given by the first 269 found the search continues in the directory given by the first
269 @option{-I} option, then the directory in the second @option{-I} 270 @option{-I} option, then the directory in the second @option{-I}
270 option, and so on. 271 option, and so on.
271 272
272 @warning{Using the tilde character (@code{~}) with the @option{-I} 273 @warning{Using the tilde character (@code{~}) with the @option{-I}
273 switch may produce unexpected results in some shells. 274 switch may produce unexpected results in some shells.
274 275
275 Windows users will need to include a trailing slash for the directory's 276 Windows users need to include a trailing slash for the directory's
276 path.} 277 path.}
277 278
278 @cindex chroot jail, running inside 279 @cindex chroot jail, running inside
279 280
280 @item -j, --jail=@var{user},@var{group},@var{jail},@var{dir} 281 @item @code{-j}, @code{--jail=}@var{user}@code{,}@var{group}@code{,}@var{jail}@c ode{,}@var{dir}
281 [This option is only available if your operating system supports the 282 [This option is only available if your operating system supports the
282 @code{chroot} functionality. In particular, Windows doesn't support it.] 283 @code{chroot} functionality. In particular, Windows doesn't support it.]
283 284
284 Run @command{lilypond} in a chroot jail. 285 Run @command{lilypond} in a chroot jail.
285 286
286 The @option{--jail} option provides a more flexible alternative to 287 The @option{--jail} option provides a more flexible alternative to
287 @option{-dsafe}, when LilyPond formatting is being provided via a web 288 @option{-dsafe}, when LilyPond formatting is being provided via a web
288 server, or whenever LilyPond executes commands sent by external sources 289 server, or whenever LilyPond executes commands sent by external sources
289 (see @ref{Advanced command line options for LilyPond}). 290 (see @ref{Advanced command line options for LilyPond}).
290 291
291 It works by changing the root of @command{lilypond} to @var{jail} just 292 It works by changing the root of @command{lilypond} to @var{jail} just
292 before starting the actual compilation process. The user and group are 293 before starting the actual compilation process. The user and group are
293 then changed to match those provided, and the current directory is 294 then changed to match those provided, and the current directory is
294 changed to @var{dir}. This setup guarantees that it is not possible (at 295 changed to @var{dir}. This setup guarantees that it is not possible (at
295 least in theory) to escape from the jail. Note that for @option{--jail} 296 least in theory) to escape from the jail. Note that for @option{--jail}
296 to work, @command{lilypond} must be run as root, which is usually 297 to work, @command{lilypond} must be run as root, which is usually
297 accomplished in a safe way using @command{sudo}. 298 accomplished in a safe way using @command{sudo}.
298 299
299 Setting up a jail can be a relatively complex matter, as we must be sure 300 Setting up a jail can be a relatively complex matter, as we must be sure
300 that LilyPond is able to find whatever it needs to compile the source 301 that LilyPond is able to find whatever it needs to compile the source
301 @emph{inside} the jail itself. A typical chroot jail will comprise the 302 @emph{inside} the jail itself. A typical chroot jail comprises the
302 following steps: 303 following steps:
303 304
304 @table @asis 305 @table @asis
305 306
306 @item Setting up a separate filesystem 307 @item Setting up a separate filesystem
307 A separate filesystem should be created for LilyPond, so that it can be 308 A separate filesystem should be created for LilyPond, so that it can be
308 mounted with safe options such as @code{noexec}, @code{nodev}, and 309 mounted with safe options such as @code{noexec}, @code{nodev}, and
309 @code{nosuid}. In this way, it is impossible to run executables or to 310 @code{nosuid}. In this way, it is impossible to run executables or to
310 write directly to a device from LilyPond. If you do not want to create a 311 write directly to a device from LilyPond. If you do not want to create a
311 separate partition, just create a file of reasonable size and use it to 312 separate partition, just create a file of reasonable size and use it to
312 mount a loop device. A separate filesystem also guarantees that LilyPond 313 mount a loop device. A separate filesystem also guarantees that LilyPond
313 cannot write more space than it is allowed. 314 cannot write more space than it is allowed.
314 315
315 @item Setting up a separate user 316 @item Setting up a separate user
316 A separate user and group (say, @code{lily}/@code{lily}) with low 317 A separate user and group (say, @code{lily}/@code{lily}) with low
317 privileges should be used to run LilyPond inside the jail. There should 318 privileges should be used to run LilyPond inside the jail. There should
318 be a single directory writable by this user, which should be passed in 319 be a single directory writable by this user, which should be passed in
319 @var{dir}. 320 @var{dir}.
320 321
321 @item Preparing the jail 322 @item Preparing the jail
322 LilyPond needs to read a number of files while running. All these files 323 LilyPond needs to read a number of files while running. All these files
323 are to be copied into the jail, under the same path they appear in the 324 are to be copied into the jail, under the same path they appear in the
324 real root filesystem. The entire content of the LilyPond installation 325 real root filesystem. The entire content of the LilyPond installation
325 (e.g., @file{/usr/share/lilypond}) should be copied. 326 (e.g., @file{/usr/share/lilypond}) should be copied.
326 327
327 If problems arise, the simplest way to trace them down is to run 328 If problems arise, the simplest way to trace them down is to run
328 LilyPond using @command{strace}, which will allow you to determine which 329 LilyPond using @command{strace}, which allows you to determine which
329 files are missing. 330 files are missing.
330 331
331 @item Running LilyPond 332 @item Running LilyPond
332 In a jail mounted with @code{noexec} it is impossible to execute any 333 In a jail mounted with @code{noexec} it is impossible to execute any
333 external program. Therefore LilyPond must be run with a backend that 334 external program. Therefore LilyPond must be run with a backend that
334 does not require any such program. As we have already mentioned, it 335 does not require any such program. As we have already mentioned, it
335 must be run with superuser privileges (which, of course, it will lose 336 must be run with superuser privileges (which, of course, it loses
336 immediately), possibly using @command{sudo}. It is also good practice 337 immediately), possibly using @command{sudo}. It is also good practice
337 to limit the number of seconds of CPU time LilyPond can use (e.g., using 338 to limit the number of seconds of CPU time LilyPond can use (e.g., using
338 @command{ulimit@tie{}-t}), and, if your operating system supports it, 339 @command{ulimit@tie{}-t}), and, if your operating system supports it,
339 the amount of memory that can be allocated. Also see 340 the amount of memory that can be allocated. Also see
340 @ref{LilyPond in chroot jail}. 341 @ref{LilyPond in chroot jail}.
341 @end table 342 @end table
342 343
343 @cindex loglevel 344 @cindex loglevel
344 @cindex output, verbosity 345 @cindex output, verbosity
345 346
346 @item -l, --loglevel=@var{level} 347 @item @code{-l}, @code{--loglevel=}@var{level}
347 Set the verbosity of the console output to @var{level}. Possible values 348 Set the verbosity of the console output to @var{level}. Possible values
348 are: 349 are:
349 350
350 @table @code 351 @table @code
351 352
352 @item NONE 353 @item NONE
353 No output at all, not even error messages. 354 No output at all, not even error messages.
354 355
355 @item ERROR 356 @item ERROR
356 Only error messages, no warnings or progress messages. 357 Only error messages, no warnings or progress messages.
(...skipping 13 matching lines...) Expand all
370 371
371 @item DEBUG 372 @item DEBUG
372 All possible messages, including verbose debug output. 373 All possible messages, including verbose debug output.
373 374
374 @end table 375 @end table
375 376
376 @cindex directory, redirect output 377 @cindex directory, redirect output
377 @cindex output, setting filename 378 @cindex output, setting filename
378 @cindex output, directory 379 @cindex output, directory
379 380
380 @item -o, --output=@var{file} 381 @item @code{-o}, @code{--output=}@var{file}
381 @itemx -o, --output=@var{folder} 382 @itemx @code{-o}, @code{--output=}@var{folder}
382 Set the default output file to @var{file} or, if a folder with that name 383 Set the default output file to @var{file} or, if a folder with that name
383 exists, direct the output to @var{folder}, taking the file name from the 384 exists, direct the output to @var{folder}, taking the file name from the
384 input file. The appropriate suffix will be added (e.g., @code{.pdf} for 385 input file. The appropriate suffix is added (e.g., @file{.pdf} for
385 PDF) in both cases. 386 PDF) in both cases.
386 387
387 @item -O, --pspdfopt=@var{key} 388 @item @code{-O}, @code{--pspdfopt=}@var{key}
388 @cindex pspdfopt 389 @cindex pspdfopt
389 390
390 Set the PS/PDF output optimization to @var{key}. Possible values are: 391 Set the PS/PDF output optimization to @var{key}. Possible values are:
391 392
392 @table @code 393 @table @code
393 394
394 @item size 395 @item size
395 Generate a very small PS/EPS/PDF document. This is the default. 396 Generate a very small PS/EPS/PDF document. This is the default.
396 397
397 Using this value is equivalent to setting LilyPond's Scheme command 398 Using this value is equivalent to setting LilyPond's Scheme command
398 line options @code{-dmusic-@/font-@/encodings=@/"#f"} and 399 line options @code{-dmusic-@/font-@/encodings=@/'#f'} and
399 @code{-dgs-@/never-@/embed-@/fonts=@/"#f"}. 400 @code{-dgs-@/never-@/embed-@/fonts=@/'#f'}.
400 401
401 @item TeX 402 @item TeX
402 Produce files that are optimized for inclusion in pdfTeX, luatex, or 403 Produce files that are optimized for inclusion in pdfTeX, luatex, or
403 XeTeX documents. 404 XeTeX documents.
404 405
405 Using this value is equivalent to setting LilyPond's Scheme command 406 Using this value is equivalent to setting LilyPond's Scheme command
406 line options @code{-dmusic-@/font-@/encodings=@/"#t"} and 407 line options @code{-dmusic-@/font-@/encodings=@/'#t'} and
407 @code{-dgs-@/never-@/embed-@/fonts=@/"#f"}. 408 @code{-dgs-@/never-@/embed-@/fonts=@/'#f'}.
408 409
409 @item TeX-GS 410 @item TeX-GS
410 If you want to include more than one PDF generated by LilyPond in a 411 If you want to include more than one PDF generated by LilyPond in a
411 TeX document, use this option and postprocess the PDF generated by 412 TeX document, use this option and postprocess the PDF generated by
412 TeX with ghostscript. 413 TeX with Ghostscript.
413 414
414 Using this value is equivalent to setting LilyPond's Scheme command 415 Using this value is equivalent to setting LilyPond's Scheme command
415 line options @code{-dmusic-@/font-@/encodings=@/"#t"} and 416 line options @code{-dmusic-@/font-@/encodings=@/'#t'} and
416 @code{-dgs-@/never-@/embed-@/fonts=@/"#t"}. 417 @code{-dgs-@/never-@/embed-@/fonts=@/'#t'}.
417 418
418 @end table 419 @end table
419 420
420 @cindex PS (Postscript), output 421 @cindex PS (PostScript), output
421 @cindex Postscript (PS), output 422 @cindex PostScript (PS), output
422 @cindex output, PS (Postscript) 423 @cindex output, PS (PostScript)
423 424
424 @item --ps 425 @item @code{--ps}
425 Generate PostScript. This option is equivalent to @code{-fps}. 426 Generate PostScript. This option is equivalent to @code{-fps}.
426 427
427 @cindex PNG (Portable Network Graphics), output 428 @cindex PNG (Portable Network Graphics), output
428 @cindex output, PNG (Portable Network Graphics) 429 @cindex output, PNG (Portable Network Graphics)
429 430
430 @item --png 431 @item @code{--png}
431 Generate pictures of each page, in PNG format. This option is 432 Generate pictures of each page, in PNG format. This option is
432 equivalent to @code{-fpng}; it implies @option{--ps}. 433 equivalent to @code{-fpng}; it implies @option{--ps}.
433 434
434 The resolution in DPI of the image may be set with 435 The resolution of the image may be set to @var{N}@tie{}DPI with
435 @example 436 @example
436 -dresolution=110 437 -dresolution=@var{N}
437 @end example 438 @end example
438 439
439 @cindex PDF (Portable Document Format), output 440 @cindex PDF (Portable Document Format), output
440 @cindex output, PDF (Portable Document Format) 441 @cindex output, PDF (Portable Document Format)
441 442
442 @item --pdf 443 @item @code{--pdf}
443 Generate PDF. This is the default, being equivalent to @code{-fpdf}. 444 Generate PDF. This is the default, being equivalent to @code{-fpdf}.
444 It implies @option{--ps}. 445 It implies @option{--ps}.
445 446
446 @item -s, --silent 447 @item @code{-s}, @code{--silent}
447 Show no progress, only error messages. This is equivalent to 448 Show no progress, only error messages. This is equivalent to
448 @code{-lERROR}. 449 @code{-lERROR}.
449 450
450 @item -v, --version 451 @item @code{-v}, @code{--version}
451 Show version information. 452 Show version information.
452 453
453 @item -V, --verbose 454 @item @code{-V}, @code{--verbose}
454 Be verbose: show full paths of all files read, give timing 455 Be verbose: show full paths of all files read, give timing
455 information, etc. It is equivalent to @code{-lDEBUG}. 456 information, etc. It is equivalent to @code{-lDEBUG}.
456 457
457 @item -w, --warranty 458 @item @code{-w}, @code{--warranty}
458 Show the warranty with which GNU LilyPond comes. (It comes with 459 Show the warranty with which GNU LilyPond comes. (It comes with
459 @strong{NO WARRANTY}!) 460 @strong{NO WARRANTY}!)
460 461
461 @end table 462 @end table
462 463
463 464
464 @node Advanced command line options for LilyPond 465 @node Advanced command line options for LilyPond
465 @unnumberedsubsec Advanced command line options for LilyPond 466 @unnumberedsubsec Advanced command line options for LilyPond
466 467
467 @table @code 468 @table @code
(...skipping 804 matching lines...) Expand 10 before | Expand all | Expand 10 after
1272 visible shift for notes with stems, but whole notes are not visibly 1273 visible shift for notes with stems, but whole notes are not visibly
1273 shifted unless an actual clash of the note heads occurs, or when the 1274 shifted unless an actual clash of the note heads occurs, or when the
1274 voices cross over from their natural order (when @code{\voiceThree} 1275 voices cross over from their natural order (when @code{\voiceThree}
1275 is higher than @code{\voiceOne}, etc.) 1276 is higher than @code{\voiceOne}, etc.)
1276 1277
1277 @seealso 1278 @seealso
1278 @rlearning{Explicitly instantiating voices}, 1279 @rlearning{Explicitly instantiating voices},
1279 @rlearning{Real music example}, 1280 @rlearning{Real music example},
1280 @ruser{Single-staff polyphony}, 1281 @ruser{Single-staff polyphony},
1281 @ruser{Collision resolution}. 1282 @ruser{Collision resolution}.
LEFTRIGHT
« no previous file | no next file » | Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Toggle Comments ('s')

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b