Left: | ||
Right: |
OLD | NEW |
---|---|
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 |
11 @c \version "2.17.6" | 11 @c \version "2.17.6" |
12 | 12 |
13 | 13 |
14 @node Running lilypond | 14 @node Running lilypond |
15 @chapter Running @command{lilypond} | 15 @chapter Running @command{lilypond} |
16 | 16 |
17 This chapter details the technicalities of running LilyPond. | 17 If you have not done so already, please read the @rlearning{Tutorial} |
18 first. | |
18 | 19 |
19 @menu | 20 @menu |
20 * Normal usage:: | 21 * Using a GUI to run LilyPond:: |
21 * Command-line usage:: | 22 * Using the command-line:: |
22 * Error messages:: | 23 * Error messages:: |
23 * Common errors:: | 24 * Common errors:: |
24 @end menu | 25 @end menu |
25 | 26 |
26 | 27 |
27 @node Normal usage | 28 @node Using a GUI to run LilyPond |
28 @section Normal usage | 29 @section Using a GUI to run LilyPond |
29 | 30 |
30 Most users run LilyPond through a GUI; if you have not done so | 31 Many users run LilyPond via @q{Front-end Applications} that provide a |
31 already, please read the @rlearning{Tutorial}. If you use an alternate | 32 convenient and simple-to-use GUI. These still require that LilyPond is |
Trevor Daniels
2015/09/21 22:12:05
"... require LilyPond to be installed ..." would b
| |
32 editor to write lilypond files, see the documentation for that | 33 installed separately on your computer. There are also some |
33 program. | 34 browser-based editors available that do not require LilyPond to be |
35 installed on your computer. See @rweb{Easier editing} for more | |
36 information on where to download these applications. | |
34 | 37 |
35 | 38 |
36 @node Command-line usage | 39 @node Using the command-line |
37 @section Command-line usage | 40 @section Using the command-line |
38 | 41 |
39 This section contains extra information about using LilyPond on the | 42 Running LilyPond directly in the command-line allows for many more |
40 command-line. This may be desirable to pass extra options to the | 43 configurable options to be applied to the output. LilyPond also comes |
pwm
2015/09/14 15:13:13
Since Frescobaldi has an "Engrave (custom)" functi
pkx166h
2015/09/21 21:27:50
Done.
| |
41 program. In addition, there are certain extra @q{helper} programs (such | 44 with additional @q{helper} programs (e.g. @code{midi2ly}, @code{abc2ly}, |
42 as @code{midi2ly}) which are only available on the command-line. | 45 @code{lilypond-book}, @code{convert-ly} etc.) which are usually only |
46 available via the command-line. | |
pwm
2015/09/14 15:13:13
Since these helper programs are also available in
pkx166h
2015/09/21 21:27:50
Done.
| |
43 | 47 |
44 By @q{command-line}, we mean the command line in the operating system. | 48 For Linux and BSD users, this applies to running LilyPond in any |
45 Windows users might be more familiar with the terms @q{DOS shell} or | 49 @q{Terminal} program. |
46 @q{command shell}. MacOS@tie{}X users might be more familiar with the terms | |
47 @q{terminal} or @q{console}. Some additional setup is required | |
48 for MacOS@tie{}X users; please see @rweb{MacOS X}. | |
49 | 50 |
50 Describing how to use this part of an operating system is outside the | 51 For Windows users, this applies to running LilyPond in the @q{command} |
51 scope of this manual; please consult other documentation on this topic | 52 (or @q{cmd}) window. Some additional setup is required for Windows |
52 if you are unfamiliar with the command-line. | 53 users before being able to use LilyPond on the command-line; please see |
54 the section @q{Running on the command-line} from here; @rweb{Windows}. | |
Trevor Daniels
2015/09/21 22:12:05
From here: (should be a colon). Same in following
| |
55 | |
56 For MacOS users, this applies to running LilyPond in either the | |
57 @code{terminal} or @code{console} applications. Some additional setup | |
58 is required for MacOS users before being able to use LilyPond on the | |
59 command-line; please see the section @q{Running on the command-line} | |
60 from here; @rweb{MacOS X}. | |
61 | |
62 Describing how to configure and use each operating system's command-line | |
63 program is outside the scope of this manual. Please consult the | |
64 appropriate documentation (or help-files) for your operating system if | |
65 you are unfamiliar with using the command-line. | |
53 | 66 |
54 @menu | 67 @menu |
55 * Invoking LilyPond:: | 68 * Invoking LilyPond:: |
56 * Basic command line options for LilyPond:: | 69 * Basic command line options for LilyPond:: |
57 * Advanced command line options for LilyPond:: | 70 * Advanced command line options for LilyPond:: |
58 * Environment variables:: | 71 * Environment variables:: |
59 * LilyPond in chroot jail:: | 72 * LilyPond in chroot jail:: |
60 @end menu | 73 @end menu |
61 | 74 |
62 @node Invoking LilyPond | 75 @node Invoking LilyPond |
(...skipping 1129 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
1192 visible shift for notes with stems, but whole notes are not visibly | 1205 visible shift for notes with stems, but whole notes are not visibly |
1193 shifted unless an actual clash of the note heads occurs, or when the | 1206 shifted unless an actual clash of the note heads occurs, or when the |
1194 voices cross over from their natural order (when @code{\voiceThree} | 1207 voices cross over from their natural order (when @code{\voiceThree} |
1195 is higher than @code{\voiceOne}, etc.) | 1208 is higher than @code{\voiceOne}, etc.) |
1196 | 1209 |
1197 @seealso | 1210 @seealso |
1198 @rlearning{Explicitly instantiating voices}, | 1211 @rlearning{Explicitly instantiating voices}, |
1199 @rlearning{Real music example}, | 1212 @rlearning{Real music example}, |
1200 @ruser{Single-staff polyphony}, | 1213 @ruser{Single-staff polyphony}, |
1201 @ruser{Collision resolution}. | 1214 @ruser{Collision resolution}. |
OLD | NEW |