@end ignore
-
-@c old info that will probably be removed.
-@c TODO:
-@c * more details about running lilypond; error messages,
-@c compiling/viewing (emacs?)
-@c * where to go from First steps+More basics?
-
-@c wherever possible, do not include index entries here; the
-@c index should point to stuff in the reference manual. -gp
-
-@c Your first LilyPond score in 10 minutes?
-
@node Tutorial
@chapter Tutorial
language and how to produce printed music. After this first
contact we will explain how to create common musical notation.
-@ifhtml
-Many people learn programs by trying and fiddling around with the
-program. This is also possible with LilyPond. If you click on a
-picture in the HTML version of this manual, you will see the exact
-LilyPond input that was used to generate that image. Try it on
-this image
-
-@c no verbatim here
-@lilypond[quote,ragged-right]
-\relative c'' {
- c-\markup { \bold \huge { Click here. } }
-}
-@end lilypond
-
-By cutting and pasting everything in the @qq{ly snippet} section,
-you have a starting template for experiments. If you like
-learning in this way, you will probably want to print out or
-bookmark the @ruser{Cheat sheet}, which is a table listing of the
-most common commands for quick reference.
-
-@end ifhtml
-
@menu
* First steps::
* Single staff notation::
should also be surrounded by a space unless they are at the
beginning or end of a line to avoid ambiguities. The braces may
be omitted in some examples in this manual, but don't forget them
-in your own music!}
+in your own music! For more information about the display of
+examples in the manual, see @ref{How to read the tutorial}.}
@cindex Case sensitive
In addition, LilyPond input is @strong{case sensitive}. @code{
@subheading Entering music and viewing output
+@cindex PDF file
+@cindex Viewing music
+
In this section we will explain what commands to run and how to
view or print the output.
+Note that there are several other text editors available with
+better support for LilyPond. For more information, see
+@rprogram{Text editor support}.
+
+@warning{the first time you ever run LilyPond, it may take a
+minute or two because all of the system fonts have to be analyzed
+first. After this, LilyPond will be much faster!}
+
@subsubheading MacOS X
If you double click @code{LilyPond.app}, it will open with an
Typeset File}. The resulting PDF file will be displayed on your
screen.
-Be warned that the first time you ever run LilyPond, it will take
-a minute 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 @q{Open}. You must save your file before typesetting it. If
any errors occur in processing, please see the log window.
what LilyPond has done to the file. If any errors occur, please
examine this file.
-Note that there are several other text editors available, with
-better support for LilyPond, see @rprogram{Text editor support},
-for more information.
-
@subsubheading Unix
-Begin by opening a terminal window and starting a text editor.
-For example, you could open an xterm and execute
-@code{joe}@footnote{There are macro files for VIM addicts, and
-there 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
-@rprogram{Text editor support}, for more information.}. In your
-text editor, enter the following input and save the file as
-@file{test.ly}
-
-@verbatim
-{
+Create a file (such as @file{test.ly}) and enter:
+
+@example
+@{
c' e' g' e'
-}
-@end verbatim
+@}
+@end example
-@noindent
To process @file{test.ly}, proceed as follows
@example
Converting to `test.pdf'...
@end example
-@cindex PDF file
-@cindex Viewing music
-
-@noindent
-The result is the file @file{test.pdf} which you can print or view
-with the standard facilities of your operating system.@footnote{If
-your system does not have any such tools installed, you can try
-@uref{http://@/www@/.cs@/.wisc@/.edu/@/~ghost/,Ghostscript}, a
-freely available package for viewing and printing PDF and
-PostScript files.}
-
@node Simple notation
@subsection Simple notation
c4 c g' g a a g2
%@{
- This line, and the notes below
- are ignored, since they are in a
- block comment.
+ This line, and the notes below
+ are ignored, since they are in a
+ block comment.
- g g f f e e d d c2
+ g g f f e e d d c2
%@}
@end example
As we saw in @ruser{Working on text files}, LilyPond input must be
surrounded by @{ @} marks or a @code{\relative c'' @{ ... @}}.
-For the rest of this manual, most examples will omit this.
-
-If you are reading the HTML documentation and wish to see the
-exact exact LilyPond code that was used to create the example,
-simply click on the picture. If you are not reading the HTML
-version, you could copy and paste the displayed input, but you
-@strong{must} add the @code{\relative c'' @{ @}} like this:
+For the rest of this manual, most examples will omit this. To
+replicate the examples, you may copy and paste the displayed input
+but you @strong{must} add the @code{\relative c'' @{ @}} like
+this:
@example
\relative c'' @{
into the middle of a longer piece of music. For these examples,
it does not make sense to add @code{\relative c'' @{ @}} -- you
should not place a @code{\relative} inside another
-@code{\relative}, so you would not be able to copy a small
+@code{\relative}! If we included @code{\relative c'' @{ @}}
+around every example, you would not be able to copy a small
documentation example and paste it inside a longer piece of your
-own.
+own. Most people want to add material to an existing piece, so we
+format the manual this way.
+
+
+@subheading Clickable examples
+
+Many people learn programs by trying and fiddling around with the
+program. This is also possible with LilyPond. If you click on a
+picture in the HTML version of this manual, you will see the exact
+LilyPond input that was used to generate that image. Try it on
+this image
+
+@c no verbatim here
+@lilypond[quote,ragged-right]
+\relative c'' {
+ c-\markup { \bold \huge { Click here. } }
+}
+@end lilypond
+
+By cutting and pasting everything in the @qq{ly snippet} section,
+you have a starting template for experiments. To see exactly the
+same output (line-width and all), copy everything from @qq{Start
+cut-&-pastable section} to the bottom of the file.
@node Single staff notation
projects / lilypond.git / commitdiff