Summary: | one key mail reading | ||
---|---|---|---|
Product: | [Applications] kmail | Reporter: | Unknown <null> |
Component: | keys and menus | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | wishlist | CC: | bjoern |
Priority: | NOR | ||
Version: | 1.7 | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Mark current message as read before going to the next one. |
Description
Unknown
2004-11-08 15:38:27 UTC
Hi Dirk, Do you mean the functionality which the '+' key has ? no, the + key is defined as "go to next unread mail", "space" as "go to next unread text" but both do not mark the mail read when switching to the next. e.g. sylpheed provides this feature (but i do not remember whether it was configurable) Am Dienstag, 9. November 2004 13:26 schrieb Dirk Haage:
> no, the + key is defined as "go to next unread mail", "space" as
> "go to next unread text" but both do not mark the mail read when
> switching to the next.
Please check the following setting:
Settings -> Misc -> Folders -> Mark selected messages as read after ... sek
Andreas
No, that's a different feature, if I would choose e.g. 5 sec. and read a short mail in 2 sec. and switch to the next, the read mail is not marked read and if I start to read a long mail but do not finish, this mail is marked read even if I did not read it. (Even more, with "jump to first unread message" messages are marked read without reading at all) mfg /dirk Created attachment 15372 [details]
Mark current message as read before going to the next one.
This one line of code should do what the reporter asked for. It calls
slotSetMsgStatusUnread() before slotNextUnreadMessage().
Wow. My brain must have been short-circuted. It's of course slotSetMsgStatusRead() that should be called. This is pretty trivial. Can it be implemented with this one-liner or does it have to be configurable? Dirk, can you confirm that the solution is what you want? I'm not sure about this change. Let's say I'm using Space to browse all my unread messages, but I explicitely mark some of them as unread again because I want to deal with them later. With your patch they would be marked as read again. Making the behavior configurable doesn't really solve the above problem. Maybe the automagic marking as read should only be active for users who disabled "Mark selected messages as read after n seconds"? Or maybe the automagic marking as read should only be performed if the user didn't explicitely mark the current message as unread? Simple answer: You can always use Next unread message (+ (but I've reconfigured it to N, which is closer to space)) instead of Next unread text if you don't want to mark the message as read. If you don't like that, it could be possible to turn it off. But coupling it with "Mark selected messages as read after n seconds" is too limiting. Your last suggestion is better (but requires more coding), IMHO. There are currently a couple of possible usage modes: 1. With "Mark ... read after n seconds" set to a low number, mark all messages as read almost immediately; manually mark as unread (preferably bind a key to that command) those messages that you want to read again. 2. With "Mark ... read after n seconds" off or set to a high number, manually mark all messages as read (preferably bind a key to that command) before going to the next one, or mark the whole folder as read after reading the last message (beware of new messages arriving while reading). With this wish implemented, another usage mode becomes possible: 3. Simply push Space repeatedly. Combine with 1 or 2 depending on "Mark ... read after n seconds" setting. Long and uninteresting messages can be marked as read by the timer, while short and uninteresting messages can be dismissed rapidly. Suggestion 2 above is probably the best way to go. |