From: Trevor Daniels <t.daniels@treda.co.uk>
Date: Fri, 26 Dec 2008 08:40:54 +0000 (+0000)
Subject: Docs: NR 1.2.4 Beams: beatGrouping
X-Git-Tag: release/2.12.1-1~30^2
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=2ba457cf6d351faf53062cbd4020e9fad5114cbf;p=lilypond.git

Docs: NR 1.2.4 Beams: beatGrouping

 - \set commands must be placed after \time commands
---

diff --git a/Documentation/user/rhythms.itely b/Documentation/user/rhythms.itely
index 47b83a282f..7e84e74d16 100644
--- a/Documentation/user/rhythms.itely
+++ b/Documentation/user/rhythms.itely
@@ -1453,7 +1453,9 @@ particular beam in the time signature in use, its beaming is
 controlled by three context properties:
 @code{measureLength}, @code{beatLength} and @code{beatGrouping}.
 These properties may be set in the @code{Score}, @code{Staff} or
-@code{Voice} contexts to delimit their scope.
+@code{Voice} contexts to delimit their scope.  The default values
+are set while processing @code{\time} commands, so the @code{\set}
+commands must be placed after all @code{\time} commands.
 
 These determine the beaming as follows:
 
diff --git a/input/new/specifying-context-with-beatgrouping.ly b/input/new/specifying-context-with-beatgrouping.ly
index f45d4f1904..71ef3530c7 100644
--- a/input/new/specifying-context-with-beatgrouping.ly
+++ b/input/new/specifying-context-with-beatgrouping.ly
@@ -5,7 +5,9 @@
   texidoc = "
 By specifying the context, the effect of @code{beatGrouping} can be
 limited to the context specified, and the values which may have
-been set in higher-level contexts can be overridden:
+been set in higher-level contexts can be overridden.  The
+@code{\set} commands must be placed @emph{after} all @code{\time}
+commands:
 "
   doctitle = "Specifying context with beatGrouping"
 }