Do a quick search then try to sort the results by thread. Nothing happens.

No threading in quick search results is intended behavior... I think we have an existing bug about disabling the threading menu items, button.

yes, we don't support threading of quick search results.

*** Bug 147557 has been marked as a duplicate of this bug. ***

*** Bug 157195 has been marked as a duplicate of this bug. ***

*** Bug 183785 has been marked as a duplicate of this bug. ***

setting assignee to seth spitzer... may become more important issue with the introduction of the MailViews feature.

*** Bug 198448 has been marked as a duplicate of this bug. ***

*** Bug 205669 has been marked as a duplicate of this bug. ***

Perhaps this needs to be set OS All?

As requested. Based on Hardware/OS of some of the dupes.

*** Bug 190894 has been marked as a duplicate of this bug. ***

*** Bug 206433 has been marked as a duplicate of this bug. ***

*** Bug 200169 has been marked as a duplicate of this bug. ***

*** Bug 211464 has been marked as a duplicate of this bug. ***

Maybe no threading in quick search results is an intended behaviour but threading is also not available in View/Unread mode which is a regression, because it used to be working fine.

*** Bug 214748 has been marked as a duplicate of this bug. ***

*** Bug 228697 has been marked as a duplicate of this bug. ***

*** Bug 229553 has been marked as a duplicate of this bug. ***

I think no threading in quick search should not be intended behavior. Instead two threading sort modes may be better, like: - Threading AFTER: first apply quick search, filter, custom filter and then thread-sort whatever comes out, most of it non-threadable - Threading BEFORE: first thread-sort and then filter *threads* complying with filter, say: "(thread) has unread", "() has new", "() has from: mail@me.com", etc.

See bug 197620.

*** Bug 233856 has been marked as a duplicate of this bug. ***

*** Bug 224064 has been marked as a duplicate of this bug. ***

*** Bug 252492 has been marked as a duplicate of this bug. ***

This bug applies to the new "virtual folder" feature as well -- another set of search results that cannot be threaded.

*** Bug 268143 has been marked as a duplicate of this bug. ***

*** Bug 269594 has been marked as a duplicate of this bug. ***

(In reply to comment #25) > This bug applies to the new "virtual folder" feature as well -- another set of > search results that cannot be threaded. Please support threading in "virtual folders" otherwise they cannot be really be used as it seems they should ie dynamic folders which have all the benefits of standard folders without the need to physically move and mix up mail items and with the possibility to change (and re-change) the associations of items as required at the drop of a hat. As it is I have had to combine each of my 'input' and 'output' folder pairs to obtain the benefits of threaded mail when I would still much prefer to keep them physically separate. Thank you RDL

I agree with comment #28. The biggest feature I find myself always missing is threaded messages in my saved searches. Is there some big technical reason this is impossible or is it just so difficult to accomplish it simply hasn't been tackled yet?

the latter. It's hard, and I haven't tackled it yet.

Just as a curiosity, since the messages can already be shown in a list, shouldn't it be relatively straightforward to feed that list to the threading function/library? Handle the search results as if they were all the messages there are in that group.. In any case, for many occasions this just renders TB useless for news reading. Not very helpful when you get 600+ hits on "PDF" in Corel support group.. And no threading is taking place.

There is a patch for this issue in progress at bug 263180. I'm pretty sure it's core work, so once checked in, Seamonkey will benefit as well. David, should this get duped?

yes, dup. *** This bug has been marked as a duplicate of 263180 ***