-In addition, LilyPond input is @strong{case sensitive}. @code{ @{ c d e @} }
-is valid input; @code{ @{ C D E @} } will produce an error message.
+In addition, LilyPond input is @strong{case sensitive}. @code{ @{c d e @}}
+is valid input; @code{@{ C D E @}} will produce an error message.
file. Save it, for example, to @file{test.ly} on your Desktop, and
then process it with the menu command @samp{Compile > Typeset File}.
The resulting PDF file will be displayed on your screen.
file. Save it, for example, to @file{test.ly} on your Desktop, and
then process it with the menu command @samp{Compile > Typeset File}.
The resulting PDF file will be displayed on your screen.
or two because all of the system fonts have to be analyzed first.
For future use of LilyPond, you should begin by selecting @q{New}
or two because all of the system fonts have to be analyzed first.
For future use of LilyPond, you should begin by selecting @q{New}
has done to the file. If any errors occur, please examine this file.
Note that there are several other text editors available, with better
has done to the file. If any errors occur, please examine this file.
Note that there are several other text editors available, with better
is a @code{LilyPond-mode} for Emacs addicts. If they have not been
installed already, refer to the file @file{INSTALL.txt}. The
easiest editing environment is @file{LilyPondTool}. See
is a @code{LilyPond-mode} for Emacs addicts. If they have not been
installed already, refer to the file @file{INSTALL.txt}. The
easiest editing environment is @file{LilyPondTool}. See
-LilyPond input files are treated like files in most programming languages:
-they are case sensitive, white-space insensitive, expressions are
+LilyPond input files are similar to source files in many common programming languages.
+They are case sensitive, and white-space is generally equivalent. Expressions are
If the previous sentence sounds like nonsense, don't worry! We'll explain
what all these terms mean:
If the previous sentence sounds like nonsense, don't worry! We'll explain
what all these terms mean:
@item @strong{Case sensitive}:
it matters whether you enter a letter
in lower case (i.e. @code{a, b, s, t}) or upper case (i.e.
@item @strong{Case sensitive}:
it matters whether you enter a letter
in lower case (i.e. @code{a, b, s, t}) or upper case (i.e.
-@code{A, B, S, T}). Notes are lower case: @code{ @{ c d e @} }
-is valid input; @code{ @{ C D E @} } will produce an error message.
+@code{A, B, S, T}). Notes are lower case: @code{@{ c d e @}}
+is valid input; @code{@{ C D E @}} will produce an error message.
-spaces (or new lines) you add. @code{ @{ c d e @}} means the same thing
-as @code{ @{ c @tie{} @tie{} @tie{} d e @} } and
+spaces (or new lines) you add. @code{@{ c d e @}} means the same thing
+as @code{@{ c @tie{} @tie{} @tie{} d e @}} and
introduces a line comment; anything after @samp{%} on that line is
ignored. A block comment marks a whole section of music
input as a comment. Anything that is enclosed in @code{%@{} and @code{%@}} is
introduces a line comment; anything after @samp{%} on that line is
ignored. A block comment marks a whole section of music
input as a comment. Anything that is enclosed in @code{%@{} and @code{%@}} is
@subheading Warning: key signatures and pitches
To determine whether to print an accidental, LilyPond examines the
@subheading Warning: key signatures and pitches
To determine whether to print an accidental, LilyPond examines the
the @emph{printed} accidentals, not the actual pitches! This is a
feature that often causes confusion to newcomers, so let us explain it
in more detail.
the @emph{printed} accidentals, not the actual pitches! This is a
feature that often causes confusion to newcomers, so let us explain it
in more detail.
Adding all alterations explicitly might require a little more effort
when typing, but the advantage is that transposing is easier, and
accidentals can be printed according to different conventions. See
Adding all alterations explicitly might require a little more effort
when typing, but the advantage is that transposing is easier, and
accidentals can be printed according to different conventions. See
Slurs to indicate longer phrasing can be entered with @code{\(} and
@code{\)}. You can have both legato slurs and phrasing slurs at the
same time, but you cannot have simultaneous slurs or simultaneous
Slurs to indicate longer phrasing can be entered with @code{\(} and
@code{\)}. You can have both legato slurs and phrasing slurs at the
same time, but you cannot have simultaneous slurs or simultaneous
Time signatures entered in one staff affects all other staves, but
the key signature of one staff does @emph{not} affect other
staves@footnote{This behavior may be changed if desired; see
Time signatures entered in one staff affects all other staves, but
the key signature of one staff does @emph{not} affect other
staves@footnote{This behavior may be changed if desired; see
These annotations make future upgrades of LilyPond go more
smoothly. Changes in the syntax are handled with a special program,
These annotations make future upgrades of LilyPond go more
smoothly. Changes in the syntax are handled with a special program,
@subsection After the tutorial
After finishing the tutorial, you should probably try writing a
@subsection After the tutorial
After finishing the tutorial, you should probably try writing a
add notes. If you need any notation that was not covered in the
tutorial, look at the Notation Reference, starting with
@ref{Basic notation}. If you want to write for an instrument
add notes. If you need any notation that was not covered in the
tutorial, look at the Notation Reference, starting with
@ref{Basic notation}. If you want to write for an instrument
take a look at @ref{Extending the templates}.
Once you have written a few short pieces, read the rest of
the Learning Manual (chapters 3-5). There's nothing wrong
take a look at @ref{Extending the templates}.
Once you have written a few short pieces, read the rest of
the Learning Manual (chapters 3-5). There's nothing wrong
Learning Manual assumes that you are familiar with
LilyPond input. You may wish to skim these chapters right
now, and come back to them after you have more experience.
Learning Manual assumes that you are familiar with
LilyPond input. You may wish to skim these chapters right
now, and come back to them after you have more experience.
In the rest of the manual, we are much more lax about the
printed examples: sometimes they may have omitted a
In the rest of the manual, we are much more lax about the
printed examples: sometimes they may have omitted a
pitch may be used (such as @code{c'} or @code{c,,}), and in some cases
the whole example is in absolute note mode! However, ambiguities like
this only exist where the pitches are not important. In any example
pitch may be used (such as @code{c'} or @code{c,,}), and in some cases
the whole example is in absolute note mode! However, ambiguities like
this only exist where the pitches are not important. In any example
-where the pitch matters, we have explicitly stated our @code{\relative}
-our our absolute-mode @code{@{ @}}.
+where the pitch matters, we have explicitly stated @code{\relative}
+or absolute-mode @code{@{ @}}.
If you are still confused about the exact LilyPond input that was
used in an example, read the HTML version (if you are not already doing
If you are still confused about the exact LilyPond input that was
used in an example, read the HTML version (if you are not already doing