After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 624862 - Also mark messages in subfolders? is also asked when there is no subfolder
Also mark messages in subfolders? is also asked when there is no subfolder
Status: RESOLVED DUPLICATE of bug 546551
Product: evolution
Classification: Applications
Component: Mailer
2.30.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-07-20 18:05 UTC by kalanzun
Modified: 2010-07-21 04:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description kalanzun 2010-07-20 18:05:41 UTC 
When I pick "Mark messages as read" from the context menu of a folder, it always asks me if I also want to mark messages as read in subfolders, even if there are no subfolders. In prior versions, it didn't ask that question in this case.

A different dialog appears, when I choose Folder -> Mark all messages as read from the menu. It basically asks if I really want to mark all messages as read, but it can be disabled by activating "Do not ask me again".

The menu option Mark all messages as read behaves different as the context menu one. The menu one can only mark messages in the current folder, the context menu one can do both, only in current folder, and in current folder and all subfolders.

I frequently use the context menu option to mark all messages as read. Its annoying to always have to click away that dialog box asking me a totally useless question, when the current folder has no subfolder.

Additionally, I think it would be nice, if the menu option and the context menu option behave the same way.

Debian squeeze, 2.30.2-1
Comment 1 Akhil Laddha 2010-07-21 04:16:45 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 546551 ***