Re: Doc: NR Added @knownissue for clashing note column (issue 5500043)

[pkx166h]

Reviewers: ,

Message:
Tue, 20 Dec 2011 21:30:43 +0000 (21:30 +0000)
commit  3c46876d446ca034e2b109302941586061865a01

Description:
Doc: NR Added @knownissue for clashing note column

As per suggestion of Tracker 1267.

Added under 'simultaneous expressions'

NR was more appropraite than LM in this case.

Please review this at http://codereview.appspot.com/5500043/

Affected files:
  M Documentation/notation/simultaneous.itely


Index: Documentation/notation/simultaneous.itely
diff --git a/Documentation/notation/simultaneous.itely  
b/Documentation/notation/simultaneous.itely
index  
8f55aea92856e5e2fe12bf7b91f633620f4200e6..0506020d442e59cd5ea25c6593489bd010ff1cf6  
100644
--- a/Documentation/notation/simultaneous.itely
+++ b/Documentation/notation/simultaneous.itely
@@ -209,6 +209,24 @@ generate multiple staves implicitly:

 Here different rhythms cause no problems.

address@hidden
+If notes from two or more voices, with stems in the same direction, are
+placed at the same position on the staff and have no shift (or have the
+same shift specified), the message:
+
address@hidden
+warning: ignoring too many clashing note columns
address@hidden example
+
+will appear during compilation.  This message can be suppressed by:
+
address@hidden
+\override NoteColumn #'ignore-collision = ##t
address@hidden example
+
+However, this does not only suppress the warning but will prevent any
+collision resiolution, so may have unintended results.
+

 @node Clusters
 @unnumberedsubsubsec Clusters