Carl Sorensen <c_soren...@byu.edu> writes: > On 5/7/10 8:54 AM, "David Kastrup" <d...@gnu.org> wrote: > >> Carl Sorensen <c_soren...@byu.edu> writes: >> >> >>> I appreciate your consistent questioning as to how we might be able to >>> get LilyPond to behave in a way that seems consistent with our >>> expectations. I wish I had the time to understand the internals of >>> parsing better so I could contribute more in this area. But I don't, >>> so I do the best I can with the time I have. >> >> And it's appreciated. In an ideal world, the snippet corpus would be >> without things one would label "hack". > > Well, I'll work on fixing the hack so it rotates the chords. I don't > think it's too big a shift.
Probably not. > Hopefully that will get the job done for you, until somebody can get > it fixed right. Well, I got "the job done" manually already for this particular job. It would probably be a good idea to make your function more visible to the would-be user as long as no proper fix is in. With the rotation trick and with the clashing notecolumn warning removed, there are enough non-trivial components for trickery there to make this code an interesting template for other tasks even when a "proper fix" might be available eventually. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
