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

[lilypond]

Comment #26 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

I see that a follow-up comment to comment #24 I made on the developer list  
apparently did not make it here.

The problem with \relative tracking its own version of "last chord" is that  
without Issue 2070 (and -dno-event-chord-wrapper effective!) in place,  
there is nothing distinguishing "last single-note chord" from "last  
non-chord note" in the music expression.

So for my personal priorities and schedules, whenever I might try tackling  
\relative q, I am not doing it ahead of Issue 2070 to avoid unnecessary  
work.  I won't hold back anybody else from doing it (and I think the way is  
reasonably clear: you "just" additionally would have to mark specially  
every EventChord actually coming from a chord so that \relative can find  
it, and then proceed as explained previously in the discussion), and I  
might be made to temporarily shift my priorities if the effort for doing  
the temporary workarounds that would currently still be necessary can be  
considered "paid for", but other than that, personally I'll be tackling  
things in the "natural" order.

If the issue is pressing to you, it might make sense to attach deadlines to  
your bounties and make them out such that it actually hurts when the  
deadline is missed.