vm-edit-message for re-threading
Bug #930908 reported by
Uday Reddy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| VM |
Triaged
|
Low
|
Uday Reddy | ||
Bug Description
If you use vm-edit-message to add "In-Reply-To" and "References" headers and put the message inside an existing thread, it appears that the cached data has inconsistencies.
The summary buffer showed the message in the correct place. However, doing `vm-next-message' took me to the old successor of the message, not the successor in the new message-order.
Perhaps other parts of the cached data also have inconsistencies.
Revision history for this message
| John Hein (xpqheqdvq4) wrote | #1 |
To post a comment you must log in.
I could not reproduce this when I tried to switch around message IDs in References fields in an existing thread. Navigation in the summary always followed the thread order in the summary buffer (with vm-summary-
In another test case, however, adding a 'References' to an otherwise unthreaded message put it into a short 2 message (now 3) thread in the right place (and navigation worked). But when I removed the artificial 'References' header, the message did not lose its thread indentation until I quit the folder and re-entered. Toggling vm-summary-