Bug 187031 - message folder view repositions incorrectly after deleting mails in threaded view
Summary: message folder view repositions incorrectly after deleting mails in threaded ...
Status: RESOLVED DUPLICATE of bug 183923
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-13 10:22 UTC by Prakash Punnoor
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 Prakash Punnoor 2009-03-13 10:22:34 UTC
Version:            (using KDE 4.2.1)
Compiler:          gcc-Version 4.3.3 (Gentoo 4.3.3 p1.0, pie-10.1.5) Linux headache 2.6.29-rc7 #4 SMP Fri Mar 6 10:00:32 CET 2009 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ AuthenticAMD GNU/Linux
OS:                Linux
Installed from:    Gentoo Packages

I am subscribed to the Linux kernel mailing list and as such recevie around 400-1000 emails per day. I view them in threaded view and delete whole threads using ctrl+del. Now I expect that kmail positions to the next thread, but this is not always the case. kmail likes to repositzion more up (to older messages if sorting Date ascending). esp if the deleted thread of messages was very long. This is easier to reproduce if you sort to Date descending and start from newest (down) messages. I find this bug hugely annoying and it wasn't present in kmail 3.5.
Comment 1 Jaime Torres 2009-03-13 17:51:04 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
183923, 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 183923 ***