Version: 1.5 (using KDE KDE 3.0.99) Installed from: RedHat RPMs I sort my messages by conversation/thread, date ascending. When there is an unread message in a thread, but the thread view is collapsed, the Go->Next Unread Message (or the + keyboard shortcut) does not go to unread messages in this thread, but rather to a message that I've already read (typically the most recent message in that folder).
I can confirm this bug, it's still present in a current cvs snapshot of kmail. Also "Go->Previous Unread Message" doesn't jump to unread messages in closed threads too.
This is not just redhat RPM's. It's a problem on FreeBSD ports, as well as Gentoo's .emerge package. This effectively keeps me from being able to use threaded view, which I greatly prefer.
I found another way that this bug rears its ugly head. Given a thread of messages say - mesg1 - mesg2 - mesg3 where mesg1 is older than mesg2 and so on. Also mesg2 has a sub thread which make san expanded tree look like - mesg1 - mesg2 ---------- mesg2.1 ---------- mesg2.2 - mesg3 If the subtree at mesg2 is collapsed and I recieve a mail mesg4 I try to click on mesg4. Instead I get mesg2.2 and the subtree at mesg2 expands. Notice that mesg4 is 4 down from the thread root, mesg2.2 is 4 down from the thread root iff you ignore the subthreading. This bug also marks mesg4 as read when I am actually viewing mesg2.2. If this post is too confusing please mail me for clarification.
Subject: Re: go next unread message doesn't work if thread is collapsed Voter. Threading is probably the only thing that keeps me searching for another email client. I really like Kmail other than crappy threading... *shrug* John ----- Original Message ----- From: "Aidan Delaney" <adelaney@cs.may.ie> To: <sephtin@techgodz.com> Sent: Thursday, June 26, 2003 8:38 AM Subject: [Bug 54179] go next unread message doesn't work if thread is collapsed > ------- You are receiving this mail because: ------- > You are a voter for the bug, or are watching someone who is. > > http://bugs.kde.org/show_bug.cgi?id=54179 > > > > > ------- Additional Comments From adelaney@cs.may.ie 2003-06-26 15:38 ------- > I found another way that this bug rears its ugly head. > > Given a thread of messages say > > - mesg1 > - mesg2 > - mesg3 > > where mesg1 is older than mesg2 and so on. Also mesg2 has a sub thread which > make san expanded tree look like > > - mesg1 > - mesg2 > ---------- mesg2.1 > ---------- mesg2.2 > - mesg3 > > If the subtree at mesg2 is collapsed and I recieve a mail mesg4 I try to click on > mesg4. Instead I get mesg2.2 and the subtree at mesg2 expands. Notice that > mesg4 is 4 down from the thread root, mesg2.2 is 4 down from the thread root iff you > ignore the subthreading. > > This bug also marks mesg4 as read when I am actually viewing mesg2.2. > > If this post is too confusing please mail me for clarification. >
*** This bug has been marked as a duplicate of 50806 ***