From: Francisco Vila <francisco.vila@hispalinux.es>
Date: Fri, 15 Aug 2008 00:49:29 +0000 (+0200)
Subject: Mark reorder plan for Simultaneous
X-Git-Tag: release/2.11.57-1~40^2~3^2~2
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=58ab190a8c04782c6a2e349891d57aa3ae503faa;p=lilypond.git

Mark reorder plan for Simultaneous
---

diff --git a/Documentation/user/simultaneous.itely b/Documentation/user/simultaneous.itely
index f0cf731f6e..5071270534 100644
--- a/Documentation/user/simultaneous.itely
+++ b/Documentation/user/simultaneous.itely
@@ -134,6 +134,20 @@ multiple staves.
 * Writing music in parallel::
 @end menu
 
+@ignore FUTURE PLANS. Carl suggested:
+
+Perhaps it would be clearer if we started with single-staff polyphony
+with named and explicitly created voices, along with the \voiceOne
+through \voiceFour properties.
+
+We could then introduce the << \\ >> syntax as a simple way to handle
+music where we don't care that temporary voices are created and then
+discarded.
+
+It seems to me to be much easier to go from the full understanding to
+the shortcut than the other way around.
+@end ignore
+
 
 @node Single-staff polyphony
 @unnumberedsubsubsec Single-staff polyphony