Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax

[lilypond]

Comment #17 on issue 1110 by address@hidden: Wrong octave of repetition chord  
with \relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110

Getting back to comment #11 from Werner:
> IMHO, q is such a useful feature that even a `heavy' solution would be  
> worth to implement.

Let me ask the simple and stupid question: how much worth?  "worth to  
implement" is easy to say if one is not planning to do it oneself.  I am  
not going to do the brute-force solution outlined in the first comment  
anyway.  There is no point in performance impacts for everyone for the sake  
of a feature they might not even use.  I'll likely not even bother warning  
when the next preceding chord in the sequence is not actually the one q  
takes its info from.  That's just user error.  On the other hand, it may be  
easier to reliably distinguish chords from single notes if one just tacks a  
chordId field on anyway, so it might be the easiest way to do this.

Actually the analysis, discussion (and my sleepless night) have pretty much  
been the main work.  I won't complain if somebody else takes it from  
there.  If your priorities are such that you want to see me do the coding  
as well (which is not more than the finishing touch and is likely doable by  
considerably more than half of the people regularly committing code), tempt  
me with a bounty.

If it is a motivation, I have an awful record actually collecting them, and  
if you decide to defect, you'll be in excellent company.