Bug 136739 - don't mark as unread when composing
Summary: don't mark as unread when composing
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-02 22:16 UTC by Maciej Pilichowski
Modified: 2012-08-19 00:30 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2006-11-02 22:16:12 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    SuSE RPMs

Stay in inbox. Compose new mail -> send later. Observe outbox -> 1 unread mail. Send. Sent-mail --> 0 unread mail.

Mark as read on sent feature? :-)

It is a bug (design flaw) however I would suggest not keep the marking while sending but marking composed mail as read (the user actually wrote the whole thing so I think she/he read it too ;-))) ). This way such mail would be marked as read all the way.
Comment 1 Bram Schoenmakers 2006-11-02 23:02:48 UTC
I don't see buggy behaviour here. The unread message only indicates to the user there are pending messages. I'm tending to close this bug report because of that.
Comment 2 Maciej Pilichowski 2006-11-03 07:39:47 UTC
> The unread message only indicates to the user there are pending messages.

What? Unread message is the message which user didn't read. I hope it is crystal clear. The difference between unread and read (with exception of explicit action from user as mark-as-read) is this, that she/he took a second to read it.

So how it is possible that user doesn't even remotely touch the mail, doesn't even see the title, or anything about that mail and KMail while sending assumes that the user read it.

It is a bug. If you want to indicate the mail is in the queue use another status -- "queued", "unsent", show the number in the status bar, whatever, but do not redefine status (and word) for some temporary purpose:
a) it is very bad, computer <-> human interactions should be simplified, it is rather hard to understand if the computer redefines words, right?
b) it is not consistent -- there are no longer rules, there are rules and exceptions and try to teach someone and I guarantee you will have problems explaining such odd behaviour
Comment 3 Bram Schoenmakers 2006-11-03 08:00:20 UTC
You still did not convince me. From most other clients I've used in the past, they used this mechanism and I fail to see what's wrong with it.
Comment 4 Thiago Macieira 2006-11-03 08:44:14 UTC
The message count in the Outbox folder doesn't show the number of unread messages, but the number of total messages. So we don't technically need to mark messages as unread when composing.

But I don't agree that it's confusing. Even semantically, it is correct, since you haven't read that email in the Outbox folder. Even more: the destination hasn't yet read it either.
Comment 5 Maciej Pilichowski 2006-11-03 08:58:30 UTC
Bram -- what the "unread" means? Till now it meant "not read (yet)".

Thiago:
> The message count in the Outbox folder doesn't show the number of unread
> messages, but the number of total messages.

No, no, and once again no. I see column "unread" -> count --> 1. If this is a total count, the column should be titled "total". Once again -- do not redefine words, please.
KDE 3.5.5 btw. I can attach screenshot if you don't believe me.

> So we don't technically need to mark messages as unread when composing. 

The bug (flaw) is either in step 1 (after-composing) or in step 2 (after-sending). I don't insist in which step, I only suggest that it is more logical to correct the step 1.

> since you haven't read that email in the Outbox folder

Hmm, if you compose your mails with eyes closed you are right, but it is very rare case :-)
Comment 6 Myriam Schweingruber 2012-08-18 08:18:18 UTC
Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented.
Thank you for your understanding.
Comment 7 Luigi Toscano 2012-08-19 00:30:39 UTC
Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2.