From 9e263dce9237347a6e55fcc8662829474e077b3c Mon Sep 17 00:00:00 2001 From: David Kastrup Date: Sun, 23 Dec 2012 22:21:30 +0100 Subject: [PATCH] Issue3058: Remove "Apparent error in ../ly/init.ly" from Common Errors in usage It should not really be possible to trigger this one any more. --- Documentation/usage/running.itely | 29 ----------------------------- 1 file changed, 29 deletions(-) diff --git a/Documentation/usage/running.itely b/Documentation/usage/running.itely index 2e06c8d11a..5bae43cb1e 100644 --- a/Documentation/usage/running.itely +++ b/Documentation/usage/running.itely @@ -925,7 +925,6 @@ are easily handled. @menu * Music runs off the page:: * An extra staff appears:: -* Apparent error in ../ly/init.ly:: * Error message Unbound variable %:: * Error message FT_Get_Glyph_Name:: * Warning staff affinities should only decrease:: @@ -1014,34 +1013,6 @@ problem: @end lilypond -@node Apparent error in ../ly/init.ly -@unnumberedsubsec Apparent error in @code{../ly/init.ly} - -Various obscure error messages may appear about syntax errors in -@file{../ly/init.ly} if the input file is not correctly formed, -for example, if it does not contain correctly -matched braces or quote signs. - -The most common error is a missing brace, (@code{@}}), at the end of -a @code{score} block. Here the solution is obvious: check the -@code{score} block is correctly terminated. The correct structure -of an input file is described in @rlearning{How LilyPond input files work}. -Using an editor which automatically highlights matching brackets and -braces is helpful to avoid such errors. - -A second common cause is no white space between the last syllable -of a lyrics block and the terminating brace, (@code{@}}). Without -this separation the brace is taken to be part of the syllable. It -is always advisable to ensure there is white space before and after -@emph{every} brace. For the importance of this when using lyrics, -see @ruser{Entering lyrics}. - -This error message can also appear if a terminating quote sign, -(@code{"}), is omitted. In this case an accompanying error message -@c keep "-matching straight in fancy editors -should give a line number close to the line in error. The -mismatched quote will usually be on the line one or two above. - @node Error message Unbound variable % @unnumberedsubsec Error message Unbound variable % -- 2.39.2