GNOME Bugzilla – Bug 213422
Post 1.0: Proposal for clarifying Trash/vFolder/Expunge behavior
Last modified: 2013-09-10 14:02:48 UTC
As discussed endlessly on the Evolution mailing list, the Trash vFolder is confusing the hell out of people who are used to other mailers and have never used vFolders. They are confused when they see a deleted item in two different places: The folder where it actually exists (with a line through it) and the Trash vFolder, which looks from its placement like any "plain" folder. Trying to get rid of the extra copy, they inevitably expunge in one or the other folders and suddenly oops! the mail they thought they'd merely deleted now resides in the Great Bit Bucket. The problem here is both the placement of a vFolder among normal folders, and the use of the word "Trash". Most mailers have a Trash folder in the same place, and it's great to try to make users comfortable. However, what we call Trash has completely different semantics than what users are used to. They expect that deleted items are *moved* to the Trash folder, and that recovering them means moving them back out. After a few encouraging responses from the list, I'd like to propose that "Trash" be renamed "Unexpunged Items" and moved down among the vFolders where it belongs. If, as has been suggested, traditional Trash functionality is provided in a post-1.0 release, call THAT "Trash", but retain "Unexpunged Items" for the name of this vFolder. The semantics of this folder are then MUCH clearer and the terminology closely corresponds to the Expunge verb in the Actions menu.
Actually possible UI polish for 1.1.
This is a good idea. Another, somewhat simpler solution would be to change to "Hide Messages Marked for Deletion" as the default. Anyway, we should definitely do *something* to resolve this issue, because we're confusing people.
Because of the decision to remap 1.1->1.2 and 1.2->1.4, I'm going to be moving a large number of bugs around in the bugzilla. You can just search on 'body contains' 'Because of the decision to remap' and mark all as read. Please direct all questions about this change to evolution@ximian.com, not the bug. Luis
*** bug 219592 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 206061 ***