GNOME Bugzilla – Bug 203737
deleting mail in threaded view w/ "hide deleted messages" is obnoxious
Last modified: 2005-11-15 02:22:21 UTC
I delete 90% of the mail I receive after reading it. In the threaded view, this is very tricky to do, because if you delete the head of a thread, the rest of the thread jumps to somewhere else in the tree. So the only way to to it is either to delete all of the thread children first, or to Shift-select each succeeding message in the thread as you go, and then delete them all together when you reach the end. Which doesn't help if you want to delete the beginning but keep some of the messages in the middle.
Do you have any clue as to why the thread jumps to another location?
Because when you delete the head, it has to reconstruct the thread without it, meaning it chains everything off the second message, which defaults to living somewhere else in the tree. (Of course, if you don't move the thread then, then when do you move it?) It's probably worth seeing how Netscape, Gnus, and other threading mailers behave. It may just be that "threaded view" and "hide deleted messages" are incompatible options.
*** bug 205800 has been marked as a duplicate of this bug. ***
Mutt only threads when you open the folder. If new mail arrives while the folder is open it gets slotted into the right place in the threaded order. Deleting a message causes the cursor to move to the next in message display order. (Increasing priority as suggested in bug 205800)
"when you open the folder" meaning the first time, or each time you return to the folder after visiting another folder too?
*** bug 205210 has been marked as a duplicate of this bug. ***
At this point, I'm not really sure whether or not this is UI. Anna, feel free to remove the keyword and your cc: if you want.
This looks to me like it's fixed. The behavior in Evo 0.12 is: 1) select first message in thread 2) delete -> Evo moves to the next message in the thread 3) 'Expunge' messages -> Evo re-threads the messages, removed the delete message and keeping the currently selected message selected, as the top message in the new thread listing This is using an IMAP folder, sorted by 'Sent' (date). Should this bug be closed?
Oops. Never specified that this is when "hide deleted messages" is on. (So no, it's not fixed.)
No, this isnt fixed. danw: "when you open the folder" means each time you return to the folder. I don't think mutt knows about having more than one folder open at once. It doesn't really matter though, because it slots new mail into the correct place in the tree if it arrives when the threaded folder is open. Evolution can do that whether it is displaying an open folder or not. If evolution would just step the cursor to the next unread/visible message in the list, whether deleted mails are hidden or not, then this problem would be solved. While getting a backtrace of another problem, I captured these messages that show why this problem exists. Me deleting messages causes evolution-mail to print: folder changed event, changes = 0x8353918 changed = 1 added = 0 removed = 0 folder changed event, changes = 0x8353918 changed = 1 added = 0 removed = 0 Message threading 7 messages took 0.000 seconds emitting cursor changed signal, for uid 572 folder changed event, changes = 0x8355900 changed = 1 added = 0 removed = 0 emitting cursor changed signal, for uid 573 Message threading 6 messages took 0.000 seconds folder changed event, changes = 0x8253fc0 changed = 1 added = 0 removed = 0 emitting cursor changed signal, for uid 577 Message threading 5 messages took 0.000 seconds ... and so on.
Well this used to work better, but then selection stuff got moved to etable. This is basically an etable-restoring-selection issue isn't it chris?
This is not etable. The mailer does this on purpose. OK, since several people have not understood this now... Suppose you have: (capitals = "bold" = unread) [] wombats Mon 9:29 PM [] widgets Mon 9:30 PM <-- selected message [] | RE: WIDGETS MON 10:47 PM [] + RE: WIDGETS MON 11:15 PM [] FROBS MON 9:45 PM [] GEGLS MON 10:13 PM [] ZOTS MON 11:03 PM If you delete the selected message, and "hide deleted messages" is set, you'll end up with: [] wombats Mon 9:29 PM [] FROBS MON 9:45 PM [] GEGLS MON 10:13 PM [] RE: WIDGETS MON 10:47 PM <-- selected message [] + RE: WIDGETS MON 11:15 PM [] ZOTS MON 11:03 PM The selection moved to the next message in the thread (which is correct), but the thread itself has now jumped over several unread messages (the ones that arrived between the first two messages in the thread). If you now delete this selected message, the next message in the thread will jump again. Eventually you reach the end of the folder, but there are still unread messages above you. What you want to happen when you delete the head of the thread is this: [] wombats Mon 9:29 PM [] RE: WIDGETS Mon 10:47 PM <-- selected message [] + RE: WIDGETS Mon 11:15 PM [] FROBS Mon 9:45 PM [] GEGLS MON 10:13 PM [] ZOTS Mon 11:03 PM Eg, its thread is regenerated (the 11:15 msg is chained to the 10:47 message now since the 9:30 one is gone), but the thread as a whole still remains at the same spot in the tree relative to the other messages, *even though that's not where it logically belongs any more*. And then the next time you send/receive, change the sorting, toggle threading, or leave the folder and come back, it would move to where it belongs, because doing so then isn't going to mess up your mail reading (hopefully).
Well this isn't going to change. If you want threaded messages its going to have to be displayed threaded. If you want somethign that isn't threaded, then thats a different feature.
This *is* threaded messages. It's exactly how other mailers (like Mutt) do it.
I'll agree it's not going to change for 1.0 at this point though.
Oops, this never got moved back from gal to mail
*** bug 215107 has been marked as a duplicate of this bug. ***
*** bug 223897 has been marked as a duplicate of this bug. ***
*** bug 219991 has been marked as a duplicate of this bug. ***
*** bug 218791 has been marked as a duplicate of this bug. ***
*** bug 224663 has been marked as a duplicate of this bug. ***
I think this is a fairly critical problem, and judging from the number of duplicate bug reports, a lot of other people do too. Reading in threaded mode, deleting messages as you go, is a very common way of interacting with a mail client. Other clients such as Mutt and Sylpheed handle this flawlessly. Evolution not only handles it poorly, but acts unpredictably, so that it is difficult to even learn to live with it.
I'm reassigning this to me. I dont trust dan to know how to fix it.
this got fixed a while back