Bug 186972 - unread message in different folder not selected after Go->next unread message
Summary: unread message in different folder not selected after Go->next unread message
Status: RESOLVED DUPLICATE of bug 183452
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.11.0
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-12 15:51 UTC by Michal Hlavinka
Modified: 2009-03-19 00:42 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Hlavinka 2009-03-12 15:51:53 UTC
Version:           1.11.0 (using KDE 4.2.0)
OS:                Linux
Installed from:    Fedora RPMs

If you are in folder where all messages are read and there is another folder with unread messages (when trying to find unread messages = Loop in All Folders; When entering a folder=Jump to Last Selected Message):

situation A:
1) press '+' = Go->Next unread message
2)question "Go to the next unread message in folder xyz?" - click "Go To"
3)xyz folder is opened but not on the unread message

situation B:
* the same as A - pressing '-' instead of '+'
* missing step 2, you get "go to folder" question after pressing '+', but you don't get this question after pressing '-'

In my opinion, after selecting "Go->Next unread message" (or pressing '+') kmail should jump to next unread message (ignoring "When entering a folder" value) and not only jump to the folder.
Comment 1 Jaime Torres 2009-03-12 20:43:44 UTC
Thank you for taking the time to report this bug and helping to make KDE
better. This particular bug has already been reported and is a duplicate of bug
183452, so it is being marked as such. Please look at the other bug report to
see if there is any missing information that you can provide, or to see if
there is a workaround for the bug. Additionally any further discussion
regarding the bug should occur in the other report. Feel free to continue to
report any other bugs you may find.

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