Steve D wrote:
Is there actually a need to integrate the \extendedTies block? IMO, there should only be a usual ~ tie simbol, which should work until the first same-pitch note.
That would cause a problem with chords. For example in {<e a>4 ~ <e g> --some-music-- a} the two a's would get tied, which will come quite unexpectedly to the user. I think that practically, partially-tied chords will be lost as a feature.
But I still think that we can get along without an \extendedTies block. I suggest one of the following:
- Support tying individual notes from chords, so the correct way to write the previous example is {<e~ a>4 <e g>}.
This is probably the cleanest solution, and maybe the only way to get some strange constructs like {<c~ e> f <c g> e} right - though I don't think I've ever seen something like that.
- Add a new piece of syntax for an extended tie, such as {c ~~ e ~~ g ~ <c e g>} or {c~( e~( g~ <c e g>~).
Probably easiest to implement, and IMO still a significant improvement over \extendedTies.
- Make ties starting at chords an exception - these have to match the next notes or else be nulled.
Simple, but I don't like exceptions :)
Yuval
_______________________________________________ lilypond-devel mailing list [email protected] http://lists.gnu.org/mailman/listinfo/lilypond-devel
