thread roots and thread operations

I'm just wondering what is occurring related to this report that seems
strange. I certainly agree with the importance of recognizing threads
roots as such but I have not seen any weird behavior with stand alone
threads or anything. Shouldn't the operations naturally just occur
with the root in such a case? And if the original root is deleted the
second in line becomes the root, behavior which is exhibited at
present in VM.

Or maybe I'm reading this wrong, it's a call to be on the lookout for
strange things?

-Arik

Your original method for getting thread-folding information was by
analyzing the Summary buffer. I have now added a folded-flag in the
message attributes and changed it to get the information from there.
The new method should be more reliable in the long run. But we need
to get the bugs out first.

In the example I ran into, there was a thread that looked like:

  + 21+1 ...
      22 ...

I deleted and expunged 22, then tried to save 21. It turns out that
the folded-flag of 21 is still true. So, VM thinks that it is still
the root of a thread. I have vm-enable-thread-operations set to 'ask.
So, VM asks whether it should save all the messages in the thread
(even though there is only one message in the thread now).

I did a quick fix to `vm-thread-root-p' by saying that a message
should be regarded as a root only if it has more than one message in
the thread.

But perhaps the folded-flag should be set to nil when the rest of its
thread gets expunged. I haven't come to a resolution on that issue
yet.

This bug report merely says that we should test out all the
implications of moving to the folded-flag so that the we can get the
bugs out.

Cheers,
Uday

Thanks for the clarification, will do some thinking about this and be
on the look out for other strangeness.

Cheers,
-Arik

In virtual folders, multiple copies of messages were getting added to thread-subtrees (and thread-symbols), which resulted in individual messages getting counted as thread-roots. Fixed in revision 1195.

Things seem to be working ok now. So, we will close this bug report.

Revision 1312 has another bug fix. We will keep this bug report open for a while.