Suspected Bug in Lilypond: pushToTag vs EventCord

[Bjørn Bäuchle]

Happy New Year!

I have come across some odd behaviour with \pushToTag.

See this MWE:

x = \relative c' { \tag #'dyn c \tag #'dyn <c e>4 }
\relative c' { \pushToTag #'dyn \p \x }

I receive the following message:

test.ly:...: warning: \pushToTag cannot push post-event
\relative c' { \pushToTag #'dyn
                                \p \S }
test.ly:...: to this music
S = \relative c' { \tag #'dyn c
                                \tag #'dyn <c e>4 }

Investigating, I found the error message in ly/music-functions.ly:1880.
This code has been introduced in
fda7efb2254751862897d66c6b27b099fb2975b6 ; the commit message says
"rhythmic events or articulations can be pushed to chords, and
articulations only can be pushed to rhythmic events." Now I don't quite
understand how articulations can be pushed to chords and then only to
rhythmic events, but in any case passing a chord into add-left which is
defined in lines 1874-1909 triggers the first condition "(music-is-of-
type? m 'simultaneous-music)" (line 1877).

Changing the order of the conditions - first checking event-chord, then
sequential-music and simultaneous-music, i.e., moving lines 1884-1897
above line 1876, works and allows to push a dynamic mark to an
EventChord.

Cheers
Bjørn B