Re: Document <> and improve other simultanous music documentation. (issue 6248080)

[dak]

On 2012/06/02 07:28:37, dak wrote:

> >  music = \relative c'' { e16 d c d }
> >  { f'4 <>\marcato \music r <>^"smorz." \mp \> \music <>\! }

> Incidentally, something like
> atLast =
> #(define-music-function (parser location post music)
>     (ly:event? ly:music?)
>     (let ((final
>           (fold-some-music
>            (lambda (m) (or (music-is-of-type? m 'rhythmic-event)
>                            (music-is-of-type? m 'event-chord)))
>            (lambda (m p) m)
>            #f
>            music)))
>       (if final
>          (set! (ly:music-property final 'articulations)
>                (cons post (ly:music-property final 'articulations)))
>          (ly:music-warning music "No place for post-event"))
>       music))

> music = \relative c'' { e16 d c d }
> { f'4 <>\marcato \music r <>^"smorz." \mp \> \atLast \! \music }

> looks nicer, but is not exactly manual material.

In this case, compare what happens if you follow this up with
c\f c c c

The solution with <>\! will essentially get ignored, and the
descrescendo ends in forte.  The solution with \atLast will, in
contrast, end the descrescendo independently from \f and placed at a
different vertical position much better reflecting the musical
meaning.

It would seem that _trailing_ <> are not really something we should
lightly suggest since it is unknown what their articulations will
attach themselves to.


http://codereview.appspot.com/6248080/