Kieren MacMillan wrote Sunday, September 06, 2009 3:34 PM
\\ is quite more convenient than explicit voices and thus an
important
idiom that makes Lilypond friendlier to the user.
Yes, but as previously discussed, the confusion it (ultimately)
causes is a poor
trade-off. The whole problem would be solved if \\ Did The Right
Thing, i.e.
<< { musicA } \\ { musicB }>>
would automagically expand to
<< { \voiceOne musicA } \context Voice = "2" { \voiceTwo
musicB }>> \oneVoice
This change would help, but I don't think it
would solve the whole problem. You'd still have
an implied name for the second context, so it
doesn't work in more than one staff, or when
there are lyrics to assign.
I can take this on as my next Frog task, if it requires no C++.
Then, the
documentation can simply use \\ early on (e.g., in the LM), and
show what it does > later.
I think this is implemented in voicify-music
in scm/music-functions.scm.
I'll hold fire on the re-documentation a bit
longer until you've had a look at this.
Trevor
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
