Re: [Lilypond-auto] Issue 2858 in lilypond: Document \shape music function

[lilypond]

Comment #9 on issue 2858 by address@hidden: Document \shape music  
function
http://code.google.com/p/lilypond/issues/detail?id=2858

"Offtopic: it uses (define ((shape-curve offsets) item) ...  Is there a  
reason that this is not just (define (shape-curve item) ... and is later  
used as #shape-curve rather than #(shape-curve offsets) ?

Guilev2 does not support curried definitions by default (it requires  
loading an extra module), and in this case, the currying seems to serve no  
purpose."

Nice catch.  Absolutely right: what sense is there passing around offsets  
when it's right there in the environment?

"When used as a \tweak, it will be applied to slurs, ties and similarly  
brief stuff.
\shape ( #'(...........................)
or even
\shape \laissezVibrer #'(............................)
seems quite tolerable.  The reason to stick music arguments at the end is  
that music arguments tend to be long (which is not the case here) and that  
often one wants to apply multiple functions with arguments ona music  
expression.  Ok, something like
\shape \tweak #'color #red \laissezVibrer #'(........................) is  
unnice, but one can write
\tweak #'color #red \shape \laissezVibrer #'(........................)  
instead."

I like this.  Seems to me, the flexibility in ordering is a good thing.

"[...] but it would save writing a convert-ly rule"

Good enough for me!