From 93859ecf84b5af2d7623fdf66be32247533ab4ff Mon Sep 17 00:00:00 2001 From: Trevor Daniels Date: Thu, 11 Jun 2009 09:44:14 +0100 Subject: [PATCH] Docs: LM 2 Tutorial: add more on whitespace - emphasise need for whitespace to separate syntactic elements --- Documentation/user/tutorial.itely | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/Documentation/user/tutorial.itely b/Documentation/user/tutorial.itely index 86836d02ab..f5c20df995 100644 --- a/Documentation/user/tutorial.itely +++ b/Documentation/user/tutorial.itely @@ -503,7 +503,7 @@ Notes are lower case: @w{@code{@{ c d e @}}} is valid input; @item @strong{Whitespace insensitive}: -it does not matter how many spaces (or new lines) you add. +it does not matter how many spaces (or tabs or new lines) you add. @w{@code{@{ c d e @}}} means the same thing as @w{@code{@{ c @tie{}} @tie{} @tie{} d e @}} and: @@ -522,6 +522,13 @@ thumb is to indent code blocks with either a tab or two spaces: @} @end example +However, whitespace @emph{is} required to separate many syntactical +elements from others. In other words, whitespace can always be +@emph{added}, but it cannot be @emph{eliminated}. As missing +whitespace can give rise to strange errors it is advisable to +always insert whitespace before and after every syntactic element, +for example, before and after every curly brace. + @item @strong{Expressions}: every piece of LilyPond input needs to have @strong{@{ curly -- 2.39.5