[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#14060: marked as done (deleting threaded messages) by Michael =?iso-8859-1?q?H=E4ckel?= <haeckel
From:       owner () bugs ! kde ! org (Stephan Kulow)
Date:       2001-12-31 12:33:11
[Download RAW message or body]

Your message with subj: sorting and threads

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.



has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Stephan Kulow
(administrator, KDE bugs database)

Received: (at submit) by bugs.kde.org; 29 Oct 2000 21:43:02 +0000
Received: (qmail 17829 invoked from network); 29 Oct 2000 21:42:58 -0000
Received: from v90-232-217.dialup.umass.edu (HELO joseph.localdomain) (128.119.232.217)
  by max.tat.physik.uni-tuebingen.de with SMTP; 29 Oct 2000 21:42:58 -0000
Received: from joseph.localdomain (joseph.localdomain [127.0.0.1])
	by joseph.localdomain (Postfix) with SMTP id 6CAE94E088
	for <submit@bugs.kde.org>; Sun, 29 Oct 2000 16:42:55 -0500 (EST)
Subject: threaded messages
From: Jon Aseltine <aseltine@cs.umass.edu>
To: submit@bugs.kde.org
Message-Id: <20001029214255.6CAE94E088@joseph.localdomain>
Date: Sun, 29 Oct 2000 16:42:55 -0500 (EST)

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.
[prev in list] [next in list] [prev in thread] [next in thread]