(*** This bug was imported into bugs.kde.org ***) Package: kmail Version: 1.2 (KDE 2.0 >= 20001022) Severity: normal Compiler: gcc version 2.95.3 19991030 (prerelease) OS: Linux 2.2.17-21mdksmp i686 (compiled sources) Deleting the first message in a thread should result in the next message in the thread being displayed. Instead the messages are resorted (e.g. based on date) and the view jumps to the next message in sort order. This violates the principle of least surprise and makes the threaded view very difficult to use.
On Sunday 29 October 2000 22:42 Jon Aseltine wrote: > Package: kmail > Version: 1.2 (KDE 2.0 >= 20001022) > Severity: normal > Compiler: gcc version 2.95.3 19991030 (prerelease) > OS: Linux 2.2.17-21mdksmp i686 (compiled sources) > > Deleting the first message in a thread should result in the next message in > the thread being displayed. Yes it does. > Instead the messages are resorted (e.g. based > on date) and the view jumps to the next message in sort order. This > violates the principle of least surprise and makes the threaded view very > difficult to use. I think not resorting would be a bad idea. I delete from the bottom of a thread up it works okay. The best solution I know of would be to implement marking of messages for deletion (ie delayed deletion) and the messages will be moved to the trash when the folder is exited. BFN Don.
You are right about it jumping to the next message in the thread. But the resorting is still bothersome: I like to read my mail top to bottom but I also like to read threads in order. Once the resort happens I have to scroll back up because lots of intermediate messages are skipped. Another solution would be for each thread to have a date the same as the first message in the thread (and doesn't change as messages are deleted from the thread). Then sort on the thread date. The date would persist until the thread is gone. This would allow for immediate deletion but also eliminate jumping around the message list. What do you think? Thanks Jon On Sunday 29 October 2000 17:42 Don Sanders wrote: > The best solution I know of would be to implement marking of messages for > deletion (ie delayed deletion) and the messages will be moved to the > trash when the folder is exited. > > BFN > Don. -- _______________________________________________________________________ Jonathan Aseltine aseltine@cs.umass.edu MAS Umass Amherst
On Sunday 29 October 2000 18:43 Jon Aseltine wrote: > You are right about it jumping to the next message in the thread. But the > resorting is still bothersome: I like to read my mail top to bottom but I > also like to read threads in order. Once the resort happens I have to > scroll back up because lots of intermediate messages are skipped. > > Another solution would be for each thread to have a date the same as the > first message in the thread (and doesn't change as messages are deleted > from the thread). Then sort on the thread date. The date would persist > until the thread is gone. This would allow for immediate deletion but also > eliminate jumping around the message list. What do you think? What's wrong with reading an entire thread before deleting it? That seems to make most sense to me anyways. -- George Staikos
On Sunday 29 October 2000 19:01 George Staikos wrote: > > What's wrong with reading an entire thread before deleting it? That > seems to make most sense to me anyways. Nothing is wrong with that. But once I start deleting kmail resorts every time jumping all over the message list. When I'm finished I may be somewhere near the end of the message list: I then need to scroll back up and hunt for wherever I was. Not everyone works the same way true enough. But this behavior is unexpected confusing and unlike any other mail reader I have ever used. Jon -- _______________________________________________________________________ Jonathan Aseltine aseltine@cs.umass.edu MAS Umass Amherst
On Monday 30 October 2000 02:02 Jon Aseltine wrote: > On Sunday 29 October 2000 19:01 George Staikos wrote: > > What's wrong with reading an entire thread before deleting it? That > > seems to make most sense to me anyways. > > Nothing is wrong with that. But once I start deleting kmail resorts every > time jumping all over the message list. When I'm finished I may be > somewhere near the end of the message list: I then need to scroll back up > and hunt for wherever I was. > > Not everyone works the same way true enough. But this behavior is > unexpected confusing and unlike any other mail reader I have ever used. > > Jon I read the thread finish at the bottom of the thread delete the last message then press left-arrow to go to the previous message repeat until the thread is deleted. BFN Don.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I was originally going to submit this as a bug but having seen that someone's beaten me to it and that some of the comments in the bug log seem to be "Why are you doing that anyway?" I'd like to add my voice to the throng saying it's a misfeature. To hopefully make it very clear take a look at http://people.freebsd.org/~nik/snapshot1.png This shows me reading the first message in a two message thread. Note that the next message in the thread is displayed correctly underneath this message. Notice also that the unread message after this thread is "cloning network interfaces". Now I delete the first message in the thread and the display changes to http://people.freebsd.org/~nik/snapshot2.png As you can see KMail has correctly jumped to the correct message but the messages have been reordered and the "cloning network interfaces" new message is now above the message I'm reading. So I've got to scroll back up the list to make sure I've read all the messages. This is even more of a problem in long threads. Ideally I should be able to read all the new messages by 1. Clicking on the first new message. 2. Choosing the delete message function or 'next unread' function as necessary. I should never need to scroll back and forth through the message list like this. Compare and contrast with how something like Mutt handles this. N - -- FreeBSD: The Power to Serve http://www.freebsd.org/ FreeBSD Documentation Project http://www.freebsd.org/docproj/ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjsmMKcACgkQk6gHZCw343X6lwCfSRyY9quIBgS2p/iCY5ebFzjM MX4Amwc3uVxC7j1TManjWcs/50tdEQwV =M7b1 -----END PGP SIGNATURE-----
I left KDE 2.1.1 expecting to see this very frustrating bug to me fixed. now after a very rough upgrade to 2.2.1 its still around. Threads need to stay together and not move around whether one deletes messages or reads them. This is the way Netscape Mail works Eudora works and any other thoughtfully developed mail client. Personally until this is cleared up I think Kmail has regressed not grown. -- Rob Blomquist Kirkland WA
Folder are now also bold when subfolders contain new mail which should allow you to find the folders with new mail more easy. Displaying the total unread messages would only be confusing since top level folder can contain mail on its own.
This problem has been fixed (KDE 3.2).
Reopening due to bug 140863.
*** Bug 140863 has been marked as a duplicate of this bug. ***
With kmail 1.12 (kde 4.3.0), there is a context menu to "move Thread to Trash". Also, when the root message of a thread is deleted (individually), the messages are resorted, but the next message in the thread is selected.
When I delete the top message of a thread in kmail 1.12.3 the whole thread is deleted - so considering this fixed.