Version: 1.5.94 (using KDE 3.1.94 (CVS >= 20031206), compiled sources) Compiler: gcc version 3.3.1 OS: Linux (i686) release 2.6.0 Hello, here comes a little wish for post-3.2: IMO the separate reader window should have two buttons to read the next/previous message. Currently one has to close the reader win and then open the next message which is not optimal. Thanks, Thomas
oh, and using ESC to close the window (instead of clicking the X with the mouse) would be very cool as well :-) Thomas
The window can be closed with Ctrl+w and Alt+F4 (just like other windows).
*** Bug 95289 has been marked as a duplicate of this bug. ***
*** Bug 103706 has been marked as a duplicate of this bug. ***
A button to delete the message then have the next unread message displayed in the viewer would be useful as well
I second the comment 5. And optionally close the message window and delete the message from message list. Even some good to have buttons can be implemented with macros, I think those are part of basic functionality and most users (like my parents) are not able to configure those.
Delete button has been added in fixing bug 65115. But still need next/previous buttons, and the ability to automatically move to next or previous message (configurable) after deleting a message.
This comes close to 117808 "tabbed mail browsing", but probably in a simpler wa. I guess KDE-PIM developpers would have to define a strategy here. Currently, wish 117808 has 490 votes.
*** Bug 127917 has been marked as a duplicate of this bug. ***
Created attachment 18178 [details] in the Patch for the 3.5 branch This patch adds navigation buttons to the reader window. I'm still waiting for approval so that I can commit it.
*** Bug 135489 has been marked as a duplicate of this bug. ***
Thanks Christian, really appreciate your efforts for this.
See also bug 132089, which suggests to use the existing actions somehow (so that the shortcut can be shared for example).
*** Bug 138008 has been marked as a duplicate of this bug. ***
*** Bug 190168 has been marked as a duplicate of this bug. ***
*** Bug 243371 has been marked as a duplicate of this bug. ***
Reassigning to kmail2