From: Graham Percival Date: Sun, 14 Oct 2007 21:34:35 +0000 (-0700) Subject: Misc improvements. X-Git-Tag: release/2.11.35-1~46^2~47 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=48e9cecc0d45f08084a760ad3feaedbda92964df;p=lilypond.git Misc improvements. --- diff --git a/Documentation/user/music-glossary.tely b/Documentation/user/music-glossary.tely index 384db68670..e0c7cae231 100644 --- a/Documentation/user/music-glossary.tely +++ b/Documentation/user/music-glossary.tely @@ -1410,7 +1410,7 @@ lines have been selected: #'minimum-Y-extent = #'(0 . 0) \override Staff.Clef #'stencil = ##f % No clef required \clef "F" - g,1 b, d f a + g,1_" " b, d f a % s s s s s s % Keep staff showing } % End staff F >> diff --git a/Documentation/user/pitches.itely b/Documentation/user/pitches.itely index 5aa116e742..395d8911e1 100644 --- a/Documentation/user/pitches.itely +++ b/Documentation/user/pitches.itely @@ -596,11 +596,11 @@ the existing music with another @code{\transpose} @seealso -Program reference: @internalsref{TransposedMusic}. - Snippets: @lsrdir{pitch}, @lsr{scheme, transpose-pitches-with-minimum-accidentals.ly}. +Program reference: @internalsref{TransposedMusic}. + @refbugs @@ -909,11 +909,9 @@ generating a whole-tone scale: Music glossary: @rglos{Church mode}, @rglos{scordatura}. -Snippets: @lsrdir{pitch} - -FIXME Link to snippet 248 (maybe) -Another example of using @code{keySignature} can be found in -@lsrdir{scordatura} +Snippets: @lsrdir{pitch}, +FIXME link to snippet 248, +FIXME link to a snippet about scordatura. Program reference: @internalsref{KeyCancellation}, @internalsref{KeySignature}, @internalsref{Key_engraver} diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely index e4593e66c2..78f639d312 100644 --- a/Documentation/user/tutorial.itely +++ b/Documentation/user/tutorial.itely @@ -22,18 +22,6 @@ Tutorial guidelines: @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 @@ -41,28 +29,6 @@ This tutorial starts with an introduction to the LilyPond music 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:: @@ -113,7 +79,8 @@ the result looks like this 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{ @@ -124,9 +91,20 @@ error message. @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 @@ -135,10 +113,6 @@ Desktop, and then process it with the menu command @samp{Compile > 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. @@ -165,29 +139,16 @@ also produces a @file{.log} file that contains some information on 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 @@ -209,17 +170,6 @@ Layout output to `test.ps'... 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 @@ -467,11 +417,11 @@ fragment shows possible uses for comments 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 @@ -486,13 +436,10 @@ There are more tips for constructing input files in 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'' @{ @@ -504,9 +451,32 @@ Why omit the braces? Most examples in this manual can be inserted 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