Red Hat Bugzilla – Bug 236841
when I move a message into a different folder, the next message should display
Last modified: 2007-11-30 17:12:02 EST
When I am viewing a message in the message preview, and I drag and drop that
specific message into a different folder, and it therefore disappears from the
folder I'm viewing, the next message should be selected automatically and
displayed in the message preview. Instead, what happens is that no message ends
up being selected.
This bug was already fixed by upstream, patch included at bug
that was fixed upstream in Evolution 2.10.1
The upstream bug was about deleting a message, not about moving a message into
a different failure. Deleting works as expected in 2.10.1, but moving
doesn't. Hence my bug report.
I could not reproduce this bug on 2.10.1, but on 2.8.3 I could.
I was testing it in this way:
a) I did create an empty folder in "On This Computer->Inbox".
b) have exactly 3 messages in the Inbox
c) when I move the second in the list with drag&drop over new folder, then it
disappear from Inbox and the (previously) third message is selected.
d) when I will move the second message from Inbox now (it is that last), then:
d) 1) on Evolution 2.8.3 *is not* selected message above that moved,preview is empty
d) 2) on Evolution 2.10.1 *is* selected that previous message, as expected.
Could you write here result of "rpm -q evolution", please? Only to confirm you
have installed right version. (May be also Help->About in Evolution).
May be I missed something in my process?
There is only one exception, when you have unchecked View->Hide Deleted
Messages, then that moved message is only marked as deleted and the focus in
list isn't changed.
Well, I'll be darned. Perhaps when I filed the bug I was using 2.10 rather than
2.10.1. You're right, it works for me now as well.
I *knew* I wasn't crazy.
It works for local folders. It works for IMAP folders. It *doesn't* work for
When you move the message you're viewing from one Exchange folder to another,
the next message isn't selected.
OK, in that case the fix in upstream bug  will probably help you.
Unfortunately, it still waits for an approve. Are you OK to close this as
upstream and track the problem there?
Fine with me. Marking resolved / upstream.