Description of problem:
When auto-moving within message list, move to "most preferred" or "least preferred unread". Auto moving within messages happens pretty often when e.g. user switches to the folder from another folder or when she clears search filter.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. move to the folder from another folder OR apply a search filter and clear it again
evolution moves in folders lists to one of following:
* the top of message list (in my case, to the oldest - least
interesting - actually)
* somewhere randomly among unread messages
evolution moves in message list so that "least preferred" unread message is visible - in my case of sorting by date, it's the oldest unread message
if the above is not possible, then it should move to "most preferred" message - in my case, the newest one aka the bottom of the list.
I looked briefly in the code and the rule for selecting a message when moving to a folder looks close to this:
a) if previously selected message exists, select it
b) if it doesn't exist or is not saved (like when multiple messages were
selected when leaving the folder), then pick message with the same uid from
the previous folder (usually doesn't apply)
c) then pick first message in the list
That's only a rough view from the code, though.
Current evolution, the 3.4.0, uses different approach, it picks unread message, if it cannot restore previously selected message. It's part of 2.30 too, according to:
Thus patches available.
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
I noticed one thing: it often sort-of-works - when switching to a folder with multiple unread, evo centers at the oldest unread message, but it leads to wrong behaviour in threaded view with Date (ascendin) sort:
[lots of old threads]
- thread a) start
--- unread message #2 <-- topmost unread
- thread b) start
--- unread message #1 <-- oldest unread
--- unread message #3 <-- newest unread
as you can see, topmost unread should be focused when user switches to the folder instead of oldest unread because sorting of threads based on thread newes message can differ wildly from message order in flat view.
Upstream patch part of 2.32.3, thus depend on the rebase bug.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.