From 6b5efd4631ffb19aea9499769c9e23584f2a1213 Mon Sep 17 00:00:00 2001 From: Trevor Daniels Date: Mon, 22 Jun 2009 10:00:16 +0100 Subject: [PATCH] Docs: NR 3.1.3 Say when whitespace is required --- Documentation/user/input.itely | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/Documentation/user/input.itely b/Documentation/user/input.itely index b20cc4ebf3..2bf35cf51d 100644 --- a/Documentation/user/input.itely +++ b/Documentation/user/input.itely @@ -354,6 +354,27 @@ A multi-line comment delimited by @code{%@{ .. %@}}. @end itemize +@cindex whitespace + +Whitespace between items in the input stream is generally ignored, +and may be freely omitted or extended to enhance readability. +However, whitespace should always be used in the following +circumstances to avoid errors: + +@itemize +@item Around every opening and closing curly bracket. +@item After every command or variable, i.e. every item that +begins with a @code{\} sign. +@item After every item that is to be interpreted as a Scheme +expression, i.e. every item that begins with a @code{#} sign. +@item To separate all elements of a Scheme expression. +@item In @code{lyricmode} to separate all the terms in both +@code{\override} and @code{\set} commands. In particular, spaces +must be used around the dot and the equals sign in commands like +@code{\override Score . LyricText #'font-size = #5} and before and +after the entire command. + +@end itemize @seealso Learning Manual: -- 2.39.5