Bug 295932 - Setting "Loop in all folders" when trying to find unread messages does not work properly
Summary: Setting "Loop in all folders" when trying to find unread messages does not wo...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: Git (master)
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-13 15:12 UTC by Marc Schiffbauer
Modified: 2017-01-07 21:25 UTC (History)
1 user (show)

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 Marc Schiffbauer 2012-03-13 15:12:46 UTC
Settings -> Configure Kmail
Misc -> Folders -> When trying to find unread messages:

The setting "Loop in all folders" does not work properly and instead behaves equal to "Loop in current folder".
Only difference: With ".. all folders" it will jump from a folder without unread messages to the next folder with unread messages.

The problem is that it will loop in a folder until there are no unread messages anymore, which seems wrong. (I have set kmail to NOT mark messages as read automatically, because I use the unread flag as something like a "TODO" flag)

Expected behavior would be to not loop within a folder when "Loop in all folders" is set but instead jump to the next folder if last unread message within a folder has been reached.

"Loop in all folders" should not work on top of the per folder "Loop within Current folder" setting but on top of "Do not Loop" setting.

-Marc
Comment 1 Denis Kurz 2016-09-24 18:11:48 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 21:25:29 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.