From fdec1ca56b81c564259729b87ded0564533da25c Mon Sep 17 00:00:00 2001 From: Carl Sorensen Date: Wed, 14 Apr 2010 21:24:12 -0600 Subject: [PATCH] Doc: Add links to troubleshooting to Learning Manual --- Documentation/learning/tutorial.itely | 38 +++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) diff --git a/Documentation/learning/tutorial.itely b/Documentation/learning/tutorial.itely index da4acb948d..0b55738695 100644 --- a/Documentation/learning/tutorial.itely +++ b/Documentation/learning/tutorial.itely @@ -20,6 +20,7 @@ This chapter gives a basic introduction to working with LilyPond. @menu * Compiling a file:: * How to write input files:: +* What if it doesn't work:: * How to read the manuals:: @end menu @@ -567,6 +568,43 @@ comments: @end itemize +@node What if it doesn't work +@section What if it doesn't work + +@cindex troubleshooting + +Sometimes LilyPond doesn't produce the output you expect. This +section provides some links to help you solve the problems you +might encounter. + + +@menu +* General troubleshooting tips:: +* Some common errors:: +@end menu + +@node General troubleshooting tips +@subsection General troubleshooting tips + +Troubleshooting LilyPond problems can be challenging for +people who are used to a graphical interface, because invalid +input files can be created. When this happens, a logical approach +is the best way to identify and solve the problem. Some guidelines +to help you learn to do this are provided in @rprogram{Troubleshooting}. + + +@node Some common errors +@subsection Some common errors + +@cindex common errors +@cindex errors, common + +There are a few common errors that are difficult to troubleshoot +based simply on the error messages that are displayed. These are +described in @rprogram{Common errors}. + + + @node How to read the manuals @section How to read the manuals -- 2.39.5