[Mutt] #3008: Odd behavior in mutt-thread patch?

[Mutt <fleas@xxxxxxxx>]

#3008: Odd behavior in mutt-thread patch?

 This is my first bug report here, so please be kind if I'm out of line, or
 something. :)

 I run Debian testing's Mutt 1.5.17. I encountered unexpected behavior with
 the ~(pattern) syntax which I suspect is a bug, though nothing obvious
 jumped at me when I looked at what the patch added to pattern.c.
 Incidently my C is a bit rusty...

 I view collapsed threads by default:

 {{{
 set sort='threads'
 set sort_aux='last-date-received'
 folder-hook . 'push <collapse-all>'
 }}}

 I wanted to highlight flagged messages, not only for stand-alone messages,
 but for entire threads containing a flagged message, so I could always see
 where there were any. First try:

 {{{
 color index brightred default "~(~F)"
 color index brightred default "~F"
 }}}

 This works as expected: all messages of threads containing at least one
 flagged message get highlighted, and stand-alones too of course. I wanted,
 however, that expanded threads only highlight flagged messages, not the
 whole thread:

 {{{
 color index brightred default "~(~F ~v)"
 color index brightred default "~F"
 }}}

 Unexpectedly, this does not highlight anything. I tried removing the
 space, adding extra parenthesis, changing the order to ~v ~F, nothing
 worked. Either of the two patterns works as expected alone, but together
 like this, match nothing.

 I worked around the issue with a wild guess:

 {{{
 color index brightred default "~(~F) ~(~v)"
 color index brightred default "~F"
 }}}

 This does work as I initially intended: highlight collapsed threads
 containing flagged messages.

 PS: I am unfamiliar with TRAC's way of sending e-mail updates. I am wary
 of the "Cc" field in case it makes my address public (i.e. for spam-bots.)
 Please "subscribe" me to this ticket so I don't have to monitor its web
 page to notice you replied. Thanks! :)

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3008>